Centos 7 hardware server can not stop or reboot, lock on stirng (Shutting down.)

Issues related to hardware problems
Post Reply
ryzn
Posts: 3
Joined: 2021/12/17 06:42:29

Centos 7 hardware server can not stop or reboot, lock on stirng (Shutting down.)

Post by ryzn » 2021/12/17 08:11:42

Last 3-4 mounths hardware server can not stop or reload.
It's locked on string(info from journalctl):
systemd[1]: Shutting down.
And we have to use button on server for restart.

CentOS Linux release 7.9.2009 (Core)
Motherboard:
Base Board Information
Manufacturer: HPE
Product Name: ProLiant DL380 Gen10

Last log here, but in previous log last string was "Shutting down." :
Dec 13 02:37:22 cloud.1c.com.vn systemd[1]: Stopped Collect Read-Ahead Data.
Dec 13 02:37:22 cloud.1c.com.vn kernel: type=1130 audit(1639337842.655:171908): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-readahead-collect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 13 02:37:22 cloud.1c.com.vn kernel: type=1131 audit(1639337842.656:171909): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-readahead-collect comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 13 02:37:22 cloud.1c.com.vn systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Dec 13 02:37:22 cloud.1c.com.vn kernel: type=1130 audit(1639337842.705:171910): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 13 02:37:22 cloud.1c.com.vn kernel: type=1131 audit(1639337842.705:171911): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Dec 13 02:37:22 cloud.1c.com.vn systemd[1]: Stopping LVM2 metadata daemon...
Dec 13 02:37:22 cloud.1c.com.vn systemd[1]: Stopped LVM2 metadata daemon.
Dec 13 02:37:22 cloud.1c.com.vn systemd[1]: Reached target Shutdown.
Dec 13 02:37:22 cloud.1c.com.vn systemd[1]: Reached target Final Step.
Dec 13 02:37:22 cloud.1c.com.vn systemd[1]: Starting Reboot...
Dec 13 02:37:22 cloud.1c.com.vn systemd[1]: Closed LVM2 metadata daemon socket.
Dec 13 02:37:22 cloud.1c.com.vn systemd[1]: Shutting down.
Dec 13 02:37:22 cloud.1c.com.vn systemd[1]: Hardware watchdog 'HPE iLO2+ HW Watchdog Timer', version 0
Dec 13 02:37:22 cloud.1c.com.vn kernel: watchdog: watchdog0: watchdog did not stop!
Dec 13 02:37:22 cloud.1c.com.vn systemd[1]: Set hardware watchdog to 10min.
-- Reboot --
Dec 13 02:50:42 cloud.1c.com.vn systemd-journal[387]: Runtime journal is using 8.0M (max allowed 4.0G, trying to leave 4.0G free of 94.1G available → current limit 4.0G).
Dec 13 02:50:42 cloud.1c.com.vn kernel: microcode: microcode updated early to revision 0x2006b06, date = 2021-03-08
Dec 13 02:50:42 cloud.1c.com.vn kernel: Initializing cgroup subsys cpuset
Dec 13 02:50:42 cloud.1c.com.vn kernel: Initializing cgroup subsys cpu

User avatar
TrevorH
Site Admin
Posts: 33191
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Centos 7 hardware server can not stop or reboot, lock on stirng (Shutting down.)

Post by TrevorH » 2021/12/17 17:54:03

Dec 13 02:37:22 cloud.1c.com.vn systemd[1]: Set hardware watchdog to 10min.
-- Reboot --
Dec 13 02:50:42 cloud.1c.com.vn systemd-journal[387]: Runtime journal is using 8.0M (max allowed 4.0G, trying to leave 4.0G free of 94.1G available
Did you reboot that or was it the 10 minute hardware watchdog that did it?
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

ryzn
Posts: 3
Joined: 2021/12/17 06:42:29

Re: Centos 7 hardware server can not stop or reboot, lock on stirng (Shutting down.)

Post by ryzn » 2021/12/21 04:34:13

Yes, operator pushed button on server by hand.

ryzn
Posts: 3
Joined: 2021/12/17 06:42:29

Re: Centos 7 hardware server can not stop or reboot, lock on stirng (Shutting down.)

Post by ryzn » 2022/05/16 08:50:23

Hello!

Tell me, please, about:

Some days ago I tied to stop my hardware server again, but it could not. Dispatcher pushed button after one hour.

What do you think: Could it be from "wron way to Windows shared folder", boot log below:
May 07 04:11:25 cloud.1c.com.vn systemd[1]: Stopped Create Static Device Nodes in /dev.
May 07 04:11:25 cloud.1c.com.vn systemd[1]: Stopped Collect Read-Ahead Data.
May 07 04:11:25 cloud.1c.com.vn systemd[1]: Stopped Replay Read-Ahead Data.
May 07 04:11:25 cloud.1c.com.vn systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
May 07 04:11:25 cloud.1c.com.vn systemd[1]: Stopping LVM2 metadata daemon...
May 07 04:11:25 cloud.1c.com.vn systemd[1]: Stopped LVM2 metadata daemon.
May 07 04:11:25 cloud.1c.com.vn systemd[1]: Reached target Shutdown.
May 07 04:11:25 cloud.1c.com.vn systemd[1]: Reached target Final Step.
May 07 04:11:25 cloud.1c.com.vn systemd[1]: Starting Power-Off...
May 07 04:11:25 cloud.1c.com.vn systemd[1]: Closed LVM2 metadata daemon socket.
May 07 04:11:25 cloud.1c.com.vn systemd[1]: Shutting down.
May 07 04:11:26 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:11:28 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:11:30 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:11:32 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:11:34 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:11:36 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:11:38 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:11:40 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:11:42 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:11:44 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:11:46 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:11:48 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:11:50 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:11:52 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:11:54 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:11:56 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:11:58 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:12:00 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:12:02 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare
May 07 04:12:04 cloud.1c.com.vn kernel: CIFS VFS: BAD_NETWORK_NAME: \\trade.local\winshare

User avatar
jlehtone
Posts: 4523
Joined: 2007/12/11 08:17:33
Location: Finland

Re: Centos 7 hardware server can not stop or reboot, lock on stirng (Shutting down.)

Post by jlehtone » 2022/05/16 12:56:07

If system mounts network shares, then it should umount them before closing other services, like network.
Yours seems to hang on to CIFS mount way too long.

Post Reply