Help me

iamgkz

New Member
Jun 12, 2009
5
0
1
Feb 12 04:14:33 ns1 kernel: EXT3-fs: recovery complete.
Feb 12 04:14:33 ns1 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Feb 12 04:18:24 ns1 kernel: kjournald starting. Commit interval 5 seconds
Feb 12 04:18:24 ns1 kernel: EXT3 FS on dm-3, internal journal
Feb 12 04:18:25 ns1 kernel: EXT3-fs: dm-3: 97 orphan inodes deleted
Feb 12 04:18:25 ns1 kernel: EXT3-fs: recovery complete.
Feb 12 04:18:26 ns1 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Feb 12 04:20:35 ns1 kernel: kjournald starting. Commit interval 5 seconds
Feb 12 04:20:35 ns1 kernel: EXT3 FS on dm-3, internal journal
Feb 12 04:20:36 ns1 kernel: EXT3-fs: dm-3: 97 orphan inodes deleted
Feb 12 04:20:36 ns1 kernel: EXT3-fs: recovery complete.
Feb 12 04:20:37 ns1 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Feb 12 04:27:21 ns1 kernel: kjournald starting. Commit interval 5 seconds
Feb 12 04:27:21 ns1 kernel: EXT3 FS on dm-3, internal journal
Feb 12 04:27:22 ns1 kernel: EXT3-fs: dm-3: 97 orphan inodes deleted
Feb 12 04:27:22 ns1 kernel: EXT3-fs: recovery complete.
Feb 12 04:27:23 ns1 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Feb 12 04:31:09 ns1 kernel: kjournald starting. Commit interval 5 seconds
Feb 12 04:31:09 ns1 kernel: EXT3 FS on dm-3, internal journal
Feb 12 04:31:10 ns1 kernel: EXT3-fs: dm-3: 97 orphan inodes deleted
Feb 12 04:31:10 ns1 kernel: EXT3-fs: recovery complete.
Feb 12 04:31:11 ns1 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Feb 12 06:25:02 ns1 kernel: imklog 3.18.6, log source = /proc/kmsg started.
Feb 12 06:25:02 ns1 rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="6926" x-info="http://www.rsyslog.com"] restart
Feb 12 06:33:58 ns1 kernel: printk: 6 messages suppressed.
Feb 12 06:39:30 ns1 kernel: printk: 5 messages suppressed.
Feb 12 08:35:03 ns1 kernel: printk: 1 messages suppressed.
Feb 12 08:35:08 ns1 kernel: printk: 3 messages suppressed.
Feb 12 08:35:19 ns1 kernel: printk: 1 messages suppressed.
Feb 12 08:35:24 ns1 kernel: printk: 2 messages suppressed.
Feb 12 09:38:58 ns1 kernel: printk: 2 messages suppressed.
Feb 12 09:40:04 ns1 kernel: printk: 4 messages suppressed.
Feb 12 09:40:11 ns1 kernel: printk: 3 messages suppressed.
Feb 12 09:46:45 ns1 kernel: printk: 2 messages suppressed.
Feb 12 09:47:21 ns1 kernel: printk: 1 messages suppressed.
Feb 12 09:52:05 ns1 kernel: printk: 2 messages suppressed.
Feb 12 10:13:18 ns1 kernel: printk: 4 messages suppressed.
Feb 12 10:21:10 ns1 kernel: vmbr0: port 5(vmtab302i0) entering disabled state
Feb 12 10:21:10 ns1 kernel: vmbr0: port 5(vmtab302i0) entering disabled state
Feb 12 11:26:05 ns1 kernel: printk: 1 messages suppressed.
Feb 12 12:03:47 ns1 kernel: printk: 2 messages suppressed.
Feb 12 12:08:17 ns1 kernel: printk: 3 messages suppressed.
Feb 12 13:06:45 ns1 kernel: printk: 5 messages suppressed.
Feb 12 13:07:54 ns1 kernel: printk: 7 messages suppressed.
Feb 12 13:07:59 ns1 kernel: printk: 17 messages suppressed.
Feb 12 13:08:21 ns1 kernel: printk: 8 messages suppressed.
Feb 12 13:18:38 ns1 kernel: vmbr0: port 6(vmtab101i0) entering disabled state
Feb 12 13:18:38 ns1 kernel: vmbr0: port 6(vmtab101i0) entering disabled state
Feb 12 13:19:26 ns1 kernel: CT: 208: stopped
Feb 12 13:21:03 ns1 kernel: CT: 208: started
Feb 12 13:31:04 ns1 kernel: printk: 3 messages suppressed.
Feb 12 13:35:42 ns1 kernel: printk: 1 messages suppressed.
Feb 12 14:34:30 ns1 kernel: printk: 11 messages suppressed.
Feb 12 14:39:28 ns1 kernel: printk: 3 messages suppressed.
Feb 12 16:17:36 ns1 kernel: CT: 208: stopped
Feb 12 16:18:18 ns1 kernel: CT: 208: started
Feb 12 16:38:52 ns1 kernel: printk: 1 messages suppressed.
Feb 12 17:13:30 ns1 kernel: printk: 10 messages suppressed.
Feb 12 17:18:26 ns1 kernel: printk: 2 messages suppressed.
Feb 12 17:21:10 ns1 kernel: printk: 2 messages suppressed.
Feb 12 17:27:42 ns1 kernel: printk: 5 messages suppressed.
Feb 12 17:28:02 ns1 kernel: printk: 6 messages suppressed.
Feb 12 17:58:55 ns1 kernel: printk: 5 messages suppressed.
Feb 12 17:59:00 ns1 kernel: printk: 1 messages suppressed.
Feb 12 17:59:08 ns1 kernel: printk: 2 messages suppressed.
Feb 12 17:59:09 ns1 kernel: printk: 1 messages suppressed.
Feb 12 17:59:14 ns1 kernel: printk: 1 messages suppressed.
Feb 12 17:59:20 ns1 kernel: printk: 4 messages suppressed.
Feb 12 17:59:26 ns1 kernel: printk: 8 messages suppressed.
Feb 12 17:59:31 ns1 kernel: printk: 1 messages suppressed.
Feb 12 18:00:00 ns1 kernel: printk: 6 messages suppressed.
Feb 12 18:00:10 ns1 kernel: printk: 1 messages suppressed.
Feb 12 18:00:17 ns1 kernel: printk: 6 messages suppressed.
Feb 12 18:00:35 ns1 kernel: printk: 4 messages suppressed.
Feb 12 18:00:59 ns1 kernel: printk: 2 messages suppressed.
Feb 12 18:01:34 ns1 kernel: printk: 3 messages suppressed.
Feb 12 18:01:46 ns1 kernel: printk: 1 messages suppressed.
Feb 12 18:02:09 ns1 kernel: printk: 5 messages suppressed.
Feb 12 18:02:41 ns1 kernel: printk: 3 messages suppressed.
Feb 12 18:59:12 ns1 kernel: printk: 2 messages suppressed.
Feb 12 19:29:15 ns1 kernel: printk: 4 messages suppressed.
Feb 12 23:45:35 ns1 kernel: printk: 9 messages suppressed.
Feb 13 06:25:02 ns1 kernel: Kernel logging (proc) stopped.
Feb 13 06:25:02 ns1 kernel: imklog 3.18.6, log source = /proc/kmsg started.
Feb 13 06:25:02 ns1 rsyslogd: [origin software="rsyslogd" swVersion="3.18.6" x-pid="6926" x-info="http://www.rsyslog.com"] restart
Feb 13 06:32:05 ns1 kernel: printk: 3 messages suppressed.
Feb 13 06:32:12 ns1 kernel: printk: 1 messages suppressed.
Feb 13 07:11:50 ns1 kernel: printk: 2 messages suppressed.
Feb 13 10:07:45 ns1 kernel: printk: 1 messages suppressed.
Feb 13 10:07:51 ns1 kernel: printk: 5 messages suppressed.
Feb 13 10:07:55 ns1 kernel: printk: 1 messages suppressed.
Feb 13 10:08:00 ns1 kernel: printk: 5 messages suppressed.
Feb 13 10:08:06 ns1 kernel: printk: 4 messages suppressed.
Feb 13 10:08:27 ns1 kernel: printk: 1 messages suppressed.
Feb 13 10:55:02 ns1 kernel: Route hash chain too long!
Feb 13 10:55:02 ns1 kernel: Adjust your secret_interval!


after this log my server creshed what's my problem?

thank you
 
What is the output of

# pveversion -v


ns1:~# pveversion -v
pve-manager: 1.5-5 (pve-manager/1.5/4627)
running kernel: 2.6.18-1-pve
proxmox-ve-2.6.18: 1.5-4
pve-kernel-2.6.18-1-pve: 2.6.18-4
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-7
vncterm: 0.9-2
vzctl: 3.0.23-1pve6
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-4
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!