Ticket ID: 112126
We had a Stable Cpanel server issue a nightly update and 2 minutes after commencing mysql was downgraded from 4.1.13 to 4.0.25 breaking quite a few databases on the server.
Cpanel support indicated that the nightly update would not do this.
Second night, different server, process tree:
├─crond─┬─crond─┬─exim
│ │ └─php
│ └─crond─┬─exim
│ └─upcp───upcp───mysqlup
This looks pretty apparent here. First of all, it is really unacceptable for a stable push to downgrade a server's mysql version from 4.1 to 4.0. Secondly, what change has been made to cause this behavior, and can we get a direct response from a developer at cpanel regarding this?



LinkBack URL
About LinkBacks
Reply With Quote




