Hi,
The Winterhill at our repeater site sometimes jumps to "timeout" on all inputs or the receiver just stops. Manual restart works fine, but is not a good solution.
Can someone explain me how to plan a daily reboot of the Winterhill at 0.00h and 12.00h?
How to daily reboot
Re: How to daily reboot
As it is running on linux, a suitable file in /etc/cron.daily to reboot the pi might be a solution, but that relies on the system not crashing. Personally, I use a mechanical mains timer, the ones designed to turn the lights on and off when you are not at home, they tend to work.
For info on cron https://en.wikipedia.org/wiki/Cron
What you really need to do is monitor and detect the timeouts and restart the winterhill application rather than reboot the machine.
Mike
For info on cron https://en.wikipedia.org/wiki/Cron
What you really need to do is monitor and detect the timeouts and restart the winterhill application rather than reboot the machine.
Mike
Re: How to daily reboot
For that I need a piece of software which monitors the function of Winterhill and if not OK reboot the application.
Re: How to daily reboot
Yes, that's what I was suggesting you develop, bash or shell script perhaps? One that checks for a lockup and acts accordingly. The question is how do you know it has locked up. Is there some indicator? It will only work if you have a way to tell it has locked up, e.g. a process is no longer running or no data etc. I don't know if you can do this via the winterhill api. I would think so.
For a daily reboot at say 23:59, add this to crontab -
Type sudo crontab -e // That opens the editor
then add a line
59 23 * * * /sbin/shutdown -r now
Save it.
Mike
For a daily reboot at say 23:59, add this to crontab -
Type sudo crontab -e // That opens the editor
then add a line
59 23 * * * /sbin/shutdown -r now
Save it.
Mike
Re: How to daily reboot
Done that, but it doesn't work. When checking uptime it says over 4 days. So that was the last time I manually rebooted it.
Do I have to enable CRON somewhere?
Do I have to enable CRON somewhere?
g0mjw wrote: ↑Mon Jan 06, 2025 4:50 pmYes, that's what I was suggesting you develop, bash or shell script perhaps? One that checks for a lockup and acts accordingly. The question is how do you know it has locked up. Is there some indicator? It will only work if you have a way to tell it has locked up, e.g. a process is no longer running or no data etc. I don't know if you can do this via the winterhill api. I would think so.
For a daily reboot at say 23:59, add this to crontab -
Type sudo crontab -e // That opens the editor
then add a line
59 23 * * * /sbin/shutdown -r now
Save it.
Mike