OpenVZ Forum


Home » General » Support » Note - Problem with RPM Repo versions right now maybe?
Note - Problem with RPM Repo versions right now maybe? [message #8752] Tue, 05 December 2006 13:30 Go to previous message
tchipman is currently offline  tchipman
Messages: 28
Registered: June 2006
Junior Member
Just a comment, in case anyone else has seen this?

I'm using the OpenVZ RPM Repo for Yum so that my OpenVZ gets updated automagically when I do a "yum update" on my server (great idea IMHO and I'm really glad this is available Smile

One small wrinkle maybe though?

-I rolled an update yesterday AM

-This brought kernel up to version "2.6.9-023stab032.1-smp".

-It also updated my vzctl to version "3.0.13"

After rebooting, OpenVZ didn't start up correctly. I got errors about being unable to access /dev/vz. Double-checking my dmesg output, and then /etc/init.d/vz control script output, openvz was convinced it was running correctly... but my vzhosts didn't autostart when the system booted, and I couldn't bring them up manually.

A quick search through forums gave me a hint, that it might be a problem with the kernel and the vzctl binaries not being compatible.

So, I pulled the latest and greatest "test" kernel (2.6.18-ovz028test007.1-smp for my machine) and then rebooted using this kernel.

Bingo, everything works now "as it should" - vzctl is not pissed off at me, the vzhosts started on their own when the system booted and life is good.

however: The fact that this problem happened seems to be resting in the fact that the kernel and vzctl versions in the "auto update yum repo" right now are not exactly fully compatible

I might encourage the folks who maintain this yum repo to either

-roll back the vzctl version
-or roll a newer kernel which is compatible with the vzctl

otherwise anyone else who is using the yum repo as their vzctl update control will be equally messed up the next time they roll a yum update.

I'll leave things as they stand now, on the hope that this "test" kernel is OK for a production system. (In the past I believe I've been told as much...)

I hope this info is "correct" or at least not wrong, and possibly of some use to someone.


--Tim Chipman
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Reboot
Next Topic: vzquota : (error) Quota on syscall for 777: No such file or directory
Goto Forum:
  


Current Time: Sun Sep 15 15:18:13 GMT 2024

Total time taken to generate the page: 0.03300 seconds