From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joshua Branson Subject: bug#29662: bug#24194: GUIX gc - add warning Date: Sun, 24 Dec 2017 23:16:20 +0000 Message-ID: References: <8108bd02-a9f8-fad9-e5a1-93416ece607b@openmailbox.org> <20160810185620.GA14104@jasmine> <87mv3rb2bj.fsf@gnu.org> <87d13l89yy.fsf@portkomputilo.i-did-not-set--mail-host-address--so-tickle-me> <87h8swtjdp.fsf@gnu.org> <87h8slrvyw.fsf@portkomputilo.i-did-not-set--mail-host-address--so-tickle-me>, <87608z9jsn.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="_000_DM5PR1001MB22203988B1CD6A2705A4727FA6000DM5PR1001MB2220_" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60001) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eTFVx-0005i0-QG for bug-guix@gnu.org; Sun, 24 Dec 2017 18:17:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eTFVu-0000Oi-GJ for bug-guix@gnu.org; Sun, 24 Dec 2017 18:17:05 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:42344) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eTFVu-0000OX-C1 for bug-guix@gnu.org; Sun, 24 Dec 2017 18:17:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eTFVu-0003lZ-3E for bug-guix@gnu.org; Sun, 24 Dec 2017 18:17:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87608z9jsn.fsf@gnu.org> Content-Language: en-US List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= , Quiliro Ordonez Baca Cc: "29662@debbugs.gnu.org" <29662@debbugs.gnu.org> --_000_DM5PR1001MB22203988B1CD6A2705A4727FA6000DM5PR1001MB2220_ Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Hey, Sorry to bother you guys, but I'm having trouble leaving this email list... I've tried logging into the web interface, and that failed. I tried emailing guix-devel-leave@gnu.org, and that didn't seam to work. Can someone help me leave this email list? Thanks, Joshua ________________________________ From: bug-Guix on= behalf of Ludovic Court=E8s Sent: Friday, December 22, 2017 4:46 AM To: Quiliro Ordonez Baca Cc: 29662@debbugs.gnu.org Subject: bug#29662: bug#24194: GUIX gc - add warning Hi Quiliro, Quiliro Ordonez Baca skribis: >>> menuentry "GNU with Linux-Libre 4.12.9 (beta)" >>> Kernel panic >> >> Could you paste (or take a picture) what=92s on the screen? Without thi= s >> we can=92t 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 =85 ERROR: no code for module (ice-9 popen) The group.lock error above suggests it=92s an old generation before commit aad8a143000600abec5c8ebfadec4c09f34f1b73 (see , 12 Oct. 2017). The (ice-9 popen) issue that ensues, I don=92t know; you should type =93,bt= =94 at the prompt when that happens and report the backtrace. But let=92s 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=92t see anything to worry about. Are you sure you paste the log of this very generation where =93sudo herd status=94 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 instal= lation. I don=92t doubt you=92ve stumbled upon a bug! I=92m just trying to isolate the various issues, and here it=92s 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=92. --_000_DM5PR1001MB22203988B1CD6A2705A4727FA6000DM5PR1001MB2220_ Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable
Hey,
Sorry to bother you guys, but I'm having trouble leaving this email list...=

I've tried logging into the web interface, and that failed.

I tried emailing guix-devel-leave@gnu.org, and that didn't seam to work.
Can someone help me leave this email list?

Thanks,

Joshua
From: bug-Guix <bug-guix= -bounces+bransoj+bug-guix=3Dhotmail.com@gnu.org> on behalf of Lu= dovic Court=E8s <ludo@gnu.org>
Sent: Friday, December 22, 2017 4:46 AM
To: Quiliro Ordonez Baca
Cc: 29662@debbugs.gnu.org
Subject: bug#29662: bug#24194: GUIX gc - add warning
 
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=92s on the screen?  = Without this
>> we can=92t draw any conclusions.
>
> I attach one photo. There are different messages. But, wouldn't it be<= br> > 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
  =85
  ERROR: no code for module (ice-9 popen)

The group.lock error above suggests it=92s an old generation before commit<= br> aad8a143000600abec5c8ebfadec4c09f34f1b73 (see
<https://bugs.gnu.org/28772&g= t;, 12 Oct. 2017).

The (ice-9 popen) issue that ensues, I don=92t know; you should type =93,bt= =94
at the prompt when that happens and report the backtrace.

But let=92s ignore this one because it looks like an old generation.

>>> menuentry "GNU with Linux-Libre 4.11.6 (beta) (#1, 2017-0= 6-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 ~10= 0
>> 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=92t see anything to worry about.

Are you sure you paste the log of this very generation where =93sudo herd status=94 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 gi= ve 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 ins= tallation.

I don=92t doubt you=92ve stumbled upon a bug!  I=92m just trying to is= olate
the various issues, and here it=92s 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=92.



--_000_DM5PR1001MB22203988B1CD6A2705A4727FA6000DM5PR1001MB2220_--