Hi guys. It would be nice if iHost had a sheduled reboot. I really miss this function.
better you report your issue that force you to reboot than suggest this function
2 Likes
All modern electronic devices that use RAM (modems, routers, IP cameras, even mobile phones) are recommended to be reboot from time to time to ensure that they work without errors. What is the first piece of advice from your internet provider’s technical support? Reset the modem. ?! Most routers, IP cameras … have a sheduled reboot option in their firmware. Probably not without reason. I think this feature prevents many problems during operation. It also detects other errors that we are not aware of if the system does not work properly after a reboot. Of course, this is just my humble opinion.
All modern electornic devices should work 24/7 with no interruption.
This device, for example, is only going offline/restarting only when I unplug it by mistake.
I agree. Should. The emphasis is on should.
What will you do first when the device does not work properly? Are you going to call the manufacturer’s technical support immediately or do a reboot?
Do you think that the programmers at TP-Link, Asus … needlessly wasted their time programming the shedulled reboot feature? Or maybe they didn’t have a better job.
Report the bug.
If you just reboot it, the bug still will be there and you will need to reboot it once again, disconnecting all devices.
This is not the correct way to fix a problem.
I agree. The scheduled reboot is a feature I looked for when configuring my iHost, and was surprised it was not there. There is an importance to rebooting regularly and it does not have to be because of a bug or an issue. Rebooting a device will typically clear any cache and close any unused assets reducing the overall system load, thus reducing heat. Reduction of heat extends the service life of any product.
1 Like
Sorry, but this is not true.
Do you believe that Google reboot their servers frequently?
Yes, they reboot.
In google’s case, they have redundant servers so their load balancing points traffic to the servers that are up while the others reboot… then switch to the newly rebooted ones to reboot the others.
No, they don’t.
Servers are restarted just for a single purpose: Kernel update.
There is no evidence that we need a schedule reboot for iHost
Holy Moly restart that thing lol, your swap space is full and load averages are off the charts.
Sorry but you really don’t understand how the swap works and how the load average works in Linux systems.
It’s a server with 512Gb of RAM and 128 Cores.
It’s expected to have 4Gb of swap always full and a load average of 20 is the same as 0.15 in a single core CPU.