[opensuse-factory] SystemD core dumps since 202010* snapshots
Since my last snapshot upgrade with "zypper dup" I have the problem, that Systemd gets a core dump after "systemctl" calls. This my command line: zypper ref; zypper dup; a2dismod mod_php7; systemctl disable sendmail; systemctl stop sendmail; The core dump looks like this: Oct 15 09:21:59 mybox sendmail[18383]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Address already in use Oct 15 09:21:59 mybox sendmail[18383]: daemon MTA: problem creating SMTP socket Oct 15 09:21:59 mybox sendmail[18383]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: server SMTP socket wedged: exiting Oct 15 09:21:59 mybox rsyslogd[1031]: action 'action-38-builtin:ompipe' suspended (module 'builtin:ompipe'), next retry is Thu Oct 15 09:22:29 2> Oct 15 09:22:01 mybox systemd[1]: Reloading. Oct 15 09:22:01 mybox systemd[1]: Assertion 'hashmap_isempty(m->jobs)' failed at src/core/manager.c:1335, function manager_clear_jobs_and_units(> Oct 15 09:22:01 mybox systemd-coredump[19861]: Due to PID 1 having crashed coredump collection will now be turned off. Oct 15 09:22:01 mybox systemd[1]: Caught <ABRT>, dumped core as pid 19860. Oct 15 09:22:01 mybox systemd[1]: Freezing execution. Oct 15 09:22:01 mybox systemd-coredump[19861]: Process 19860 (systemd) of user 0 dumped core. Stack trace of thread 19860: #0 0x00007f21bbbbb917 kill (libc.so.6 + 0x3d917) #1 0x0000558644b3acdf n/a (systemd + 0x3dcdf) #2 0x00007f21bbbbb6c0 __restore_rt (libc.so.6 + 0x3d6c0) #3 0x00007f21bbbbb641 raise (libc.so.6 + 0x3d641) #4 0x00007f21bbba4538 abort (libc.so.6 + 0x26538) #5 0x00007f21bbef75be n/a (libsystemd-shared-246.so + 0x635be) #6 0x0000558644b7e8b8 n/a (systemd + 0x818b8) #7 0x0000558644b39dba n/a (systemd + 0x3cdba) #8 0x00007f21bbba5e0a __libc_start_main (libc.so.6 + 0x27e0a) #9 0x0000558644b3a86a n/a (systemd + 0x3d86a) I am unsure which snapshot caused this problem. I skipped some snapshots because of the keyboard layout problem (#1177545). Currently I have snapshot 20201012. Anyone else with this problem? Greetings, Björn -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Björn,
Bjoern Voigt
Since my last snapshot upgrade with "zypper dup" I have the problem, that Systemd gets a core dump after "systemctl" calls.
This my command line: zypper ref; zypper dup; a2dismod mod_php7; systemctl disable sendmail; systemctl stop sendmail;
The core dump looks like this: Oct 15 09:21:59 mybox sendmail[18383]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: cannot bind: Address already in use Oct 15 09:21:59 mybox sendmail[18383]: daemon MTA: problem creating SMTP socket Oct 15 09:21:59 mybox sendmail[18383]: NOQUEUE: SYSERR(root): opendaemonsocket: daemon MTA: server SMTP socket wedged: exiting Oct 15 09:21:59 mybox rsyslogd[1031]: action 'action-38-builtin:ompipe' suspended (module 'builtin:ompipe'), next retry is Thu Oct 15 09:22:29 2> Oct 15 09:22:01 mybox systemd[1]: Reloading. Oct 15 09:22:01 mybox systemd[1]: Assertion 'hashmap_isempty(m->jobs)' failed at src/core/manager.c:1335, function manager_clear_jobs_and_units(> Oct 15 09:22:01 mybox systemd-coredump[19861]: Due to PID 1 having crashed coredump collection will now be turned off. Oct 15 09:22:01 mybox systemd[1]: Caught <ABRT>, dumped core as pid 19860. Oct 15 09:22:01 mybox systemd[1]: Freezing execution. Oct 15 09:22:01 mybox systemd-coredump[19861]: Process 19860 (systemd) of user 0 dumped core.
Stack trace of thread 19860: #0 0x00007f21bbbbb917 kill (libc.so.6 + 0x3d917) #1 0x0000558644b3acdf n/a (systemd + 0x3dcdf) #2 0x00007f21bbbbb6c0 __restore_rt (libc.so.6 + 0x3d6c0) #3 0x00007f21bbbbb641 raise (libc.so.6 + 0x3d641) #4 0x00007f21bbba4538 abort (libc.so.6 + 0x26538) #5 0x00007f21bbef75be n/a (libsystemd-shared-246.so + 0x635be) #6 0x0000558644b7e8b8 n/a (systemd + 0x818b8) #7 0x0000558644b39dba n/a (systemd + 0x3cdba) #8 0x00007f21bbba5e0a __libc_start_main (libc.so.6 + 0x27e0a) #9 0x0000558644b3a86a n/a (systemd + 0x3d86a)
I am unsure which snapshot caused this problem. I skipped some snapshots because of the keyboard layout problem (#1177545). Currently I have snapshot 20201012.
Anyone else with this problem?
I have not seen this issue. I can only suggest that you install
systemd's debuginfo to get a better stacktrace and open a bug.
Cheers,
Dan
--
Dan Čermák
participants (2)
-
Bjoern Voigt -
Dan Čermák