After upgrade loopback address is set to 127.0.0.2: Apache & MySQL won't start

[dan]

Hi,

I've just upgraded to Version 2.0-18/16283a5a. After restarting my VM Apache and MySQL won't come up. So I checked /etc/network/interfaces and saw that the loopback address was automatically set to 127.0.0.2. Why is that? How can I change it back to 127.0.0.1?

# Auto generated lo interfaceauto lo
iface lo inet loopback


# Auto generated venet0 interface
auto venet0
iface venet0 inet manual
up ifconfig venet0 up
up ifconfig venet0 127.0.0.2
up route add default dev venet0
down route del default dev venet0
down ifconfig venet0 down




iface venet0 inet6 manual


auto venet0:0
iface venet0:0 inet static
address <my external ip>
netmask 255.255.255.255

pveversion -vpve-manager: 2.0-18 (pve-manager/2.0/16283a5a)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 2.0-55
pve-kernel-2.6.32-6-pve: 2.6.32-55
lvm2: 2.02.88-2pve1
clvm: 2.02.88-2pve1
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-1
libqb: 0.6.0-1
redhat-cluster-pve: 3.1.8-3
pve-cluster: 1.0-17
qemu-server: 2.0-13
pve-firmware: 1.0-14
libpve-common-perl: 1.0-11
libpve-access-control: 1.0-5
libpve-storage-perl: 2.0-9
vncterm: 1.0-2
vzctl: 3.0.29-3pve8
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-1
ksm-control-daemon: 1.1-1

Thanks a lot.

 

[bread-baker]

I have similar issues with vz networking, but have not isolated why . it is something I need to look into later..

some of our vz's do not work the 1-st start after host boot.

restarting the vz makes them work here.

 

[dan]

I had to change the ip in my.cfg to 127.0.0.2 to make mysql start again. But I don't like this workaround.

 

[bread-baker]

which operating system is the vz using?

we also had to change my.cnf on recent ubuntu releases.

but have not had a problem with systems based on debian templates

 

[bread-baker]

when this issue occurs here, the loopback device is missing 127.0.0.1 .

we get:

1: lo: <LOOPBACK> mtu 16436 qdisc noop state DOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

instead of:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever

does that happen in your problem vz?