From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) Subject: bug#29662: bug#24194: GUIX gc - add warning Date: Fri, 22 Dec 2017 10:46:48 +0100 Message-ID: <87608z9jsn.fsf@gnu.org> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37285) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eSJv1-00058Y-48 for bug-guix@gnu.org; Fri, 22 Dec 2017 04:47:08 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eSJuw-00046v-Ul for bug-guix@gnu.org; Fri, 22 Dec 2017 04:47:07 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:38197) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eSJuw-00045w-QZ for bug-guix@gnu.org; Fri, 22 Dec 2017 04:47:02 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eSJuw-0004Xn-DR for bug-guix@gnu.org; Fri, 22 Dec 2017 04:47:02 -0500 Sender: "Debbugs-submit" Resent-Message-ID: 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") 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: Quiliro Ordonez Baca Cc: 29662@debbugs.gnu.org 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=E2=80=99s on the screen? Witho= ut this >> we can=E2=80=99t 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 =E2=80=A6 ERROR: no code for module (ice-9 popen) The group.lock error above suggests it=E2=80=99s an old generation before c= ommit aad8a143000600abec5c8ebfadec4c09f34f1b73 (see , 12 Oct. 2017). The (ice-9 popen) issue that ensues, I don=E2=80=99t know; you should type = =E2=80=9C,bt=E2=80=9D at the prompt when that happens and report the backtrace. But let=E2=80=99s 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=E2=80=99t see anything to worry about. Are you sure you paste the log of this very generation where =E2=80=9Csudo = herd status=E2=80=9D 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=E2=80=99t doubt you=E2=80=99ve stumbled upon a bug! I=E2=80=99m just= trying to isolate the various issues, and here it=E2=80=99s 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=E2=80=99.