[SOLVED] Proxmox-VE 2.3 to 3 upgrade gone wrong ... somehow stuck

[steffen]

First of all, yes I have google everything I could think of and searched the Forum as well. I guess part of the Problem is that I do not understand the Problem. Well I do see whatit is telling me, but it is not making sense.

Original 2.3 Install was direktly from Proxmox-VE 2.3 Installer CD / ISO. To upgrade I used the script provided in the wiki. Made backup of my containers and ensured they where all powered down and made sure all apt-get updates where fully handled.

Ran the script and failed somewhere.

The Problem seems to trace to the following error:

[....] Restarting pve cluster filesystem: pve-cluster/usr/bin/pmxcfs: symbol lookup error: /usr/bin/pmxcfs: undefined symbol: g_mutex_lock
failed!


Sorry for not being quite so bright, but WTF is a mutex lock ?? "mutex" should be some sort of mechanism checking that two or more things are not interfereing with each other. So a "lock" of that would tell me that there IS something blocking something else ... but that's all theory without any real meaning.

/usr/bin/pmxcfs sems to exist (it's a binary)

uname -a currently says:
Linux proxmox-one 2.6.32-19-pve #1 SMP Wed May 15 07:32:52 CEST 2013 x86_64 GNU/Linux

 

[steffen]

/usr/bin/pmxcfs: undefined symbol: g_mutex_lock

This has got mean something to someone out there. I have even been desperate enough to purge pve-cluster and try installing it fresh again ... I get the same thing thrown at me and google is not helping either.

 

[steffen]

Sorry, I guess this thread is never going to help anyone. I got a Cable connection that has gone bonkers. I get screwed packages non stop ... so I guess during the upgrade I got a sack full of not not quite right packages.

Downloaded the Installer ISO at home and simply re-installed and am now working on getting the backups of the containers back at the start.