Reboot/Poweroff not working on DNS320L

[Jesus M Diaz]

Hi!

Today after a power issue at home and some services not coming back, I made some changes in the configuration and tried to test them by rebooting the device. But the reboot didin't work, as it didin't the poweroff.

I got a message saying the device would be unavaliable for 60 seconds, but it did nothing more than shutting off few services.

I tried from CLI and same: neither reboot or poweroff worked.

[root@cinemateka]67 uptime
08:14:45 up 35 min,  0 users,  load average: 0.01, 0.21, 0.44
[root@cinemateka]68 date
Tue Dec  7 08:14:49 GMT 2021
[root@cinemateka]69 reboot
[root@cinemateka]70 uptime
08:15:07 up 36 min,  0 users,  load average: 0.00, 0.19, 0.43
[root@cinemateka]71
[root@cinemateka]71
[root@cinemateka]71 date
Tue Dec  7 08:15:09 GMT 2021
[root@cinemateka]72 uptime
08:15:31 up 36 min,  0 users,  load average: 0.00, 0.18, 0.42
[root@cinemateka]73 poweroff
[root@cinemateka]74 uptime
08:15:49 up 36 min,  0 users,  load average: 0.00, 0.17, 0.41
[root@cinemateka]75
[root@cinemateka]75
[root@cinemateka]75 uptime
08:17:17 up 38 min,  0 users,  load average: 0.00, 0.12, 0.37
[root@cinemateka]76
[root@cinemateka]76 uptime
08:18:16 up 39 min,  0 users,  load average: 0.00, 0.10, 0.34
[root@cinemateka]77

Any idea why? I would like to avoid hiting the power button to reload the device.

Thanks

[Hell Fish]

Reboot/Shutdown through WebUI also doesn't work?
Probably dns320l-daemon, see https://groups.google.com/g/alt-f/c/SEcWeGWgoSM/m/sFl9MRJYAAAJ

[Jesus M Diaz]

Thanks!

Apparently that worked. I manually executed the commands and then the device rebooted (clearly the 'reboot' command was queued). Then I added the commands to the user script, and rebooted the device again ... it restarted fine. And as a final test, I rebooted again this time from the GUI, and it worked.

It also solved other problem I noticed after the power issue today: the user script wasn't working (I am adding a secondary IP address), but it seems that it was working, but blocked for some reason, so executing first the 'refreshing' of the dns320l-daemon apparently fixed the other issue as well.

So now everything is working fine except the device coming up automatically after a power issue, I still need to hit the power button. Any hint on how to configure it to power on back when power is restored?

Thanks!!

--
You received this message because you are subscribed to the Google Groups "Alt-F" group.
To unsubscribe from this group and stop receiving emails from it, send an email to alt-f+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/alt-f/da5a65f2-950a-4539-aa1c-c61abc9137fan%40googlegroups.com.

[jesusm.d...@gmail.com]

Found and fixed!

dns320l-daemon -x GetPowerRecoveryState

dns320l-daemon -x EnablePowerRecovery

Thanks

[pedja]

Solution for 320L A3, poweroff, and restrat work

Services->User, user, Configure, "Script to execute on power-up:"

/mnt/md1/Alt-F/usr/bin/startup.sh 

md1, sda... whatever works for your config

#########################################################################

#!/bin/sh

# Script to execute as the root user at boot time.
# You can loose your data or make the system inaccessible
# if using the wrong commands. You have been warned!

exec >> /var/log/user.log 2>&1

case "$1" in
       start)
               echo "Starting $0"
               while ! killall -0 dns320l-daemon; do usleep 100000; done
               killall dns320l-daemon
               ;;
       stop)
               echo "Stopping $0"

               killall dns320l-daemon  
               ;;
esac

#########################################################################

AND SAVE CONFIG CHANGE !!!