After a clean Proxmox 3.4 install, proxmox stops responding

A

atasever

New Member
Mar 22, 2009
9
0
1
Hi,

After upgrading to 3.4 with a clean install, server started to hang on frequently.
Syslog is filled with "Blabla blocked for more than 120 seconds" errors.

any help is appreciated.

Thanks

Code: 
Aug 14 11:52:28 urgup kernel: INFO: task sshd:106635 blocked for more than 120 seconds.
Aug 14 11:52:28 urgup kernel:      Tainted: P           ---------------    2.6.32-39-pve #1
Aug 14 11:52:28 urgup kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Aug 14 11:52:28 urgup kernel: sshd          D ffff880838a24b40     0 106635   2855    0 0x00000000
Aug 14 11:52:28 urgup kernel: ffff8806b1c77bf8 0000000000000082 ffff8808399ab880 00000000000000db
Aug 14 11:52:28 urgup kernel: ffff880700000000 ffff8806b1c77ac8 ffffffff811c5f10 dead000000100100
Aug 14 11:52:28 urgup kernel: dead000000200200 ffff880837accc00 00000001053c8131 00000000000000db
Aug 14 11:52:28 urgup kernel: Call Trace:
Aug 14 11:52:28 urgup kernel: [<ffffffff811c5f10>] ? pollwake+0x0/0x70
Aug 14 11:52:28 urgup kernel: [<ffffffff81562444>] schedule_timeout+0x204/0x300
Aug 14 11:52:28 urgup kernel: [<ffffffff81058143>] ? __wake_up+0x53/0x70
Aug 14 11:52:28 urgup kernel: [<ffffffff81561c87>] wait_for_completion+0xd7/0x110
Aug 14 11:52:28 urgup kernel: [<ffffffff8106da40>] ? default_wake_function+0x0/0x20
Aug 14 11:52:28 urgup kernel: [<ffffffff810a0096>] flush_work+0x76/0xc0
Aug 14 11:52:28 urgup kernel: [<ffffffff8109e3b0>] ? wq_barrier_func+0x0/0x20
Aug 14 11:52:28 urgup kernel: [<ffffffff810a0132>] flush_delayed_work+0x52/0x70
Aug 14 11:52:28 urgup kernel: [<ffffffff81344595>] tty_flush_to_ldisc+0x15/0x20
Aug 14 11:52:28 urgup kernel: [<ffffffff81340c6c>] n_tty_read+0x1dc/0x960
Aug 14 11:52:28 urgup kernel: [<ffffffff8106da40>] ? default_wake_function+0x0/0x20
Aug 14 11:52:28 urgup kernel: [<ffffffff8133b4c2>] tty_read+0x92/0xf0
Aug 14 11:52:28 urgup kernel: [<ffffffff811ae12e>] vfs_read+0x9e/0x190
Aug 14 11:52:28 urgup kernel: [<ffffffff811ae26a>] sys_read+0x4a/0x90
Aug 14 11:52:28 urgup kernel: [<ffffffff8109576b>] ? sys_rt_sigprocmask+0x8b/0x120
Aug 14 11:52:28 urgup kernel: [<ffffffff8100b182>] system_call_fastpath+0x16/0x1b

Code: 
proxmox-ve-2.6.32: 3.4-156 (running kernel: 2.6.32-39-pve)
pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
pve-kernel-2.6.32-39-pve: 2.6.32-156
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-17
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1
 
Hi,

have you this problems also with the
pve-kernel-2.6.32-40?
 
After running for 20 hours , I am getting the same error with the new kernel. Is there anything else that i can try ?

Thanks
 
You must log in or register to reply here.
Top Bottom