System Uptime Info and an Automatic Reboot

[JePeSWE (Jerry)]

Ahh, ok then. Thanks alot

Uptime openHAB aN:aN whats wrong when i get aN:aN instead of the time?

[David_Bontems]

Dear All

I applied the logic described above, tried different syntax/format, added notification to make the code was executed
but the Rasp is never rebooting, the line below does not move anything
executeCommandLine(’“sudo” “reboot”’, 5000)

Has anyone been successful with reboot from openhab rule ?
Thank you

[mdnx (Martin Tamke)]

Im not using the rule here, but would assume, that the rule can only reboot OpenHab, when the Openhab user is member of sudoers. Only than the Openhab user can trigger a reboot.

Have a look at this article, this might help you:

How to solve Exec binding problems

One of the most common problems I help people with on this forum is dealing with the Exec binding. So I’m writing this post so I can reference it later. Background When openHAB is installed in the automated way (i.e. via apt-get) an openhab user is created and the service runs under that user. The openhab user has the following attributes: no shell so one cannot log in or su to this user limited rights not a member of sudoers has a home directory in /var/lib/openhab (or /var/lib/openhab2) has…

[vzorglub (Vincent Regaud)]

What does the logs tell you?

[rlkoshak (Rich Koshak)]

@David_Bontems

but the Rasp is never rebooting, the line below does not move anything
executeCommandLine(’“sudo” “reboot”’, 5000)

Has anyone been successful with reboot from openhab rule ?

I do not think it is possible to reboot the machine that OH is running on from OH itself. Here is the sequence of events.

1. OH creates a shell
2. OH calls reboot
3. reboot sends out the “we’re going down!” signal to all running processes.
4. OH receives the “we’re going down!” signal
5. OH abruptly kills the shell it create to call the reboot command
6. The reboot command get’s killed because the shell it was running in, it’s parent process, was killed
7. The machine stops rebooting.

This seems to be the behavior when ever someone tries to do it. I do think this is a side effect from the fact that the reboot command’s parentage is something like:

systemd -> java -> shell -> reboot

Perhaps the reboot command can’t survive it’s grandparent process being killed the same way it can it’s parent process.

[David_Bontems]

Thank you mdnx, I managed to get the reboot working by following your instruction

Regards
David