Json local endpoint restart versus settings page reboot.
At one point the restart didn’t fully clear out clear out everything, and would lead to a hub crash.
1 Like
That makes it clear, using HubInfo to restart with the json call, starting reciently, memory had been never showing the large amount of free memory i was used to.
Just starting low, and plummets turning it in to a cyclic nightmare.
Is it as simple as changing restart to reboot in the json call?
Http://10.0.0.xxx:8080/hub/restart
To
Http://10.0.0.xxx:8080/hub/reboot
?
1 Like
That should work unless you have hub security turned on.
BTW - Hub Info doesn’t do a restart, it has a reboot or a shutdown.
3 Likes
And it is one fine device!
Thank you, for this help, and very much for HubInfo.
1 Like
Thank you again, @thebearmay, this has made a world of difference in the last day.
Much more memory available on reboot than restart.
1 Like
I believe restart refers to the Java VM in which the hub platform runs.
Reboot refers to the underlying Linux OS running the Java VM.
2 Likes
So restart just kills and restarts the jvm and reboot is a full reboot. Which is really recommend for low memory i believe all of us have been doing the former.
From memory it was when there were mass slowdowns and the team couldn't work out why. As a way to investigate and to not have to fully reboot the device they brought it in.
The rebooter app had that function added from a request from Victor from memory as a example.
This brings me to the question...
What is the best way, using RM, to accomplish a reboot.
Syntax if possible!
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
