Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Unraid Summer Sale in live: 20% off Starter and Unleashed + buy one, get one 50% off

Automated shutdown issues

ezelbanaan
in General Support

Featured Replies

Hello,
I have set up a user script to run the ```shutdown``` command every night to shut down my unraid server. I've then scheduled WoL packets using my router to turn it back on, and most of the time this works great. However, I've had it happen a few times that my server never seems to turn off, and the server won't respond to anything. Due to this issue, I have set up a syslog server to capture logs in the hope of finding the issue, but the only thing I've noticed was ```NAS root: /usr/local/sbin/powerdown has been deprecated```, but from what I can find online, it should still be the way to go.
If anyone knows how to fix this, please let me know.
Here are the rest of the logs: 

Shutdown: 

Jul 16 00:00:01 NAS root: /usr/local/sbin/powerdown has been deprecated
Jul 16 00:00:01 NAS init: Switching to runlevel: 0
Jul 16 00:00:01 NAS init: Trying to re-exec init
Jul 16 00:00:02 NAS kernel: mdcmd (36): nocheck cancel
Jul 16 00:00:03 NAS emhttpd: Spinning up all drives...
Jul 16 00:00:03 NAS emhttpd: read SMART /dev/sdh
Jul 16 00:00:03 NAS emhttpd: read SMART /dev/sdg
Jul 16 00:00:03 NAS emhttpd: read SMART /dev/sdd
Jul 16 00:00:03 NAS emhttpd: read SMART /dev/sde
Jul 16 00:00:03 NAS emhttpd: read SMART /dev/sdb
Jul 16 00:00:03 NAS emhttpd: read SMART /dev/sdf
Jul 16 00:00:03 NAS emhttpd: read SMART /dev/sdc
Jul 16 00:00:03 NAS emhttpd: read SMART /dev/nvme0n1
Jul 16 00:00:03 NAS emhttpd: read SMART /dev/nvme1n1
Jul 16 00:00:03 NAS emhttpd: read SMART /dev/sda
Jul 16 00:00:03 NAS emhttpd: Stopping services...
Jul 16 00:00:03 NAS emhttpd: shcmd (201): /etc/rc.d/rc.libvirt stop
Jul 16 00:00:03 NAS root: Stopping libvirtd...
Jul 16 00:00:03 NAS dnsmasq[4923]: exiting on receipt of SIGTERM
Jul 16 00:00:03 NAS root: Network c315c6e7-4d76-4341-80d6-4fec73df80a2 destroyed
Jul 16 00:00:03 NAS root:
Jul 16 00:00:06 NAS root: Stopping virtlogd...
Jul 16 00:00:07 NAS root: Stopping virtlockd...
Jul 16 00:00:08 NAS emhttpd: shcmd (202): umount /etc/libvirt
Jul 16 00:00:08 NAS emhttpd: shcmd (204): /etc/rc.d/rc.docker stop
Jul 16 00:00:09 NAS kernel: docker0: port 1(veth744f552) entered disabled state
Jul 16 00:00:09 NAS kernel: veth8014231: renamed from eth0
Jul 16 00:00:09 NAS kernel: docker0: port 1(veth744f552) entered disabled state
Jul 16 00:00:09 NAS kernel: device veth744f552 left promiscuous mode
Jul 16 00:00:09 NAS kernel: docker0: port 1(veth744f552) entered disabled state
Jul 16 00:00:09 NAS kernel: docker0: port 2(veth7d3d611) entered disabled state
Jul 16 00:00:09 NAS kernel: veth9e3cc06: renamed from eth0
Jul 16 00:00:09 NAS kernel: docker0: port 2(veth7d3d611) entered disabled state
Jul 16 00:00:09 NAS kernel: device veth7d3d611 left promiscuous mode
Jul 16 00:00:09 NAS kernel: docker0: port 2(veth7d3d611) entered disabled state
Jul 16 00:00:13 NAS kernel: docker0: port 4(veth320c11e) entered disabled state
Jul 16 00:00:13 NAS kernel: vethd33e926: renamed from eth0
Jul 16 00:00:13 NAS kernel: docker0: port 4(veth320c11e) entered disabled state
Jul 16 00:00:13 NAS kernel: device veth320c11e left promiscuous mode
Jul 16 00:00:13 NAS kernel: docker0: port 4(veth320c11e) entered disabled state
Jul 16 00:00:19 NAS kernel: docker0: port 3(vethdd12a7d) entered disabled state
Jul 16 00:00:19 NAS kernel: veth7068ad7: renamed from eth0
Jul 16 00:00:19 NAS kernel: docker0: port 3(vethdd12a7d) entered disabled state
Jul 16 00:00:19 NAS kernel: device vethdd12a7d left promiscuous mode
Jul 16 00:00:19 NAS kernel: docker0: port 3(vethdd12a7d) entered disabled state
Jul 16 00:00:19 NAS root: stopping dockerd ...
Jul 16 00:00:20 NAS root: Cleaning up old /var/run/dockerd.pid.
Jul 16 00:00:20 NAS emhttpd: shcmd (205): umount /var/lib/docker
Jul 16 00:00:20 NAS emhttpd: shcmd (206): /etc/rc.d/rc.samba stop
Jul 16 00:00:20 NAS wsdd2[3487]: 'Terminated' signal received.
Jul 16 00:00:20 NAS winbindd[3490]: [2023/07/16 00:00:20.800707,  0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler)
Jul 16 00:00:20 NAS winbindd[3491]: [2023/07/16 00:00:20.800728,  0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler)
Jul 16 00:00:20 NAS winbindd[3490]:   Got sig[15] terminate (is_parent=1)
Jul 16 00:00:20 NAS winbindd[3491]:   Got sig[15] terminate (is_parent=0)
Jul 16 00:00:20 NAS wsdd2[3487]: terminating.
Jul 16 00:00:20 NAS winbindd[5629]: [2023/07/16 00:00:20.800774,  0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler)
Jul 16 00:00:20 NAS winbindd[5629]:   Got sig[15] terminate (is_parent=0)
Jul 16 00:00:20 NAS emhttpd: shcmd (207): rm -f /etc/avahi/services/smb.service
Jul 16 00:00:20 NAS avahi-daemon[3519]: Files changed, reloading.
Jul 16 00:00:20 NAS avahi-daemon[3519]: Service group file /services/smb.service vanished, removing services.
Jul 16 00:00:20 NAS emhttpd: shcmd (209): /etc/rc.d/rc.nfsd stop
Jul 16 00:00:20 NAS rpc.mountd[2669]: Caught signal 15, un-registering and exiting.
Jul 16 00:00:22 NAS kernel: nfsd: last server has exited, flushing export cache
Jul 16 00:00:22 NAS emhttpd: Stopping mover...
Jul 16 00:00:22 NAS emhttpd: shcmd (210): /usr/local/sbin/mover stop
Jul 16 00:00:22 NAS root: mover: not running
Jul 16 00:00:22 NAS emhttpd: Sync filesystems...
Jul 16 00:00:22 NAS emhttpd: shcmd (211): sync

