From: ludo@gnu.org (Ludovic Courtès)
To: Quiliro Ordonez Baca <quiliro@riseup.net>
Cc: 29662@debbugs.gnu.org
Subject: bug#29662: bug#24194: GUIX gc - add warning
Date: Fri, 22 Dec 2017 10:46:48 +0100 [thread overview]
Message-ID: <87608z9jsn.fsf@gnu.org> (raw)
In-Reply-To: <87h8slrvyw.fsf@portkomputilo.i-did-not-set--mail-host-address--so-tickle-me> (Quiliro Ordonez Baca's message of "Wed, 20 Dec 2017 15:21:59 -0500")
Hi Quiliro,
Quiliro Ordonez Baca <quiliro@riseup.net> skribis:
>>> menuentry "GNU with Linux-Libre 4.12.9 (beta)"
>>> Kernel panic
>>
>> Could you paste (or take a picture) what’s on the screen? Without this
>> we can’t draw any conclusions.
>
> I attach one photo. There are different messages. But, wouldn't it be
> rude to attach 6MB to the whole mailing list?
Please try to compress them more. A few 100KiB is OK.
The picture you posted roughly shows:
deleting group 'sshd'
groupdel: existing lock file /etc/group.lock
groupdel: cannot lock /etc/group
…
ERROR: no code for module (ice-9 popen)
The group.lock error above suggests it’s an old generation before commit
aad8a143000600abec5c8ebfadec4c09f34f1b73 (see
<https://bugs.gnu.org/28772>, 12 Oct. 2017).
The (ice-9 popen) issue that ensues, I don’t know; you should type “,bt”
at the prompt when that happens and report the backtrace.
But let’s ignore this one because it looks like an old generation.
>>> menuentry "GNU with Linux-Libre 4.11.6 (beta) (#1, 2017-06-21 18:01)"
>>> No GUI. Lost keyboad configuration on tty's. Logged in as user. The
>>> output of 'sudo herd status' was 'error: connect:
>>> /var/run/shepherd/socket: No existe el fichero o el directorio'.
>>
>> Sounds like the root file system is missing files.
>>
>> Can you send the content of /var/log/shepherd.log and the last ~100
>> lines of /var/log/messages for that config?
>
> /var/log/shepherd.log:
> 2017-12-19 20:40:53 Service console-font-tty2 has been started.
[...]
> 2017-12-19 20:41:44 Service ssh-daemon could not be started.
Apart from that last line I don’t see anything to worry about.
Are you sure you paste the log of this very generation where “sudo herd
status” fails?
> I understand you doubt that this happens because guix is not supposed to
> do it. I know I could have missed something, but I doubt it. Please give me the
> benefit of the doubt. It is important for me to confirm that guix does
> not have this bug. I can try to reproduce the problem with another installation.
I don’t doubt you’ve stumbled upon a bug! I’m just trying to isolate
the various issues, and here it’s just too fuzzy for me to draw any
conclusion.
Do you have a working GuixSD configuration based on a recent-ish master?
Or a clear failure with a recent GuixSD configuration?
We should focus on just one issue at a time.
Thank you,
Ludo’.
next prev parent reply other threads:[~2017-12-22 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 23:59 bug#24194: GUIX gc - add warning J. Eppler
2016-08-10 5:53 ` Mark H Weaver
2016-08-10 18:56 ` Leo Famulari
2017-11-12 21:43 ` Ludovic Courtès
[not found] ` <87d13l89yy.fsf@portkomputilo.i-did-not-set--mail-host-address--so-tickle-me>
[not found] ` <87h8swtjdp.fsf@gnu.org>
[not found] ` <87h8slrvyw.fsf@portkomputilo.i-did-not-set--mail-host-address--so-tickle-me>
2017-12-22 9:46 ` Ludovic Courtès [this message]
2017-12-24 23:16 ` bug#29662: " Joshua Branson
2018-01-16 21:16 ` Adonay Felipe Nogueira
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87608z9jsn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29662@debbugs.gnu.org \
--cc=quiliro@riseup.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).