Multiple services restart on their own hours apart. Why?

[dustindauncey]

This is still happening. Any other suggestions? Named has been removed but this issue still occurs. Memory never reaches maximum or not even that close to be honest, so I'm fairly certain it isn't a memory thing which is what my first thought was when I noticed this problem.

[dustindauncey]

OK, after further investigation I believe that the other member on this thread was onto something about it being inaccurate/unreliable. I started a Github issue report which contains all the details at https://github.com/serghey-rodin/vesta/issues/199

[erldcrtz]

I suggest you get another vps from digitalocean.com for testing purposes.. they charge per hour so you can destroy them after testing or leave them on for couple of days

install vestacp in it and observe... if its not restarting any services that means theres something wrong with your current server which is giving you problems..

thats the only way to find out if its a vestacp bug or something is wrong with your server.. because personally I have not experienced what you have experienced and I currently have 5 servers running vestacp in them...

[dustindauncey]

I suggest you get another vps from digitalocean.com for testing purposes... install vestacp in it and observe... if its not restarting any services that means theres something wrong with your current server which is giving you problems... thats the only way to find out if its a vestacp bug or something is wrong with your server.. because personally I have not experienced what you have experienced and I currently have 5 servers running vestacp in them...

Hi, thanks for the suggestion. I may do that. I'm not sure how much you read on the github link I posted, but I ran a command which shows the service start time and elapsed time, and it shows 19 hours for httpd as an example, yet the panel showed 41 minutes. So to me that is a clear VestaCP issue when it isn't using the times provided by the system itself.