Upgrade 1.1 to 1.3

[typo3usa]

logs -- they would be a good place to start.

 

[mhammett]

Here's a log from when the last startup till the crash.

Aug 22 12:37:56 fenix kernel: CT: 122: started
Aug 22 12:40:07 fenix kernel: CT: 123: started
Aug 22 12:42:14 fenix kernel: CT: 124: started
Aug 22 12:42:23 fenix kernel: CT: 127: started
Aug 22 12:42:34 fenix kernel: CT: 128: started
Aug 22 12:42:37 fenix kernel: ioctl32(mount:6206): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bf968be8) on /
Aug 22 12:42:37 fenix kernel: ioctl32(mount:6206): Unknown cmd fd(3) cmd(00001260){t:12;sz:0} arg(bf968bf0) on /
Aug 22 12:42:37 fenix kernel: ioctl32(mount:6206): Unknown cmd fd(3) cmd(801c0204){t:02;sz:28} arg(bf968bcc) on /
Aug 22 12:42:37 fenix kernel: ioctl32(mount:6206): Unknown cmd fd(3) cmd(80041272){t:12;sz:4} arg(bf968be8) on /
Aug 22 12:42:37 fenix kernel: ioctl32(mount:6206): Unknown cmd fd(3) cmd(00001260){t:12;sz:0} arg(bf968bf0) on /
Aug 22 12:42:37 fenix kernel: ioctl32(mount:6206): Unknown cmd fd(3) cmd(801c0204){t:02;sz:28} arg(bf968bcc) on /
Aug 22 12:42:39 fenix kernel: kvm: Nested Paging enabled
Aug 22 12:42:39 fenix kernel: loaded kvm module (kvm-kmod-devel-86)
Aug 22 13:17:16 fenix kernel: device vmtab129i0 entered promiscuous mode
Aug 22 13:17:16 fenix kernel: audit(1250965036.792:3): dev=vmtab129i0 prom=256 old_prom=0 auid=4294967295
Aug 22 13:17:16 fenix kernel: vmbr0: port 2(vmtab129i0) entering learning state
Aug 22 13:17:16 fenix kernel: vmbr0: topology change detected, propagating
Aug 22 13:17:16 fenix kernel: vmbr0: port 2(vmtab129i0) entering forwarding state
Aug 22 13:17:20 fenix kernel: device vmtab130i0 entered promiscuous mode
Aug 22 13:17:20 fenix kernel: audit(1250965040.368:4): dev=vmtab130i0 prom=256 old_prom=0 auid=4294967295
Aug 22 13:17:20 fenix kernel: vmbr0: port 3(vmtab130i0) entering learning state
Aug 22 13:17:20 fenix kernel: vmbr0: topology change detected, propagating
Aug 22 13:17:20 fenix kernel: vmbr0: port 3(vmtab130i0) entering forwarding state
Aug 25 15:05:14 fenix kernel: imklog 3.18.6, log source = /proc/kmsg started.

 

[dietmar]

After my upgrade from 1.1 to 1.3, it has been quite buggy. It responds to pings, but not to much else. I can open SSH, it asks for my username, but then just hangs.

Please can you be a bit more elaborate? I am especially interested what you mean by 'it'?

 

[mhammett]

Please can you be a bit more elaborate? I am especially interested what you mean by 'it'?

After my upgrade from 1.1 to 1.3, the server has been quite buggy. The server responds to pings, but not to much else. I can open SSH, the prompt asks for my username, but then just hangs.

When I'm at the physical console, I can login, but nothing ever completes successfully. I tell the server to restart networking and the restart hangs. I tell the server to shut down and the shutdown hangs. Well, hang isn't the proper word. With the networking, I can ctrl-c out back to the command prompt, though I can't do that with init as, well, the server has left the shell.

 

[mhammett]

I would like to note that the server initially works, but after some unknown amount of time, the server does as reported above.

 

[dietmar]

What happens when you stop the containers?

 

[mhammett]

They stop in a timely fashion (almost instantly). I stopped them all to be sure.

 

[mhammett]

Should my problems be broken out into a new thread?

I noticed that the VLAN I had created wasn't there anymore. Not sure if I removed it or it ran away in some other fashion. The machine has 3+ days of uptime, which normally would have resulted in a lack of response.

I recreated the VLAN. (new bridged device with the VLAN port (eth0.2) as a device. Maybe that's my failure?

 

[dietmar]

I noticed that the VLAN I had created wasn't there anymore. Not sure if I removed it or it ran away in some other fashion.

How did you create it?

 

[mhammett]

How did you create it?

I created a new bridge, with eth0.2 as the interface that was in it.

 

[dietmar]

I created a new bridge, with eth0.2 as the interface that was in it.

On the web interface? Or you directly edited /etc/network/interfaces?

 

[mhammett]

On the web interface? Or you directly edited /etc/network/interfaces?

In the web interface, yes. I've attached a screen shot.

fenix:~# cat /etc/network/interfaces
# network interface settings
auto lo
iface lo inet loopback

iface eth0 inet manual

auto vmbr0
iface vmbr0 inet static
address 10.1.5.7
netmask 255.255.255.0
gateway 10.1.5.1
bridge_ports eth0
bridge_stp off
bridge_fd 0

auto vmbr1
iface vmbr1 inet static
address 65.182.165.39
netmask 255.255.255.0
bridge_ports eth0.2
bridge_stp off
bridge_fd 0

 

[dietmar]

Are you sure you want to use eth0 and eth0.2 - what is the advantage of the vlan in this case?

 

[mhammett]

Are you sure you want to use eth0 and eth0.2 - what is the advantage of the vlan in this case?

No VLAN tagging is for internal traffic. VLAN 2 is for public IPs.

 

[mhammett]

okay, so it seems that whenever I add that network bridge, ProxMox becomes unstable. It stopped responding 3 days 14 hours ago, which is not long after I set it up again.

 

[mhammett]

Are you sure you want to use eth0 and eth0.2 - what is the advantage of the vlan in this case?

What's the next step in figuring out why ProxMox stops responding?

 

[dietmar]

Whats the output of

# pveversion -v

 

[mhammett]

Whats the output of

# pveversion -v

Here is the output you requested.

fenix:~# pveversion -v
pve-manager: 1.3-1 (pve-manager/1.3/4023)
qemu-server: 1.0-14
pve-kernel: 2.6.24-10
pve-kvm: 86-3
pve-firmware: 1
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.1-2
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1

 

[dietmar]

What vlan mode do you use? Does it work stable without vlan (or when you use another mode)?

 

[mhammett]

What vlan mode do you use? Does it work stable without vlan (or when you use another mode)?

When the VLAN wasn't present, the system was up for several days.

I'm not sure what you mean by VLAN mode. A previous post of mine shows the configuration.