Just noticed this today, not sure if others have or not. Its not really a bug, error, or issue so much as it is risky forgetfulness. This is a public service announcement (PSA) regarding saved browser tabs and WHM service restarts courtesy of, me.
So yesterday near the end of the shift I had to do a MySQL restart. Instead of logging into SSH like I normally do, I hopped in WHM to do this in the restart services tab. Works great, its awesome
Anyways, I had left the "MySQL restarted successfully" screen/message up in the tab in WHM, and as the day completed, finished work in other tabs, then closed the browser.
Today upon starting my browser all the previous tabs are reloaded and I am greeted by our ecom homepage, with uber fatal query and MySQL connect errors all over the place. My coworker immediately went into panic mode as his admin session and consequent pre-save data was wiped off the face of the earth. Sales freaked out, who knows what customers got booted (or what orders lost). Ahh what the heck happened!? Looking for errors, crashed DB, load, .... nothing. And then....
Omg. Facepalm. Un-lol. When the browser opened, it restarted MySQL again. I restarted MySQL without even knowing it.
Yes I deserved the heat I got from the team/customers because I should have known better. But you may not realize, so I'm letting you know: don't ever leave the "MySQL restarted successfully" (or other restart services) tab(s) open in your browser upon closing it, else as we are all now aware of, it may restart the service or server itself when you reopen the browser. This is assuming that your browser reopens sessions and your WHM cpsess ID is still valid of course. Regardless, be sure to always navigate away from these tabs when you're done working with a service or server restart.
Sure it would be cool to build a mechanism into WHM that prevents this, something like the success screen is a different URi than the actual restart initiation screen, but for now awareness is the clear fix.
So yesterday near the end of the shift I had to do a MySQL restart. Instead of logging into SSH like I normally do, I hopped in WHM to do this in the restart services tab. Works great, its awesome
Today upon starting my browser all the previous tabs are reloaded and I am greeted by our ecom homepage, with uber fatal query and MySQL connect errors all over the place. My coworker immediately went into panic mode as his admin session and consequent pre-save data was wiped off the face of the earth. Sales freaked out, who knows what customers got booted (or what orders lost). Ahh what the heck happened!? Looking for errors, crashed DB, load, .... nothing. And then....
Omg. Facepalm. Un-lol. When the browser opened, it restarted MySQL again. I restarted MySQL without even knowing it.
Yes I deserved the heat I got from the team/customers because I should have known better. But you may not realize, so I'm letting you know: don't ever leave the "MySQL restarted successfully" (or other restart services) tab(s) open in your browser upon closing it, else as we are all now aware of, it may restart the service or server itself when you reopen the browser. This is assuming that your browser reopens sessions and your WHM cpsess ID is still valid of course. Regardless, be sure to always navigate away from these tabs when you're done working with a service or server restart.
Sure it would be cool to build a mechanism into WHM that prevents this, something like the success screen is a different URi than the actual restart initiation screen, but for now awareness is the clear fix.