When we upgrade sections on cpanel and wHM we tend not to email customers as we do it on a regular basis and it is very time consuming emailing the correct people everytime we make a upgrade.
Obviously if there was a big update about to happen we would notify all customers straight away.
We need to keep "Automatic Updates" enabled on our cPanel servers as that allows to get rid of any security hole that may have been recently found and patched by cpanel. We take care of Server Security and OS related security from our end but cpanel updates cannot be disabled.
Even though the some functionalities change in your control panel but its not something so major that you need to learn the control panel from the beginning. Changes are very minor and it takes no time to understand those.
Becareful with CPanel release 10.9.0 - 57 release..
Theres a corker of a bug in it relating to the management of Parked / Addon /Sub domains.
On my previous host everything was all jumbled up with subdomains showing in addons, addons showing in subdomains....right ole mess it was and they said there was nothing they could do until CPanel released a fix. Problem was you couldn't delete anything..
Update must have caused the problem. Our new servers setup in this week were setup with WHM 10.8.0 cPanel 10.9.0-R57 and so far we have had no problems with those.
Is this a recent thing? I've been getting a lot of emails with the body:
cpsrvd failed @ Sun Dec 24 18:29:24 2006. A restart was attempted automatically
over the Christmas period. Every time I look the website is up so I haven't wanted to bother the support staff but it'd be good to know if this is related to this post. Thanks
As per my knowledge you have a VPS and we will need to check why cpservd is failing on your VPS. cpservd checks working of all services and if any service goes down then it will restart that service automatically.
If cpservd itself fails then there wont be auto restart for other services if any service fails. Contact our VPS Hosting support team to get this sorted.
Comment