SSH Server in Serverstatus on System information don't update correctly

Submitted by Blueforce on Thu, 07/19/2018 - 21:02 Pro Licensee

Hi,

I have noticed for a while now that SSH Server in Server Status on System information page don't update status correctly.

I usually don't has SSH running, and the Server status is shoving "Not running", but if I then start it from the "Servers/SSH Server" it still shows "Not running". The same happens if I restart of the server. On boot, the SSH Server gets started but when logging in to Virtualmin/Webmin the Server status still shows "Not running"! Shouldn't the status actually get checked before showing it? Anyway... the SSH status is not working correctly.

Best regards, Leffe

Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Thu, 07/19/2018 - 23:14

That status can be cached for up to 5 minutes in some cases - so starting the SSH server from elsewhere may not show up immediately.

Submitted by Blueforce on Fri, 07/20/2018 - 17:59 Pro Licensee

Ok, thanks,

Reading old status info from some cache when rebooting a server don't feel right at all! Starting something up should be a "fresh" start and should not have any cached status!

//Leffe

Submitted by Blueforce on Fri, 07/20/2018 - 18:31 Pro Licensee

Does this cached status apply to all services on "Server Status"?

I think it would be better to show no status at all after a reboot instead of showing wrong status? Can't this be read live on a restart. I don't remember having this behavior earlier when using Virtualmin Framed Theme.

//Leffe

Submitted by JamieCameron on Sun, 07/22/2018 - 14:27

Yes, all status is refreshed in the background unless you start one of the servers using the Virtualmin UI or click the refresh button on that page. Collecting statuses in realtime would be too slow and CPU intensive.

Submitted by Blueforce on Sun, 07/22/2018 - 21:24 Pro Licensee

I didn't mean it should be realtime statuses when running, I meant that it should not show any status before it is collected from a server start/restart. The status from a prior run of the server is not relevant after a restart.

Not a big deal really, IF you now that the status after a restart has nothing to do with the actual run, better with no info than wrong info, why not clear old collected data on restart. That's how I would prefer it.

Thanks for the info, you can close this issue if you want as it's working as designed.

Best Regards, Leffe

Submitted by JamieCameron on Tue, 07/24/2018 - 00:36

Ah good point, it would be reasonable to re-run the status check at startup time. I'll update this ticket when that's done..

Submitted by JamieCameron on Sat, 08/04/2018 - 20:56

Implemented for inclusion in the next release.

Submitted by IssueBot on Thu, 10/11/2018 - 20:07

Status: Fixed ยป Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.