[Bug 727771] New: systemd: shuts down network for no reason
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c0
Summary: systemd: shuts down network for no reason
Classification: openSUSE
Product: openSUSE 12.1
Version: Factory
Platform: Other
OS/Version: Other
Status: NEW
Severity: Major
Priority: P5 - None
Component: Basesystem
AssignedTo: bnc-team-screening@forge.provo.novell.com
ReportedBy: jslaby@suse.com
QAContact: qa@suse.de
CC: fcrozat@suse.com
Blocks: 696902
Found By: ---
Blocker: ---
When booting with systemd (sysvinit is OK), I have no network.
With sysvinit:
2: eth0:
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c1
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c2
--- Comment #2 from Jiri Slaby
could you post dmesg output after booting with systemd.log_level=debug systemd.log_target=kmsg ?
Sure. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c3
--- Comment #3 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c4
--- Comment #4 from Jiri Slaby
systemctl show network.service | grep RemainAfterExit
RemainAfterExit=no -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c
Andreas Jaeger
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c5
--- Comment #5 from Danny van Delft
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c6
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c7
--- Comment #7 from Danny van Delft
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c8
--- Comment #8 from Ludwig Nussel
So, we need to add one or two LSB extra headers to tell systemd this service should stay as "RemainAfterExit".
I propose adding
X-Remain-After-Exit: yes/no
X-Pidfile:
Sounds good. Although it should be X-Systemd or X-SUSE I guess. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c9
--- Comment #9 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c10
--- Comment #10 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c11
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c12
--- Comment #12 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c13
--- Comment #13 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c14
--- Comment #14 from Jiri Slaby
I've pushed support for PIDFile and X-Systemd-RemainAfterExit in home:fcrozat:systemd / systemd
please test (and add X-Systemd-RemainAfterExit: true in /etc/init.d/network header)
Looks OK. But is this normal? 30635ms bootsplash-quit.service 4999ms network.service 1158ms apparmor.service There is no splash here... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c
Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c15
--- Comment #15 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c16
--- Comment #16 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c17
J. Daniel Schmidt
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c18
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c19
--- Comment #19 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c20
--- Comment #20 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c21
--- Comment #21 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c23
Till Dörges
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c24
Cristian Rodríguez
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c25
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c26
Marius Tomaschewski
12.1 maintenance update has been released for systemd
Now, we need a maintenance update for sysconfig (reopening bug report until everything is fixed in 12.1)
Marius, could you handle it ? I see on OBS some other sr (#97040, #97208) are pending regarding sysconfig. Maybe we should integrate the systemd fix in the same update ?
I'd not disturb the running updates. Further, I'm still testing some issues -- going to branch sysconfig and I'll apply all patches to home:mtomaschewski:branches:openSUSE:12.1:Update:Test. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c27
--- Comment #27 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c28
Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c29
--- Comment #29 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c30
--- Comment #30 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c31
Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c32
Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c33
EDSS Virtual
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c34
Morten Bjoernsvik
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c35
--- Comment #35 from Marius Tomaschewski
Hi
I have the same problem, but the fix has been revoked, So I'm unable to test.
Which fix has been revoked?
For me it works if I add: #/etc/init.d/network start -o debug
This works because there is no systemd involved / no redirection done by the /etc/rc.status script because of this guard: if test $PPID -ne 1 -a $# -eq 1 ; then [when not started by systemd and only one arg given -> redirect to systemd] but it causes another problem: systemd does not know anything about your start and continue to consider it dead/failed/not yet started, even a "rcnetwork status -o" will show it started. The problem (part of) is IMO, that systemd a) tries to resolve dependencies [generally a good thing], b) does not use status reported by the LSB scripts (does not call /etc/init.d/network status), but own meaning instead. Further, there is IMO no way to tell let it refresh the systemd state, e.g. via "systemctl reset-failed". It is seems to not work for LSB scripts, e.g. by executing the LSB status action... Additional problems may be caused by hooks installed by samba-client or ntp, that cause a systemd deadlock by executing init scripts that depend from the network script via hooks inside of the network scripts (if-up.d, ...), see bug 732930 alias bug 732395 alias bug 725503 alias ... Workarounds are (until release of fixes for samba-client, ...): - move the /etc/sysconfig/network/if-*.d/21* links away - remove ntp-runtime from NETCONFIG_MODULES_ORDER in /etc/sysconfig/network/config. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c36
--- Comment #36 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c37
Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c38
Danny van Delft
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c39
--- Comment #39 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c40
Michal Filka
rpm -q sysconfig systemd sysconfig-0.75.4-2.7.1.x86_64 systemd-37-3.11.1.x86_64
Doesn't work: Change from DHCP -> static IP (using YaST; network service not running after change)
/etc/init.d/network status redirecting to systemctl network.service - LSB: Configure the localfs depending network interfaces Loaded: loaded (/etc/init.d/network) Active: inactive (dead) since Thu, 05 Apr 2012 12:35:44 +0200; 8s ago Process: 6709 ExecStop=/etc/init.d/network stop (code=exited, status=0/SUCCESS) Process: 6099 ExecReload=/etc/init.d/network reload (code=exited, status=0/SUCCESS) Process: 5452 ExecStart=/etc/init.d/network start (code=exited, status=0/SUCCESS) Works: configured with static IP (doesn't matter if network service runs or nor), after reboot network service runs.
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c41
--- Comment #41 from Michal Filka
After which a manual ifup eth0 at the console was needed :-(
Just an idea ... do you have samba-client installed? There is an issue related to starting network during boot in such case. bnc#745859 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c42
--- Comment #42 from Danny van Delft
(In reply to comment #38)
After which a manual ifup eth0 at the console was needed :-(
Just an idea ... do you have samba-client installed? There is an issue related to starting network during boot in such case. bnc#745859
Not at the faulty boot. Prior to this boot, I had done a zypper up. Just prior to that I had removed some unneeded packages, amongst which samba-client (which was not in use anyway, but that seems irrelevant for bnc#745859). So it was installed at boot time when the machine was up and running, then removed, then zypper up-ed, then rebooted which then failed. However, in accordance to #c39, I have tried to get the output as requested. Since then this (virtual) machine has been rebooted some 120 times, without failing the network setup. Perhaps the extra debugging output "fixes" the problem. I'll try to get the machine into a state where it fails again. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c43
Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c44
Danny van Delft
could you also try to downgrade to systemd-37-3.8.1 (from upgrade repository) to see if it fixes your issue ?
At the moment, with systemd-37-3.11.1, I cannot reproduce, even if it did occur the first time I booted with this version. So, me thinks I should first try to reproduce with systemd-37-3.11.1, before downgrading to systemd-37-3.8.1? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c45
--- Comment #45 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c46
--- Comment #46 from Danny van Delft
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c47
--- Comment #47 from Marius Tomaschewski
Note at the time this bz2 was made, the eth0 interface had been manually upped.
That's ok. dmesg.txt: [ 54.196701] systemd[1]: network.service changed start -> running [ 54.196710] systemd[1]: Job network.service/start finished, result=done [ 54.196983] systemd[1]: network.target changed dead -> active [ 54.196989] systemd[1]: Job network.target/start finished, result=done [ 54.196997] systemd[1]: remote-fs-pre.target changed dead -> active [ 54.197002] systemd[1]: Job remote-fs-pre.target/start finished, result=done ... [ 54.213945] systemd[1]: About to execute: /etc/init.d/mysql start [ 54.218964] systemd[1]: Forked /etc/init.d/mysql as 1547 [ 54.218998] systemd[1]: mysql.service changed dead -> start ... [ 54.484353] systemd[1]: network.service: cgroup is empty [ 54.484396] systemd[1]: About to execute: /etc/init.d/network stop [ 54.489237] systemd[1]: Forked /etc/init.d/network as 1626 [ 54.489286] systemd[1]: network.service changed running -> stop messages.txt: ... Apr 10 08:40:07 roxeli mysql[1547]: /etc/rc.status: line 57: /dev/stderr: No such device or address ... This is from /etc/init.d/mysql -> systemct redirection. A bit strange... Network will be started fine, but then (to resolve deps), systemd is stopping it (see begin of exdeb.network_1626.1._.stop). Hmm... for me it looks like a problem with dependencies and there is the "network.service: cgroup is empty" message before it gets stopped. Something about mysql.service? Going to install it and take a look. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c48
Per Jessen
messages.txt: ... Apr 10 08:40:07 roxeli mysql[1547]: /etc/rc.status: line 57: /dev/stderr: No such device or address ...
This is from /etc/init.d/mysql -> systemct redirection. A bit strange...
FYI, I see this quite frequently, usually from /etc/init.d/ntp. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c49
--- Comment #49 from Danny van Delft
(In reply to comment #46) ... ... Apr 10 08:40:07 roxeli mysql[1547]: /etc/rc.status: line 57: /dev/stderr: No such device or address ...
This is from /etc/init.d/mysql -> systemct redirection. A bit strange...
Network will be started fine, but then (to resolve deps), systemd is stopping it (see begin of exdeb.network_1626.1._.stop).
Hmm... for me it looks like a problem with dependencies and there is the "network.service: cgroup is empty" message before it gets stopped. Something about mysql.service? Going to install it and take a look.
See https://bugzilla.novell.com/show_bug.cgi?id=728774 where I reported this phenomenon "way back" ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c50
Stefan Kuehne
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c51
--- Comment #51 from Stefan Kuehne
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c52
--- Comment #52 from Stefan Kuehne
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c53
Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c54
--- Comment #54 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c55
--- Comment #55 from H Harun
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c56
--- Comment #56 from Stefan Kuehne
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c57
--- Comment #57 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c58
--- Comment #58 from Frederic Crozat
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c59
--- Comment #59 from Bernhard Wiedemann
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c60
Benjamin Brunner
https://bugzilla.novell.com/show_bug.cgi?id=727771
https://bugzilla.novell.com/show_bug.cgi?id=727771#c61
--- Comment #61 from Swamp Workflow Management
http://bugzilla.novell.com/show_bug.cgi?id=727771
http://bugzilla.novell.com/show_bug.cgi?id=727771#c63
--- Comment #63 from LTC BugProxy
Still the question remains why we only see this on LPAR and not under z/VM. Any idea?
Without X-Systemd-RemainAfterExit this (IMHO) should happen on both *** This bug has been marked as a duplicate of bug 727771 *** -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=727771
LTC BugProxy
http://bugzilla.novell.com/show_bug.cgi?id=727771
http://bugzilla.novell.com/show_bug.cgi?id=727771#c64
--- Comment #64 from LTC BugProxy
http://bugzilla.novell.com/show_bug.cgi?id=727771
http://bugzilla.novell.com/show_bug.cgi?id=727771#c65
--- Comment #65 from LTC BugProxy
Created attachment 100321 [details] testconf
Stripped down version of the dumpconf service:
The "start" function of this service script forks itself as a new background process with parameters "start background" and then exits.
The background process does the following:
1) It creates a PID file "/var/run/testconf.pid" 2) Sleeps for 2 seconds 3) Removes the PID file 4) Exits
Installation:
1) Copy "testconf" init script to /etc/init.d/ 2) Issue: chkconfig --add testconf
Execution:
1) Issue: service testconf start 2) Inspect /tmp/testconf.log
In the log on LPAR I see the following:
PPID=1 PID=24510: start PPID=1 PID=24510: The activation of testconf is being delayed PPID=1 PID=24510: start done PPID=1 PID=24510: exit PPID=1 PID=24516: start PPID=1 PID=24516: The background process PPID=1 PID=24516: sleep: 0 PPID=1 PID=24516: sleep: 1 PPID=1 PID=24516: start done PPID=1 PID=24516: exit PPID=1 PID=24525: stop <--- ???? PPID=1 PID=24525: do stop PPID=1 PID=24525: stop done PPID=1 PID=24525: exit
The question to the SUSE systemd experts is:
Why is systemd calling "testconf stop" (PID=24525) after the testconf background process has exited?
Tested on zEC12 LPAR with SLES12.1-Beta2 kernel 3.12.46-2-default #rpm -qi systemd Name : systemd Version : 210 Release : 73.6 Architecture: s390x Install Date: Tue Aug 25 14:24:37 2015 Group : System/Base Size : 12866072 License : LGPL-2.1+ Signature : RSA/SHA256, Wed Aug 19 04:07:47 2015, Key ID 70af9e8139db7c82 Source RPM : systemd-210-73.6.src.rpm Build Date : Wed Aug 19 04:05:37 2015 Build Host : s390lpd Relocations : (not relocatable) Packager : https://www.suse.com/ Vendor : SUSE LLC https://www.suse.com/ URL : http://www.freedesktop.org/wiki/Software/systemd Summary : A System and Session Manager Description : Systemd is a system and service manager, compatible with SysV and LSB init scripts for Linux. systemd provides aggressive parallelization capabilities, uses socket and D-Bus activation for starting services, offers on-demand starting of daemons, keeps track of processes using Linux cgroups, supports snapshotting and restoring of the system state, maintains mount and automount points and implements an elaborate transactional dependency-based service control logic. It can work as a drop-in replacement for sysvinit. Distribution: SUSE Linux Enterprise 12 tried testconf service #cat /tmp/testconf.log PPID=1 PID=32522: start PPID=1 PID=32522: The activation of testconf is being delayed PPID=1 PID=32522: start done PPID=1 PID=32522: exit PPID=1 PID=32528: start PPID=1 PID=32528: The background process PPID=1 PID=32528: sleep: 0 PPID=1 PID=32528: sleep: 1 PPID=1 PID=32528: start done PPID=1 PID=32528: exit no stop observed. also # cat /etc/sysconfig/dumpconf | grep -v "^#" | grep "=" ON_PANIC="dump_reipl" DELAY_MINUTES="1" DUMP_TYPE="ccw" DEVICE="0.0.7e69" WWPN="" LUN="" BOOTPROG="0" BR_LBA="0" VMCMD_1="" VMCMD_2="" VMCMD_3="" VMCMD_4="" VMCMD_5="" VMCMD_6="" VMCMD_7="" VMCMD_8="" # lsshut Trigger Action ======================== Halt stop Power off stop Reboot reipl Restart dump_reipl Panic dump_reipl # systemctl status dumpconf.service dumpconf.service - LSB: Configure s390 dump feature Loaded: loaded (/etc/init.d/dumpconf) Active: active (exited) since Tue 2015-08-25 11:59:33 MSK; 1min 36s ago Process: 32741 ExecStop=/etc/init.d/dumpconf stop (code=exited, status=0/SUCCESS) Process: 32754 ExecStart=/etc/init.d/dumpconf start (code=exited, status=0/SUCCESS) Aug 25 11:59:33 p23lp33 dumpconf[32754]: The activation of dumpconf is being delayed for 1 minutes Aug 25 11:59:33 p23lp33 systemd[1]: Started LSB: Configure s390 dump feature. no stop observed. # rpm -q systemd s390-tools systemd-210-73.6.s390x s390-tools-1.24.1-43.20.s390x -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com