Since 1.9 upgrade services in my containers won't auto-start

stevenculshaw

New Member
Sep 24, 2011
1
0
1
Hi,

I recently upgraded 3 servers in a cluster to 1.9.

Everything seemed fine, no errors during the upgrade but now when the vz restarts the services in the containers don't start.

An example: in a CentOS vz i have to manually enter it and start the network and mysqld services both of which are marked as a system service.

This was ok before the 1.9 upgrade.

The busiest of my cluster members also fell over today too it's been up for a long time on 1.7 but today it threw a kernel error to console and needed a manual reboot.

Any ideas?

Thanks,
Steven :)