[Users] 64 bit kernel

ventas at dedicados.com.mx ventas at dedicados.com.mx
Sat May 22 20:54:51 EDT 2010


i found this on my messages log:

May 22 08:49:58 denver kernel: ip_conntrack version 2.4 (8192 buckets,
65536 max) - 312 bytes per conntrack
SERVER IS ONLINE
May 22 09:12:30 denver kernel: CT: 101: started
May 22 09:12:37 denver kernel: INFO: task auditd:5029 blocked for more
than 300 seconds.
May 22 09:12:38 denver kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 22 09:12:38 denver kernel: auditd        D ffff81007ca973a0     0 
5029      1          5081  5028 (NOTLB)
May 22 09:12:39 denver kernel:  ffff81007534dd68 0000000000000086
ffff81007534dd78 ffffffff800643ba
May 22 09:12:39 denver kernel:  ffff81007ca973a0 ffff81007fa7eda0
0000006ca8e6ae96 00000105ce5e67bc
May 22 09:12:39 denver kernel:  ffff81007ca975a8 ffffffff8048b780
ffffffff80313a00 ffff81007f8393e0
May 22 09:12:39 denver kernel: Call Trace:
May 22 09:12:39 denver kernel:  [<ffffffff800643ba>] thread_return+0x6a/0x177
May 22 09:12:39 denver kernel:  [<ffffffff88037791>]
:jbd:log_wait_commit+0xa3/0xf5
May 22 09:12:39 denver kernel:  [<ffffffff800a15b9>]
autoremove_wake_function+0x0/0x2e
May 22 09:12:39 denver kernel:  [<ffffffff88030b6f>]
:jbd:journal_stop+0x267/0x29b
May 22 09:12:39 denver kernel:  [<ffffffff80030ac4>]
__writeback_single_inode+0x1e9/0x328
May 22 09:12:41 denver kernel:  [<ffffffff800ff8a4>] sync_inode+0x24/0x33
May 22 09:12:42 denver kernel:  [<ffffffff8804d3ff>]
:ext3:ext3_sync_file+0x113/0x128
May 22 09:12:43 denver kernel:  [<ffffffff80064f7d>] mutex_lock+0xd/0x1d
May 22 09:12:44 denver kernel:  [<ffffffff80052755>] do_fsync+0x9f/0x12b
May 22 09:12:45 denver kernel:  [<ffffffff800ec266>] __do_fsync+0x47/0x59
May 22 09:12:46 denver kernel:  [<ffffffff80060166>] system_call+0x7e/0x83
May 22 09:12:47 denver kernel:
May 22 09:12:49 denver kernel: INFO: task syslogd:5081 blocked for more
than 300 seconds.
May 22 09:12:49 denver kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 22 09:12:51 denver kernel: syslogd       D ffff81007fa7eda0     0 
5081      1          5084  5029 (NOTLB)
May 22 09:12:52 denver kernel:  ffff8100753b3d68 0000000000000086
ffff81006e29c990 0000000000001272
May 22 09:12:53 denver kernel:  ffff81007fa7eda0 ffff81007fe920a0
0000006ca8e6b44e 00000105ce5e757d
May 22 09:12:54 denver kernel:  ffff81007fa7efa8 ffff81007fe8e000
ffffffff80313a00 ffff81007ca973a0
May 22 09:12:55 denver kernel: Call Trace:
May 22 09:12:56 denver kernel:  [<ffffffff88037791>]
:jbd:log_wait_commit+0xa3/0xf5
May 22 09:12:57 denver kernel:  [<ffffffff800a15b9>]
autoremove_wake_function+0x0/0x2e
May 22 09:12:58 denver kernel:  [<ffffffff88030b6f>]
:jbd:journal_stop+0x267/0x29b
May 22 09:12:59 denver kernel:  [<ffffffff80030ac4>]
__writeback_single_inode+0x1e9/0x328
May 22 09:13:01 denver kernel:  [<ffffffff800eb9c7>]
do_readv_writev+0x245/0x268
May 22 09:13:02 denver kernel:  [<ffffffff800ff8a4>] sync_inode+0x24/0x33
May 22 09:13:03 denver kernel:  [<ffffffff8804d3ff>]
:ext3:ext3_sync_file+0x113/0x128
May 22 09:13:04 denver kernel:  [<ffffffff80064f7d>] mutex_lock+0xd/0x1d
May 22 09:13:05 denver kernel:  [<ffffffff80052755>] do_fsync+0x9f/0x12b
May 22 09:13:06 denver kernel:  [<ffffffff800ec266>] __do_fsync+0x47/0x59
May 22 09:13:07 denver kernel:  [<ffffffff800602dd>] tracesys+0xd5/0xe0
May 22 09:13:08 denver kernel:
May 22 09:13:09 denver kernel: INFO: task syslogd:8888 blocked for more
than 300 seconds.
May 22 09:13:10 denver kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 22 09:13:11 denver kernel: syslogd       D ffff81007d1874e0     0 
8888   8512          8978  8944 (NOTLB)
May 22 09:13:13 denver kernel:  ffff8100706ffd68 0000000000000086
ffff8100706ffd78 ffffffff800643ba
May 22 09:13:14 denver kernel:  ffff81007d1874e0 ffff81007fe920a0
0000007a5a5ec51b 00000126cc7cbb6f
May 22 09:13:15 denver kernel:  ffff81007d1876e8 ffff81007fe8e000
ffff8100744d03c0 ffff81007fb340c0
May 22 09:13:16 denver kernel: Call Trace:
May 22 09:13:17 denver kernel:  [<ffffffff800643ba>] thread_return+0x6a/0x177
May 22 09:13:18 denver kernel:  [<ffffffff88037791>]
:jbd:log_wait_commit+0xa3/0xf5
May 22 09:13:20 denver kernel:  [<ffffffff800a15b9>]
autoremove_wake_function+0x0/0x2e
May 22 09:13:21 denver kernel:  [<ffffffff88030b6f>]
:jbd:journal_stop+0x267/0x29b
May 22 09:13:22 denver kernel:  [<ffffffff80030ac4>]
__writeback_single_inode+0x1e9/0x328
May 22 09:13:23 denver kernel:  [<ffffffff8002272f>] __up_read+0x19/0x7f
May 22 09:13:23 denver kernel:  [<ffffffff8006811d>]
do_page_fault+0x4fc/0x846
May 22 09:13:23 denver kernel:  [<ffffffff800ff8a4>] sync_inode+0x24/0x33
May 22 09:13:23 denver kernel:  [<ffffffff8804d3ff>]
:ext3:ext3_sync_file+0x113/0x128
May 22 09:13:23 denver kernel:  [<ffffffff80064f7d>] mutex_lock+0xd/0x1d
May 22 09:13:23 denver kernel:  [<ffffffff80052755>] do_fsync+0x9f/0x12b
May 22 09:13:23 denver kernel:  [<ffffffff800ec266>] __do_fsync+0x47/0x59
May 22 09:13:23 denver kernel:  [<ffffffff800602dd>] tracesys+0xd5/0xe0
May 22 09:13:23 denver kernel:
SERVER RESTART!
May 22 11:16:21 denver syslogd 1.4.1: restart.
May 22 11:16:21 denver kernel: klogd 1.4.1, log source = /proc/kmsg started.



> ok, kernel installed, rebooted and server is up, 10 min and i get locked.
> need a restart, same 10-15 min and ssh take me out.
>
> what can be the problem??
>
> is a centos5.4 64bit
>
>
> _______________________________________________
> Users mailing list
> Users at openvz.org
> https://openvz.org/mailman/listinfo/users
>




More information about the Users mailing list