Help, wikimedia template doesn't work from 1.0 to 1.1 proxmox ve upgrade

[neozeed]

On the computer I've got proxmox ve installed onto, I had the 1.0 release, and I did the apt-get update/upgrade to update it to 1.1.

When I did this, I had shutdown all of my VM's.

Now I just noticed that the wiki that I keep all of my notes on is not starting... The mysql refuses to load, and doing an apt-get update/upgrade in the VM isn't working either... I should point out this is the OpenVZ wikimedia template that I've used.

Any idea where to go from here? I'll admit I'm a mysql n00b, but eve the mysqld_safe dosn't do anything usefull:

# mysqld_safe
Starting mysqld daemon with databases from /var/lib/mysql
mysqld_safe[1204]: started
STOPPING server from pid file /var/run/mysqld/mysqld.pid
mysqld_safe[1217]: ended

adding --log-error=/tmp/a.txt gives me a 0 byte file..

Before on the 1.0 I noticed that if you were to stop the mysqld, it would not restart...

Any help is greatly appreciated.

 

[neozeed]

I got an error message finally:

090212 22:03:24 InnoDB: Started; log sequence number 0 4586672
090212 22:03:24 [ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address
090212 22:03:24 [ERROR] Do you already have another mysqld server running on port: 3306 ?
090212 22:03:24 [ERROR] Aborting
090212 22:03:24 InnoDB: Starting shutdown...
090212 22:03:26 InnoDB: Shutdown completed; log sequence number 0 4586672
090212 22:03:26 [Note] /usr/sbin/mysqld: Shutdown complete


I have the VM setup with it's own ip address... At least it's consistent, a local wikipedia mirror I have is also doing the exact same thing. On the VM in question a netstat -nap

# netstat -nap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:113 0.0.0.0:* LISTEN 308/inetd
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 204/portmap
tcp6 0 0 :::22 :::* LISTEN 360/sshd
tcp6 0 148 ::ffff:192.168.57.20:22 ::ffff:192.168.57:53101 ESTABLISHED1163/1
udp 0 0 0.0.0.0:111 0.0.0.0:* 204/portmap
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags Type State I-Node PID/Program name Path
unix 2 [ ] DGRAM 100383 289/syslogd /dev/log

# netstat -na|grep LIS
tcp 0 0 0.0.0.0:113 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 52 ::ffff:192.168.57.20:22 ::ffff:192.168.57:53101 ESTABLISHED

Nothing there.. it's weird.

 

[martin]

did you reboot after upgrade?

pls post your version:

pveversion -v

 

[neozeed]

did you reboot after upgrade?

pls post your version:

pveversion -v

Yes I did reboot, to pickup the new kernel after the apt-get upgrade...

# pveversion -v
pve-manager: 1.1-3 (pve-manager/1.1/3718)
qemu-server: 1.0-10
pve-kernel: 2.6.24-5
pve-kvm: 83-1
pve-firmware: 1
vncterm: 0.9-1
vzctl: 3.0.23-1pve1
vzdump: 1.1-1
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1dso1

 

[neozeed]

I tried changing the port in /etc/mysql/my.cnf from 3306 to 63306 so that it'd be a "user port" that high up incase it was some kind of security change...

same result, it think the port is already bound.

 

[neozeed]

Ok I think I got it!

It appears that in the 1.0 to 1.1 upgrade the loopback is not configured!!

I just noticed that nothing that is expected to bind to 127.0.0.1 isn't working...

I'm not sure how exactly to modify the /etc/network structure (assuming that is where it goes)

For now I'm just going to stick the ifconfig in /etc/rc.local and I'll write back if that's "soon enough" for it to work in the rc sequence.

---- edit----

Ok, I just checked, and it's working! Something about the upgrade killed the ifconfig on the loopback.... oh well at least that was easy enough to fix after a bit of digging.....

 

[dietmar]

It appears that in the 1.0 to 1.1 upgrade the loopback is not configured!!

The update does not touch the network configuration in any way.

- Dietmar

 

[neozeed]

The update does not touch the network configuration in any way.

- Dietmar

Very strange... Oh well I hope it's an isolated incident, as I was really shocked that it refused to work after the upgrade from 1.0 to 1.1... I just confirmed it on another server that also went from 1.0 to 1.1 that it too didn't have it's loopback configured. Something about that wiki template with a vmbr0 network interface doesn't transition all so well.

Oh well, oeverall I still love proxmox, At least this turned out to be nothing major. And at least if anyone else is using it for multiple wiki's they can google it on the 1.0-1.1 update as well.