GNU bug report logs - #54969
"activate.scm.drv" Empty and Live

Previous Next

Package: guix;

Reported by: Zain Jabbar <zaijab2000 <at> gmail.com>

Date: Sat, 16 Apr 2022 03:15:01 UTC

Severity: normal

Done: Maxime Devos <maximedevos <at> telenet.be>

Bug is archived. No further changes may be made.

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 54969 in the body.
You can then email your comments to 54969 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guix <at> gnu.org:
bug#54969; Package guix. (Sat, 16 Apr 2022 03:15:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Zain Jabbar <zaijab2000 <at> gmail.com>:
New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org. (Sat, 16 Apr 2022 03:15:02 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Zain Jabbar <zaijab2000 <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: "activate.scm.drv" Empty and Live
Date: Fri, 15 Apr 2022 15:20:21 -1000
[Message part 1 (text/plain, inline)]
Aloha Guix,

A number of errors have appeared on my system. Notably I have the following
issue with "sudo guix system reconfigure $CONFIG_FILE":
"guix system: error: error parsing derivation
`/gnu/store/8jqz1m1src0h4md70q09rlxppdy6d1jx-activate-service.scm.drv':
expected string `Derive(['"

I believe this is due to key files on my system (e.g.
"/gnu/store/...-activate.scm.drv" and
"/gnu/store/...-activate-service.scm.drv") have become both empty and live
on my system.

Here is the result of trying to repair using "guix gc"
"zjabbar <at> tao ~$ sudo guix gc --verify=contents,repair
reading the store...
checking path existence...
checking hashes...
path `/gnu/store/035mddyijs1xrp7z36fn1yvqd6asx4vq-provenance-builder' was
modified! expected h
ash `468eebad16e7842b982f046d0e846c5bc2672af01879cc43409f9534820eb815', got
`77ac62e2629d8e45f
624589c0c8bf99e24b3a722349bf1e79bc186008534e246'
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://bordeaux.guix.gnu.org'...
100.0%
error: cannot repair path
`/gnu/store/035mddyijs1xrp7z36fn1yvqd6asx4vq-provenance-builder'
path `/gnu/store/0c9hqf02jksb06r3ywdz0alq1154kkq9-grub.cfg-builder' was
modified! expected hash
`04ed96b94726f1ffc7ce3fae556d5c057de1e0348da488a31694190787783b6a', got
`77ac62e2629d8e45f624589c0c8bf99e24b3a722349bf1e79bc186008534e246'
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://bordeaux.guix.gnu.org'...
100.0%
error: cannot repair path
`/gnu/store/0c9hqf02jksb06r3ywdz0alq1154kkq9-grub.cfg-builder'
path
`/gnu/store/17q0ymk80965sm1vww4anwz96q57q229-shepherd-user-homes.scm.drv'
was modified! expected hash
`c69bf28c4c631368cbe1ad4d5d3dcc424f5a0d4a658cb964e796b2b92a6306fd', got
`77ac62e2629d8e45f624589c0c8bf99e24b3a722349bf1e79bc186008534e246'
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://bordeaux.guix.gnu.org'...
100.0%
error: cannot repair path
`/gnu/store/17q0ymk80965sm1vww4anwz96q57q229-shepherd-user-homes.scm.drv'
path
`/gnu/store/1byrjg1w8mqmgla4257xc25lyh042bq2-xdg-desktop-database-builder'
was modified! expected hash
`77ed327cc6131e0a0cc6e207e679b09edc826a26a2bc4bf5c7f0f6e3f7bc6517', got
`77ac62e2629d8e45f624589c0c8bf99e24b3a722349bf1e79bc186008534e246'
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://bordeaux.guix.gnu.org'...
100.0%
error: cannot repair path
`/gnu/store/1byrjg1w8mqmgla4257xc25lyh042bq2-xdg-desktop-database-builder'
path `/gnu/store/1mcdi0zvcmb184dg6459cpxg4hr1pz4h-glib-schemas.drv' was
modified! expected hash
`b9504e60e0576992ee0cb323ec15a71a0b6aeedcb47f22be5a16040063da0757', got
`77ac62e2629d8e45f624589c0c8bf99e24b3a722349bf1e79bc186008534e246'
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://bordeaux.guix.gnu.org'...
100.0%
error: cannot repair path
`/gnu/store/1mcdi0zvcmb184dg6459cpxg4hr1pz4h-glib-schemas.drv'
path `/gnu/store/1wdm4khqlrx2yxb646jp9s7ia3f9p9w9-configuration.scm' was
modified! expected hash
`851294df3f63927f9da53b318e7cec9dedf0d7e149a57be38707ae3c2a819e80', got
`77ac62e2629d8e45f624589c0c8bf99e24b3a722349bf1e79bc186008534e246'
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://bordeaux.guix.gnu.org'...
100.0%
error: cannot repair path
`/gnu/store/1wdm4khqlrx2yxb646jp9s7ia3f9p9w9-configuration.scm'"

It looks like a lot of files have the same hash and are empty. Is the only
way to fix this to reinstall Guix? Is it known why this could happen in the
first place?

-- 
Thank you,
Zain Jabbar
[Message part 2 (text/html, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#54969; Package guix. (Sat, 16 Apr 2022 13:54:02 GMT) Full text and rfc822 format available.

Message #8 received at 54969 <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: Zain Jabbar <zaijab2000 <at> gmail.com>, 54969 <at> debbugs.gnu.org
Subject: Re: bug#54969: "activate.scm.drv" Empty and Live
Date: Sat, 16 Apr 2022 15:52:55 +0200
[Message part 1 (text/plain, inline)]
Zain Jabbar schreef op vr 15-04-2022 om 15:20 [-1000]:
> Is it known why this could happen in the first place?

I guess a power outage or the like.  Currently the guix daemon never
calls 'sync' or the like (except possibly for the SQlite db), though
maybe it should (at cost of some performance).

> Is the only way to fix this to reinstall Guix?

That's a way to do it, but there are less heavy-handed ways.  E.g.,
maybe "guix gc --verify=repair" could be extended to delete objects
that are broken (wrong hash) and aren't referenced? (long-term)

For the short term, maybe do "guix gc", possibly some of the broken
files are unused.

Greetings,
Maxime.
[signature.asc (application/pgp-signature, inline)]

Reply sent to Maxime Devos <maximedevos <at> telenet.be>:
You have taken responsibility. (Sat, 16 Apr 2022 14:48:02 GMT) Full text and rfc822 format available.

Notification sent to Zain Jabbar <zaijab2000 <at> gmail.com>:
bug acknowledged by developer. (Sat, 16 Apr 2022 14:48:02 GMT) Full text and rfc822 format available.

Message #13 received at 54969-done <at> debbugs.gnu.org (full text, mbox):

From: Maxime Devos <maximedevos <at> telenet.be>
To: Zain Jabbar <zaijab2000 <at> gmail.com>
Cc: 54969-done <at> debbugs.gnu.org
Subject: Re: bug#54969: "activate.scm.drv" Empty and Live
Date: Sat, 16 Apr 2022 16:47:41 +0200
[Message part 1 (text/plain, inline)]
Zain Jabbar schreef op za 16-04-2022 om 04:18 [-1000]:
> Aloha Maxime Devos,
> 
> Your suggestion worked! I did the following but I'm not sure how much
> was actually needed: [...]

Nice, closing.

FWIW, you can close reports yourself by sending to
NNNNN-done <at> debbugs.gnu.org instead of NNNNN <at> debbugs.gnu.org.

Greetings,
Maxime.
[signature.asc (application/pgp-signature, inline)]

Information forwarded to bug-guix <at> gnu.org:
bug#54969; Package guix. (Sat, 16 Apr 2022 15:14:02 GMT) Full text and rfc822 format available.

Message #16 received at 54969 <at> debbugs.gnu.org (full text, mbox):

From: Zain Jabbar <zaijab2000 <at> gmail.com>
To: Maxime Devos <maximedevos <at> telenet.be>
Cc: 54969 <at> debbugs.gnu.org
Subject: Re: bug#54969: "activate.scm.drv" Empty and Live
Date: Sat, 16 Apr 2022 04:18:57 -1000
[Message part 1 (text/plain, inline)]
Aloha Maxime Devos,

Your suggestion worked! I did the following but I'm not sure how much was
actually needed:

1. Use guix pull and guix system to switch to an older generation (I did
like -100)
2. Use guix gc
3. Run guix system again which remakes the files (like activate.scm as per
title)

This time guix system actually runs to completion. Mahalo nui iā ʻoe!

On Sat, Apr 16, 2022, 3:53 AM Maxime Devos <maximedevos <at> telenet.be> wrote:

> Zain Jabbar schreef op vr 15-04-2022 om 15:20 [-1000]:
> > Is it known why this could happen in the first place?
>
> I guess a power outage or the like.  Currently the guix daemon never
> calls 'sync' or the like (except possibly for the SQlite db), though
> maybe it should (at cost of some performance).
>
> > Is the only way to fix this to reinstall Guix?
>
> That's a way to do it, but there are less heavy-handed ways.  E.g.,
> maybe "guix gc --verify=repair" could be extended to delete objects
> that are broken (wrong hash) and aren't referenced? (long-term)
>
> For the short term, maybe do "guix gc", possibly some of the broken
> files are unused.
>
> Greetings,
> Maxime.
>
[Message part 2 (text/html, inline)]

bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sun, 15 May 2022 11:24:04 GMT) Full text and rfc822 format available.

This bug report was last modified 3 years and 94 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.