And when I manually press the reset button on the server:
  

Jul 16 13:34:08 NAS emhttpd: Starting services...
Jul 16 13:34:08 NAS emhttpd: shcmd (71): /etc/rc.d/rc.samba restart
Jul 16 13:34:08 NAS wsdd2[2584]: 'Terminated' signal received.
Jul 16 13:34:08 NAS winbindd[2587]: [2023/07/16 13:34:08.722238,  0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler)
Jul 16 13:34:08 NAS winbindd[2587]:   Got sig[15] terminate (is_parent=1)
Jul 16 13:34:08 NAS wsdd2[2584]: terminating.
Jul 16 13:34:08 NAS winbindd[2593]: [2023/07/16 13:34:08.722259,  0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler)
Jul 16 13:34:08 NAS winbindd[2593]:   Got sig[15] terminate (is_parent=0)
Jul 16 13:34:08 NAS winbindd[2720]: [2023/07/16 13:34:08.722386,  0] ../../source3/winbindd/winbindd_dual.c:1957(winbindd_sig_term_handler)
Jul 16 13:34:08 NAS winbindd[2720]:   Got sig[15] terminate (is_parent=0)
Jul 16 13:34:09 NAS rsyslogd: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="3461" x-info="https://www.rsyslog.com"] start
Jul 16 13:34:12 NAS root: Starting Samba:  /usr/sbin/smbd -D
Jul 16 13:34:12 NAS smbd[3504]: [2023/07/16 13:34:12.378663,  0] ../../source3/smbd/server.c:1741(main)
Jul 16 13:34:12 NAS smbd[3504]:   smbd version 4.17.7 started.
Jul 16 13:34:12 NAS smbd[3504]:   Copyright Andrew Tridgell and the Samba Team 1992-2022
Jul 16 13:34:12 NAS root:                  /usr/sbin/wsdd2 -d -4
Jul 16 13:34:12 NAS wsdd2[3518]: starting.
Jul 16 13:34:12 NAS root:                  /usr/sbin/winbindd -D
Jul 16 13:34:12 NAS winbindd[3519]: [2023/07/16 13:34:12.472566,  0] ../../source3/winbindd/winbindd.c:1440(main)
Jul 16 13:34:12 NAS winbindd[3519]:   winbindd version 4.17.7 started.
Jul 16 13:34:12 NAS winbindd[3519]:   Copyright Andrew Tridgell and the Samba Team 1992-2022
Jul 16 13:34:12 NAS winbindd[3521]: [2023/07/16 13:34:12.478149,  0] ../../source3/winbindd/winbindd_cache.c:3116(initialize_winbindd_cache)
Jul 16 13:34:12 NAS winbindd[3521]:   initialize_winbindd_cache: clearing cache and re-creating with version number 2
Jul 16 13:34:12 NAS emhttpd: shcmd (76): /etc/rc.d/rc.avahidaemon restart
Jul 16 13:34:12 NAS root: Stopping Avahi mDNS/DNS-SD Daemon: stopped
Jul 16 13:34:12 NAS avahi-dnsconfd[2699]: read(): EOF
Jul 16 13:34:12 NAS root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D
Jul 16 13:34:12 NAS avahi-daemon[3550]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214).
Jul 16 13:34:12 NAS avahi-daemon[3550]: Successfully dropped root privileges.
Jul 16 13:34:12 NAS avahi-daemon[3550]: avahi-daemon 0.8 starting up.
Jul 16 13:34:12 NAS avahi-daemon[3550]: Successfully called chroot().
Jul 16 13:34:12 NAS avahi-daemon[3550]: Successfully dropped remaining capabilities.
Jul 16 13:34:12 NAS avahi-daemon[3550]: Loading service file /services/sftp-ssh.service.
Jul 16 13:34:12 NAS avahi-daemon[3550]: Loading service file /services/smb.service.
Jul 16 13:34:12 NAS avahi-daemon[3550]: Loading service file /services/ssh.service.
Jul 16 13:34:12 NAS avahi-daemon[3550]: Joining mDNS multicast group on interface br0.IPv4 with address 10.37.100.254.
Jul 16 13:34:12 NAS avahi-daemon[3550]: New relevant interface br0.IPv4 for mDNS.
Jul 16 13:34:12 NAS avahi-daemon[3550]: Network interface enumeration completed.
Jul 16 13:34:12 NAS avahi-daemon[3550]: Registering new address record for 10.37.100.254 on br0.IPv4.
Jul 16 13:34:12 NAS emhttpd: shcmd (77): /etc/rc.d/rc.avahidnsconfd restart
Jul 16 13:34:12 NAS root: Stopping Avahi mDNS/DNS-SD DNS Server Configuration Daemon: stopped
Jul 16 13:34:12 NAS root: Starting Avahi mDNS/DNS-SD DNS Server Configuration Daemon:  /usr/sbin/avahi-dnsconfd -D
Jul 16 13:34:12 NAS avahi-dnsconfd[3559]: Successfully connected to Avahi daemon.
Jul 16 13:34:12 NAS emhttpd: shcmd (87): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 20
Jul 16 13:34:12 NAS rpc.mountd[2668]: v4.2 client attached: 0xdd5329f264b3d5a6 from "10.37.1.254:818"
Jul 16 13:34:12 NAS kernel: loop2: detected capacity change from 0 to 41943040
Jul 16 13:34:12 NAS kernel: BTRFS: device fsid 55dbb59e-01a6-42c7-85b8-7f7d95de5e02 devid 1 transid 70546 /dev/loop2 scanned by mount (3596)
Jul 16 13:34:12 NAS kernel: BTRFS info (device loop2): using crc32c (crc32c-intel) checksum algorithm
Jul 16 13:34:12 NAS kernel: BTRFS info (device loop2): using free space tree
Jul 16 13:34:12 NAS kernel: BTRFS info (device loop2): enabling ssd optimizations
Jul 16 13:34:12 NAS root: Resize device id 1 (/dev/loop2) from 20.00GiB to max
Jul 16 13:34:12 NAS emhttpd: shcmd (89): /etc/rc.d/rc.docker start
Jul 16 13:34:12 NAS root: starting dockerd ...
Jul 16 13:34:13 NAS avahi-daemon[3550]: Server startup complete. Host name is NAS.local. Local service cookie is 117036803.
Jul 16 13:34:14 NAS avahi-daemon[3550]: Service "NAS" (/services/ssh.service) successfully established.
Jul 16 13:34:14 NAS avahi-daemon[3550]: Service "NAS" (/services/smb.service) successfully established.
Jul 16 13:34:14 NAS avahi-daemon[3550]: Service "NAS" (/services/sftp-ssh.service) successfully established.
Jul 16 13:34:14 NAS kernel: Bridge firewalling registered
Jul 16 13:34:14 NAS kernel: Initializing XFRM netlink socket
Jul 16 13:34:15 NAS kernel: docker0: port 1(vethfce51f3) entered blocking state
Jul 16 13:34:15 NAS kernel: docker0: port 1(vethfce51f3) entered disabled state
Jul 16 13:34:15 NAS kernel: device vethfce51f3 entered promiscuous mode
Jul 16 13:34:15 NAS kernel: docker0: port 1(vethfce51f3) entered blocking state
Jul 16 13:34:15 NAS kernel: docker0: port 1(vethfce51f3) entered forwarding state
Jul 16 13:34:15 NAS kernel: docker0: port 1(vethfce51f3) entered disabled state
Jul 16 13:34:15 NAS kernel: eth0: renamed from veth0bfbf88
Jul 16 13:34:15 NAS kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vethfce51f3: link becomes ready
......

 

  • Quote

    • Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Reply to this topic...
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.