[Bug 1229028] New: dracut-sshd crashing when connecting to host
https://bugzilla.suse.com/show_bug.cgi?id=1229028 Bug ID: 1229028 Summary: dracut-sshd crashing when connecting to host Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs@suse.de Reporter: holgi@suse.com QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 876585 --> https://bugzilla.suse.com/attachment.cgi?id=876585&action=edit dracut-output.txt I installed dracut-sshd, added files /etc/systemd/network/20-wired.network /etc/dracut.conf.d/90-networkd.conf and created initrd again (see output of dracut -f -v). After reboot I can connect from another host to the system, but after connection is being enabled, shell is terminating with error: munmap_chunk(): invalid pointer That lead me to: https://github.com/dracutdevs/dracut/issues/2661 and https://github.com/gsauthof/dracut-sshd/pull/79 but even using the package from https://build.opensuse.org/package/show/home:darix:apps/dracut-sshd did not improve the situation (same errors) On the journalctl I can see the message: Aug 09 10:35:19 asus (sshd[221]: sshd.service: Referenced but unset environment variable evaluates to an empty string: CRYPTO_POLICY, OPTIONS ... Aug 09 10:35:20 asus sshd[221]: Server listening on 0.0.0.0 port 22. Aug 09 10:35:20 asus sshd[221]: Server listening on :: port 22. Aug 09 10:35:20 asus systemd[1]: Started OpenSSH server daemon. ... Aug 09 10:35:26 asus kernel: NET: Registered PF_PACKET protocol family Aug 09 10:35:26 asus kernel: sdj: sdj1 Aug 09 10:35:26 asus kernel: sd 7:0:0:0: [sdj] Attached SCSI disk Aug 09 10:35:23 asus systemd-networkd[623]: eth0: Gained carrier Aug 09 10:35:23 asus systemd-networkd[623]: eth0: found matching network '/etc/systemd/network/20-wired.network', based on potentially unpredictable interface name. Aug 09 10:35:26 asus systemd-networkd[623]: eth0: Gained IPv6LL Aug 09 10:35:26 asus systemd-networkd[623]: eth0: DHCPv4 address 192.168.0.3/24, gateway 192.168.0.1 acquired from 192.168.0.1 Aug 09 10:35:30 asus sshd[805]: Accepted publickey for root from 192.168.0.14 port 46992 ssh2: RSA SHA256:fQ/WvO6CBX8uzQaDceKKxAYRJRA17sO1sGYtxqle+RM Aug 09 10:35:30 asus kernel: Core dump to |/bin/false pipe failed Aug 09 10:35:30 asus sshd[807]: Received disconnect from 192.168.0.14 port 46992:11: disconnected by user Aug 09 10:35:30 asus sshd[807]: Disconnected from user root 192.168.0.14 port 46992 Aug 09 10:35:35 asus sshd[937]: Accepted publickey for root from 192.168.0.14 port 47000 ssh2: RSA SHA256:fQ/WvO6CBX8uzQaDceKKxAYRJRA17sO1sGYtxqle+RM Aug 09 10:35:35 asus sshd[939]: Received disconnect from 192.168.0.14 port 47000:11: disconnected by user Aug 09 10:35:35 asus sshd[939]: Disconnected from user root 192.168.0.14 port 47000 Aug 09 10:35:35 asus kernel: Core dump to |/bin/false pipe failed -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c1 --- Comment #1 from Holger Sickenberg <holgi@suse.com> --- Created attachment 876586 --> https://bugzilla.suse.com/attachment.cgi?id=876586&action=edit 20-wired.network -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c2 --- Comment #2 from Holger Sickenberg <holgi@suse.com> --- Created attachment 876587 --> https://bugzilla.suse.com/attachment.cgi?id=876587&action=edit 90-networkd.conf -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 Holger Sickenberg <holgi@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mrueckert@suse.com Found By|--- |Development Hardware|Other |x86-64 Assignee|screening-team-bugs@suse.de |antonio.feijoo@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c3 Antonio Feijoo <antonio.feijoo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|antonio.feijoo@suse.com |dracut-maintainers@suse.de --- Comment #3 from Antonio Feijoo <antonio.feijoo@suse.com> --- (In reply to Holger Sickenberg from comment #0)
That lead me to: https://github.com/dracutdevs/dracut/issues/2661 and https://github.com/gsauthof/dracut-sshd/pull/79 but even using the package from https://build.opensuse.org/package/show/home:darix:apps/dracut-sshd did not improve the situation (same errors)
This is a fix for OpenSSH 9.8, so this cannot be the problem (you're using Leap 15.6, and Tumbleweed does not ship this version yet).
After reboot I can connect from another host to the system, but after connection is being enabled, shell is terminating with error: munmap_chunk(): invalid pointer
This can be an error in openssh or systemd-networkd?. You haven't attached the journalctl log. I have some pending work to do after my vacation, I'll take a look at it when I have time and try to reproduce it. Meanwhile, could you try setting up `network-legacy` or `network-manager` instead of `systemd-networkd`? In these cases it should not be necessary to install something like `20-wired.network`, adding `ip=eth0:dhcp` to the kernel command line should be sufficient. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c4 --- Comment #4 from Holger Sickenberg <holgi@suse.com> --- I added parts of the journalctl to my initial comment. If necessary I can add full journalctl as well. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c5 Antonio Feijoo <antonio.feijoo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |antonio.feijoo@suse.com --- Comment #5 from Antonio Feijoo <antonio.feijoo@suse.com> --- I failed to reproduce your issue using both systemd-networkd and network-legacy. Since we don't use systemd-networkd a lot (in fact on my tests it caused eth0 to have 2 different IP addresses) and mostly we support wicked (network-legacy) and NetworkManager, could you try again using one of both dracut modules? - Comment the current content of /etc/dracut.conf.d/90-networkd.conf and add the following lines (replace network-legacy with network-manager if you're using NetworkManager on your system and not wicked):
kernel_cmdline="rd.neednet ip=eth0:dhcp" add_dracutmodules+=" network network-legacy "
- Rebuild the initrd (dracut -f) and try again. If you still get the same error, please attach the full journal log, to check what process is core dumping. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c6 --- Comment #6 from Holger Sickenberg <holgi@suse.com> --- Created attachment 877036 --> https://bugzilla.suse.com/attachment.cgi?id=877036&action=edit journalctl with debug I think the network is up with systemd-networkd. Maybe a possible reason: I installed without recommended packages, might there miss some package? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c7 --- Comment #7 from Antonio Feijoo <antonio.feijoo@suse.com> --- Thanks for the logs. So it's sshd:
Aug 30 09:53:39 asus sshd[2025]: Accepted publickey for root from 192.168.0.14 port 48240 ssh2: RSA SHA256:fQ/WvO6CBX8uzQaDceKKxAYRJRA17sO1sGYtxqle+RM Aug 30 09:53:39 asus sshd[2027]: Received disconnect from 192.168.0.14 port 48240:11: disconnected by user Aug 30 09:53:39 asus sshd[2027]: Disconnected from user root 192.168.0.14 port 48240 Aug 30 09:53:39 asus systemd[1]: Received SIGCHLD from PID 2027 (sshd). Aug 30 09:53:39 asus kernel: Core dump to |/bin/false pipe failed Aug 30 09:53:39 asus systemd[1]: Child 2027 (sshd) died (code=exited, status=255/EXCEPTION) Aug 30 09:53:39 asus systemd[1]: sshd.service: Child 2027 belongs to sshd.service.
Now there are 2 options: - First I would check if you can ssh to your machine _after_ the system is completely booted (i.e., not on the initrd). If this fails, there is an issue in sshd. - If that does not fail, then there should be some missing dependency/library in the initrd. If you have direct access to this machine, could you add `rd.break` to the kernel command line (this stops the boot process before switching root and displays the emergency shell), try to connect from another system to create the failure, and then get the output of `systemctl status sshd.service` from the emergency shell to check if it provides more useful info? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c8 --- Comment #8 from Holger Sickenberg <holgi@suse.com> --- Yes, ssh to machine when completely booted is working fine. For me it looks like ssh during boot is also working but after being connected, something crashes and connection will terminated. I can ssh again and same effect. Will try the "rd.break" option when at home. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c9 --- Comment #9 from Holger Sickenberg <holgi@suse.com> --- Created attachment 877128 --> https://bugzilla.suse.com/attachment.cgi?id=877128&action=edit bug.screenshot.jpg -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c10 --- Comment #10 from Holger Sickenberg <holgi@suse.com> --- Not really much more information -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c11 --- Comment #11 from Antonio Feijoo <antonio.feijoo@suse.com> --- (In reply to Holger Sickenberg from comment #10)
Not really much more information
Yes, let's try to get the core dump. Steps: - If you don't have `systemd-coredump` installed in your system, install it. - Add systemd-coredump to the initrd: `dracut -f -a systemd-coredump` - Boot adding `rd.break` to the kernel command line. - Connect via ssh to this machine to cause the core dump. - From the emergency shell, the core dump file should be located in /var/lib/systemd/coredump/, but /var is not persistent on the initrd, so you have to: # mount -o remount,rw /sysroot # cp /var/lib/systemd/coredump/* /sysroot/var/lib/systemd/coredump - After booting the system, you can get the core dump and attach it here. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c12 --- Comment #12 from Antonio Feijoo <antonio.feijoo@suse.com> --- (In reply to Antonio Feijoo from comment #11)
- Boot adding `rd.break` to the kernel command line.
I forgot to mention, please add also `systemd.log_level=debug` to the kernel command line, just in case systemd is the one to blame, so we have a finer journal. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c13 --- Comment #13 from Holger Sickenberg <holgi@suse.com> --- Created attachment 877169 --> https://bugzilla.suse.com/attachment.cgi?id=877169&action=edit core.sh.0.6cef12651cef4d20886ce1ee7d5f7f72.3060.1725611441000000.zst Here is the coredump -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c14 --- Comment #14 from Antonio Feijoo <antonio.feijoo@suse.com> --- (In reply to Holger Sickenberg from comment #13)
Created attachment 877169 [details] core.sh.0.6cef12651cef4d20886ce1ee7d5f7f72.3060.1725611441000000.zst
Here is the coredump
Thanks! Could you confirm if `terminfo-base` is installed correctly? Please, check the output of `rpm -ql terminfo-base` and `sudo lsinitrd | grep terminfo` -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c15 --- Comment #15 from Holger Sickenberg <holgi@suse.com> --- asus:/tmp # rpm -ql terminfo-base /etc/termcap /etc/terminfo /usr/share/misc/termcap /usr/share/tabset /usr/share/tabset/std /usr/share/tabset/stdcrt /usr/share/tabset/vt100 /usr/share/tabset/vt300 /usr/share/terminfo /usr/share/terminfo/1 /usr/share/terminfo/2 /usr/share/terminfo/3 /usr/share/terminfo/4 /usr/share/terminfo/5 /usr/share/terminfo/6 /usr/share/terminfo/7 /usr/share/terminfo/8 /usr/share/terminfo/9 /usr/share/terminfo/A /usr/share/terminfo/E /usr/share/terminfo/L /usr/share/terminfo/M /usr/share/terminfo/N /usr/share/terminfo/P /usr/share/terminfo/Q /usr/share/terminfo/X /usr/share/terminfo/a /usr/share/terminfo/a/ansi /usr/share/terminfo/a/arpanet /usr/share/terminfo/b /usr/share/terminfo/c /usr/share/terminfo/d /usr/share/terminfo/d/dialup /usr/share/terminfo/d/dumb /usr/share/terminfo/e /usr/share/terminfo/f /usr/share/terminfo/g /usr/share/terminfo/g/gnome /usr/share/terminfo/g/gnome-fc5 /usr/share/terminfo/g/gnome-rh72 /usr/share/terminfo/g/gnome-rh80 /usr/share/terminfo/g/gnome-rh90 /usr/share/terminfo/h /usr/share/terminfo/i /usr/share/terminfo/i/ibm327x /usr/share/terminfo/j /usr/share/terminfo/k /usr/share/terminfo/k/klone+color /usr/share/terminfo/k/konsole /usr/share/terminfo/k/konsole-256color /usr/share/terminfo/k/kvt /usr/share/terminfo/k/kvt-rh /usr/share/terminfo/l /usr/share/terminfo/l/linux /usr/share/terminfo/l/linux-m /usr/share/terminfo/l/linux-nic /usr/share/terminfo/m /usr/share/terminfo/m/mlterm /usr/share/terminfo/n /usr/share/terminfo/n/net /usr/share/terminfo/n/network /usr/share/terminfo/n/nxterm /usr/share/terminfo/o /usr/share/terminfo/p /usr/share/terminfo/p/patch /usr/share/terminfo/q /usr/share/terminfo/r /usr/share/terminfo/r/rxvt /usr/share/terminfo/r/rxvt-256color /usr/share/terminfo/r/rxvt-basic /usr/share/terminfo/r/rxvt-color /usr/share/terminfo/r/rxvt-unicode /usr/share/terminfo/r/rxvt-unicode-256color /usr/share/terminfo/s /usr/share/terminfo/s/screen /usr/share/terminfo/s/screen+fkeys /usr/share/terminfo/s/screen-16color /usr/share/terminfo/s/screen-256color /usr/share/terminfo/s/screen-bce /usr/share/terminfo/s/screen-w /usr/share/terminfo/s/sun /usr/share/terminfo/s/switch /usr/share/terminfo/t /usr/share/terminfo/u /usr/share/terminfo/u/unknown /usr/share/terminfo/v /usr/share/terminfo/v/vt100 /usr/share/terminfo/v/vt102 /usr/share/terminfo/v/vt220 /usr/share/terminfo/v/vt220-8 /usr/share/terminfo/v/vt220-8bit /usr/share/terminfo/v/vt320 /usr/share/terminfo/v/vt52 /usr/share/terminfo/v/vte /usr/share/terminfo/w /usr/share/terminfo/x /usr/share/terminfo/x/xterm /usr/share/terminfo/x/xterm-256color /usr/share/terminfo/x/xterm-basic /usr/share/terminfo/x/xterm-color /usr/share/terminfo/x/xterm-nic /usr/share/terminfo/x/xterm-r6 /usr/share/terminfo/z asus:/tmp # sudo lsinitrd | grep terminfo terminfo drwxr-xr-x 4 root root 0 Sep 5 14:22 usr/share/terminfo drwxr-xr-x 2 root root 0 Sep 5 14:22 usr/share/terminfo/l -rw-r--r-- 1 root root 1822 Feb 19 2024 usr/share/terminfo/l/linux drwxr-xr-x 2 root root 0 Sep 5 14:22 usr/share/terminfo/v -rw-r--r-- 1 root root 1190 Feb 19 2024 usr/share/terminfo/v/t100 -rw-r--r-- 1 root root 1184 Feb 19 2024 usr/share/terminfo/v/t102 -rw-r--r-- 1 root root 1377 Feb 19 2024 usr/share/terminfo/v/t220 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c16 --- Comment #16 from Antonio Feijoo <antonio.feijoo@suse.com> --- (In reply to Holger Sickenberg from comment #15)
asus:/tmp # rpm -ql terminfo-base ... /usr/share/terminfo/v/vt100 /usr/share/terminfo/v/vt102 /usr/share/terminfo/v/vt220 ...
asus:/tmp # sudo lsinitrd | grep terminfo terminfo ... -rw-r--r-- 1 root root 1190 Feb 19 2024 usr/share/terminfo/v/t100 -rw-r--r-- 1 root root 1184 Feb 19 2024 usr/share/terminfo/v/t102 -rw-r--r-- 1 root root 1377 Feb 19 2024 usr/share/terminfo/v/t220
This is a typo, right? these three files listed with `lsinitrd` should be `vt100`, `vt102` and `vt220`. If it's not a typo, it would explain the error. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c17 --- Comment #17 from Antonio Feijoo <antonio.feijoo@suse.com> --- FTR, the backtrace shows what the problem is:
(gdb) bt #0 0x00007f5220c944ac in __pthread_kill_implementation () from /lib64/libc.so.6 #1 0x00007f5220c428c2 in raise () from /lib64/libc.so.6 #2 0x00007f5220c2a6d9 in abort () from /lib64/libc.so.6 #3 0x00007f5220c2b517 in __libc_message.cold () from /lib64/libc.so.6 #4 0x00007f5220c9eb67 in malloc_printerr () from /lib64/libc.so.6 #5 0x00007f5220c9ee8c in munmap_chunk () from /lib64/libc.so.6 #6 0x00007f5220ca38da in free () from /lib64/libc.so.6 #7 0x00007f52210d937c in really_free_termtype (ptr=0x5624b20e8420, freeStrings=<optimized out>) at ../ncurses/./tinfo/free_ttype.c:55 #8 0x00007f52210d940a in _nc_free_termtype2 (ptr=<optimized out>) at ../ncurses/./tinfo/free_ttype.c:81 #9 0x00007f52210d9e5f in del_curterm_sp (sp=sp@entry=0x0, termp=termp@entry=0x5624b20e8350) at ../ncurses/./tinfo/lib_cur_term.c:150 #10 0x00007f52210dc922 in tgetent_sp (sp=0x0, bufp=0x5624b20e7350 "", name=name@entry=0x5624b20f7a40 "vt220") at ../ncurses/./tinfo/lib_termcap.c:136 #11 0x00007f52210dd115 in tgetent (bufp=<optimized out>, name=name@entry=0x5624b20f7a40 "vt220") at ../ncurses/./tinfo/lib_termcap.c:211 #12 0x00007f5220e3296c in _rl_init_terminal_io (terminal_name=<optimized out>) at ../terminal.c:488 #13 0x00007f5220e32d53 in rl_reset_terminal (terminal_name=<optimized out>) at ../terminal.c:631 #14 0x00005624b0e9a0f9 in do_assignment_internal (word=word@entry=0x7ffce5c99a70, expand=expand@entry=0) at subst.c:3183 #15 0x00005624b0ec490a in do_assignment_no_expand (string=string@entry=0x5624b20f8040 "TERM=vt220") at subst.c:3236 #16 0x00005624b0eab59e in set_or_show_attributes (nodefs=0, attribute=1, list=0x5624b20f80a0) at ./setattr.def:274 #17 export_builtin (list=<optimized out>) at ./setattr.def:81 #18 0x00005624b0e84c2b in execute_builtin (words=0x5624b20f80e0, subshell=0, flags=0, builtin=0x5624b0eab3c0 <export_builtin>) at execute_cmd.c:4539 #19 execute_builtin_or_function (flags=<optimized out>, fds_to_close=0x5624b0e84c2b <execute_simple_command+1243>, redirects=<optimized out>, var=<optimized out>, builtin=<optimized out>, words=0x5624b20f80e0) at execute_cmd.c:5032 #20 execute_simple_command (simple_command=<optimized out>, pipe_in=pipe_in@entry=-1, pipe_out=pipe_out@entry=-1, async=async@entry=0, fds_to_close=fds_to_close@entry=0x5624b20f7a80) at execute_cmd.c:4334 #21 0x00005624b0e8355d in execute_command_internal (command=0x5624b20f8360, asynchronous=0, pipe_in=-1, pipe_out=-1, fds_to_close=0x5624b20f7a80) at execute_cmd.c:811 #22 0x00005624b0e846d1 in execute_command (command=0x5624b20f8360) at execute_cmd.c:405 #23 0x00005624b0e84506 in execute_if_command (if_command=<optimized out>) at execute_cmd.c:3561 #24 execute_command_internal (command=0x5624b20f8390, asynchronous=asynchronous@entry=0, pipe_in=pipe_in@entry=-1, pipe_out=pipe_out@entry=-1, fds_to_close=fds_to_close@entry=0x5624b20f7c20) at execute_cmd.c:932 #25 0x00005624b0ea9896 in parse_and_execute (string=<optimized out>, from_file=from_file@entry=0x5624b20f7120 "/root/.profile", flags=flags@entry=20) at evalstring.c:421 #26 0x00005624b0ecad7c in _evalfile (filename=filename@entry=0x5624b20f7120 "/root/.profile", flags=flags@entry=9) at evalfile.c:289 #27 0x00005624b0e5f946 in maybe_execute_file (fname=fname@entry=0x5624b0eceeaa "~/.profile", force_noninteractive=1) at evalfile.c:334 #28 0x00005624b0e22370 in run_startup_files () at shell.c:1134 #29 main (argc=1, argv=0x7ffce5c9a4e8, env=0x7ffce5c9a4f8) at shell.c:684
I can reproduce your issue if I manually export a terminal _not_ available on the initrd:
initramfs-ssh:/root# cat .profile if [ -n "$SSH_TTY" ]; then export PS1='initramfs-ssh:${PWD}# ' fi
if [ -n "$TERM" ]; then export TERM=vt220 fi initramfs-ssh:/root# echo $TERM vt220 initramfs-ssh:/root# ls -l /usr/share/terminfo/v total 12 -rw-r--r-- 1 root root 1190 Feb 19 2024 vt100 -rw-r--r-- 1 root root 1184 Feb 19 2024 vt102 -rw-r--r-- 1 root root 1377 Feb 19 2024 vt220 initramfs-ssh:/root# export TERM=vt100 initramfs-ssh:/root# export TERM=dumb initramfs-ssh:/root# export TERM=xterm munmap_chunk(): invalid pointer Connection to 192.168.122.80 closed. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c18 --- Comment #18 from Holger Sickenberg <holgi@suse.com> --- (In reply to Antonio Feijoo from comment #16)
(In reply to Holger Sickenberg from comment #15)
asus:/tmp # rpm -ql terminfo-base ... /usr/share/terminfo/v/vt100 /usr/share/terminfo/v/vt102 /usr/share/terminfo/v/vt220 ...
asus:/tmp # sudo lsinitrd | grep terminfo terminfo ... -rw-r--r-- 1 root root 1190 Feb 19 2024 usr/share/terminfo/v/t100 -rw-r--r-- 1 root root 1184 Feb 19 2024 usr/share/terminfo/v/t102 -rw-r--r-- 1 root root 1377 Feb 19 2024 usr/share/terminfo/v/t220
This is a typo, right? these three files listed with `lsinitrd` should be `vt100`, `vt102` and `vt220`. If it's not a typo, it would explain the error.
I will double check when I'm in front of the system if this was a copy&paste error. From remote (via ssh) the output is correct: holger@asus:~> sudo lsinitrd | grep terminfo terminfo drwxr-xr-x 4 root root 0 Sep 5 14:22 usr/share/terminfo drwxr-xr-x 2 root root 0 Sep 5 14:22 usr/share/terminfo/l -rw-r--r-- 1 root root 1822 Feb 19 2024 usr/share/terminfo/l/linux drwxr-xr-x 2 root root 0 Sep 5 14:22 usr/share/terminfo/v -rw-r--r-- 1 root root 1190 Feb 19 2024 usr/share/terminfo/v/vt100 -rw-r--r-- 1 root root 1184 Feb 19 2024 usr/share/terminfo/v/vt102 -rw-r--r-- 1 root root 1377 Feb 19 2024 usr/share/terminfo/v/vt220 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c23 --- Comment #23 from Antonio Feijoo <antonio.feijoo@suse.com> --- (In reply to Dr. Werner Fink from comment #20)
Aug 30 09:53:39 asus kernel: Core dump to |/bin/false pipe failed ^^^^^^^^^^ /bin/false ... somehow strange
By default systemd-coredump is not included in the initrd, requested in comment #11
Aug 30 09:53:39 asus systemd[1]: Child 2027 (sshd) died (code=exited, status=255/EXCEPTION) Aug 30 09:53:39 asus systemd[1]: sshd.service: Child 2027 belongs to sshd.service.
May I asked which shell is configured in initrd for conenctions via sshd?
I should be bash, at least that is the default: initramfs-ssh:/root# ls -l /usr/bin/sh lrwxrwxrwx 1 root root 4 Aug 21 09:19 /usr/bin/sh -> bash
And for which user (guess the only available user root)?
Yes, only root.
Maybe adding an /root/.ssh/authorized_keys file in the initrd could help sshd in the initrd
I never tried this module without an authorized_keys file and I don't think that it works without that (at least it's logged a fatal error if it's not present when the initrd is built). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 Santiago Zarate <santiago.zarate@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |santiago.zarate@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c24 --- Comment #24 from Antonio Feijoo <antonio.feijoo@suse.com> --- I found a similar backtrace (even the line numbers in the source code) with similar symptoms in this old thread (reporter's name sounds familiar), compare it with comment #17: https://lists.libreplanet.org/archive/html/bug-ncurses/2019-03/msg00023.html -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c27 Antonio Feijoo <antonio.feijoo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|dracut-maintainers@suse.de |werner@suse.com --- Comment #27 from Antonio Feijoo <antonio.feijoo@suse.com> --- (In reply to Dr. Werner Fink from comment #26)
Created attachment 877209 [details] ncurses-6.1-boo1229028.patch -- Allow that later on the terminal based on fallback can be freed!
This one allocs memory for the terminal description based on static fallback entries hence we can it free later on without segfault.
Thanks! I pass the baton to you, as this would not require any fix on the dracut side (for now). -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1229028 https://bugzilla.suse.com/show_bug.cgi?id=1229028#c30 --- Comment #30 from Maintenance Automation <maint-coord+maintenance-robot@suse.de> --- SUSE-RU-2024:3300-1: An update that has one fix can now be installed. URL: https://www.suse.com/support/update/announcement/2024/suse-ru-20243300-1 Category: recommended (moderate) Bug References: 1229028 Maintenance Incident: [SUSE:Maintenance:35592](https://smelt.suse.de/incident/35592/) Sources used: openSUSE Leap Micro 5.5 (src): ncurses-6.1-150000.5.27.1 openSUSE Leap 15.5 (src): ncurses-6.1-150000.5.27.1 openSUSE Leap 15.6 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise Micro for Rancher 5.3 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise Micro 5.3 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise Micro for Rancher 5.4 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise Micro 5.4 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise Micro 5.5 (src): ncurses-6.1-150000.5.27.1 Basesystem Module 15-SP5 (src): ncurses-6.1-150000.5.27.1 Basesystem Module 15-SP6 (src): ncurses-6.1-150000.5.27.1 Development Tools Module 15-SP5 (src): ncurses-6.1-150000.5.27.1 Development Tools Module 15-SP6 (src): ncurses-6.1-150000.5.27.1 Legacy Module 15-SP5 (src): ncurses-6.1-150000.5.27.1 Legacy Module 15-SP6 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise High Performance Computing 15 SP2 LTSS 15-SP2 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise High Performance Computing LTSS 15 SP3 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise High Performance Computing ESPOS 15 SP4 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise High Performance Computing LTSS 15 SP4 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise Desktop 15 SP4 LTSS 15-SP4 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise Server 15 SP2 LTSS 15-SP2 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise Server 15 SP3 LTSS 15-SP3 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise Server 15 SP4 LTSS 15-SP4 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise Server for SAP Applications 15 SP2 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise Server for SAP Applications 15 SP3 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise Server for SAP Applications 15 SP4 (src): ncurses-6.1-150000.5.27.1 SUSE Manager Proxy 4.3 (src): ncurses-6.1-150000.5.27.1 SUSE Manager Retail Branch Server 4.3 (src): ncurses-6.1-150000.5.27.1 SUSE Manager Server 4.3 (src): ncurses-6.1-150000.5.27.1 SUSE Enterprise Storage 7.1 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise Micro 5.1 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise Micro 5.2 (src): ncurses-6.1-150000.5.27.1 SUSE Linux Enterprise Micro for Rancher 5.2 (src): ncurses-6.1-150000.5.27.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com