GNU bug report logs -
#28772
guix system reconfigure after kernel panic user or group not created
Previous Next
Full log
Message #17 received at 28772 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Hello Ludovic,
apologies for not adding logs before. It's hard to do when I do guix
commands from Xterm and not from Emacs. Emacs *shell* or *compilation*
buffers will eat all memory if they get too much text.
Probably need to redirect STDOUT STDERR in file when Xterm do guix.
I heard Guix folks work on implementing tiny log output to console and
redirect everything else to a log file. This will be my life saver.
ludo <at> gnu.org (Ludovic Courtès) writes:
> Hello,
>
> Oleg Pykhalov <go.wigust <at> gmail.com> skribis:
>
>> During 'guix system reconfigure' I got a kernel panic.
>
> Can you show the exact command and its output?
Sorry, as I said this is not a topic and I don't want to do it again and
I caution to make it on my current system.
I will setup a specific Guix VM for this, where I could make a 'system
reconfigure'. Then I'll create a new bug report with full log.
Neverless I'll leave a how-to reproduce it below for at least for myself
TODO list.
The problem
===========
The bigger problem from my view are files like /etc/group.lock and
/etc/passwd.lock. For example:
sudo touch /etc/group.lock
/etc/config.scm
(operating-system
;; …
(groups (cons
(user-group (name "test"))
%base-groups)))
reconfigure log
[report.send (text/plain, attachment)]
[Message part 3 (text/plain, inline)]
The new system generation was produced without "test" group, so you
could reboot into it. And it could lead to problems if we will have a
tiny output to console and big output to a log file, I guess.
> A user-land program is not supposed to be able to cause a kernel panic;
> if it does, that’s a kernel bug.
How to make a kernel panic
The problem will be No defined variable IPTABLES-SSH after 'guix system
reconfigure' and kernel crash after.
$HOME/src/iptables/iptables/ru.scm
(define-module (iptables ru)
;; …
)
(define %iptables-ssh
"-A INPUT -p tcp --dport 22 \
-m state --state NEW -m recent --set --name SSH -j ACCEPT")
/etc/config.scm
(use-modules ;; …
(iptables ru))
(define start-firewall
#~(let ((iptables
(lambda (str)
(zero? (system (string-join `(,#$(file-append iptables
"/sbin/iptables")
,str) " "))))))
(format #t "Install iptables rules.~%")
(and
;; …
(iptables %iptables-ssh))))
(define firewall-service
(simple-service 'firewall shepherd-root-service-type
(list
(shepherd-service
(provision '(firewall))
(requirement '())
(start #~(lambda _
#$start-firewall))
(respawn? #f)
(stop #~(lambda _
(zero?
(system* #$(file-append iptables
"/sbin/iptables")
"-F"))))))))
(operating-system
;; …
(services (cons* ;; …
firewall-service)))
Make a kernel panic
sudo GUILE_LOAD_PATH=\"$HOME/src/iptables\
:$GUILE_LOAD_PATH\" guix system reconfigure \
$HOME/dotfiles/guix/system-magnolia.scm
# Run above again and kernel will panic.
> But perhaps you got the kernel panic *after* rebooting in the
> reconfigured system? That could well be a GuixSD bug, indeed.
No, it happens after second 'guix system reconfigure' with howto above.
[...]
Thanks,
Oleg.
This bug report was last modified 3 years and 199 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.