[opensuse-factory] blogd going 100% at shutdown?
![](https://seccdn.libravatar.org/avatar/184f2936f5d39b27534f4dd7c4d15bfb.jpg?s=120&d=mm&r=g)
I have a Factory system, booting with PXE and root on NFS, which is
having trouble shutting down. I get as far as:
![](https://seccdn.libravatar.org/avatar/184f2936f5d39b27534f4dd7c4d15bfb.jpg?s=120&d=mm&r=g)
Per Jessen wrote:
I have a Factory system, booting with PXE and root on NFS, which is having trouble shutting down. I get as far as:
service network stop Shutting down (localfs) network interfaces: eth0 device: Intel Corporation 82546GB Gigabit Ethernet Co eth0 serves root filesystem. Leave it up. skipped eth1 device: Intel Corporation 82546GB Gigabit Ethernet Co No configuration found for eth1 Nevertheless the interface will be shut down. doneShutting down service (localfs) network . . . . . . . . .done service network done At this point, the shutdown seems to halt, but via a still-logged-in ssh session I see blogd using 100% CPU. It then takes 5-10 minutes (not sure exactly how long, I haven't timed it), and the system finally reboots.
278 seconds from I issue the 'reboot' to the network interface stops responding to pings. Any suggestions as to where to look for a reason for this? -- Per Jessen, Zürich (10.1°C) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/6429caf61ce44b39665ceedf5509170b.jpg?s=120&d=mm&r=g)
maybe you can try doing strace -f -p <PID> of blogd and see what is
really doing all traffic to it.
On Mon, Oct 31, 2011 at 6:06 PM, Per Jessen
Per Jessen wrote:
I have a Factory system, booting with PXE and root on NFS, which is having trouble shutting down. I get as far as:
service network stop Shutting down (localfs) network interfaces: eth0 device: Intel Corporation 82546GB Gigabit Ethernet Co eth0 serves root filesystem. Leave it up. skipped eth1 device: Intel Corporation 82546GB Gigabit Ethernet Co No configuration found for eth1 Nevertheless the interface will be shut down. doneShutting down service (localfs) network . . . . . . . . .done service network done At this point, the shutdown seems to halt, but via a still-logged-in ssh session I see blogd using 100% CPU. It then takes 5-10 minutes (not sure exactly how long, I haven't timed it), and the system finally reboots.
278 seconds from I issue the 'reboot' to the network interface stops responding to pings.
Any suggestions as to where to look for a reason for this?
-- Per Jessen, Zürich (10.1°C)
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (2)
-
Boris Manojlovic
-
Per Jessen