[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1228
  • Last Modified:

Kernel Bug Error

Hello Experts!

I have installed SME 6.0 for my proxy server.  The said server is running properly for almost a year but this time there are cases in which it encounters "kernel bug error".  By the time it occurs, all workstations could not longer connect to the internet.

With this, I have to restart the said proxy server.  After restarting it, all operations will back to normal.

I need some idea on how to fix this problem.

Any help is greatly appreciated!


eNTRANCE2002 :-)
0
Renante Entera
Asked:
Renante Entera
  • 6
  • 6
  • 3
  • +1
3 Solutions
 
wesly_chenCommented:
Hi,

> it encounters "kernel bug error".  
Could you post the error messages (in /var/log/messages by default) so people can have more understanding?

Wesly
0
 
wesly_chenCommented:
Hi,

   SME server is a customized Linux software packages based on RedHat Linux, so you might want to check the
updates from (6.0.1 is the latest version)
http://contribs.org/modules/phpwiki/index.php?Downloads

Regards,

Wesly
0
 
jlevieCommented:
If this server has been running correctly for a year or so and suddenly has started failing I'd be suspicious of something that has changed recently or some partial hardware failure. Have you made any changes to the box shortly before this behaviour surfaced? Have you checked to see that all of the cooling fans are operating properly?

Has the disk been fscked at boot recently? It might be desireable to run a memory test on the system (see http://www.memtest86.com/) to make sure you don't have a bad or flaky spot in memory.
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
The--CaptainCommented:
Running memtest may not be feasible on a production box (I have a box that is acting up, but I can't do this until we can find a time to switch it out with the cold-standby - yes, we actually have to schedule downtime of under a minute).

In any case, I'll be opening my own thread on how to diagnose potential hardware problems on a production linux box (since I'd really like to know).

Cheers,
-Jon

0
 
Renante EnteraAuthor Commented:
this is the logs that i found inside /var/log/messages.  Will you please help me on what this error messages means???

Nov 11 11:36:17 f1-sakurai kernel: kernel BUG at page_alloc.c:203!
Nov 11 11:36:17 f1-sakurai kernel: invalid operand: 0000
Nov 11 11:36:17 f1-sakurai kernel: appletalk dmfe ipt_LOG ipt_MASQUERADE ipt_state ipt_TOS ip_nat_ftp ip_conntrack_ftp iptabl$
Nov 11 11:36:17 f1-sakurai kernel: CPU:    0
Nov 11 11:36:17 f1-sakurai kernel: EIP:    0010:[rmqueue+463/832]    Not tainted
Nov 11 11:36:17 f1-sakurai kernel: EIP:    0010:[<c013db3f>]    Not tainted
Nov 11 11:36:17 f1-sakurai kernel: EFLAGS: 00010086
Nov 11 11:36:17 f1-sakurai kernel:
Nov 11 11:36:17 f1-sakurai kernel: EIP is at rmqueue [kernel] 0x1cf (2.4.20-18.7smp)
Nov 11 11:36:17 f1-sakurai kernel: eax: 000000a4   ebx: c1000650   ecx: c030c0a0   edx: 0000001c
Nov 11 11:36:17 f1-sakurai kernel: esi: c030d288   edi: 00000004   ebp: 00000002   esp: ccbd1e70
Nov 11 11:36:17 f1-sakurai kernel: ds: 0018   es: 0018   ss: 0018
Nov 11 11:36:17 f1-sakurai squid[2255]: Squid Parent: child process 2258 exited due to signal 11
Nov 11 11:36:17 f1-sakurai kernel: Process squid (pid: 2258, stackpage=ccbd1000)
Nov 11 11:36:17 f1-sakurai kernel: Stack: 00000000 0000001c 00000212 c030d2a0 00000000 c030c0a0 00000000 c030f7f8
Nov 11 11:36:17 f1-sakurai kernel:        0000030f 00000000 c013de4b cc0e2800 c1050de0 00000001 c030f7f0 000001f0
Nov 11 11:36:17 f1-sakurai kernel:        00000000 ccbd1fa8 cc0e2e80 cc0774c0 c013e130 c01565a3 cd996980 cc0e2e80
Nov 11 11:36:17 f1-sakurai kernel: Call Trace:   [__alloc_pages+123/848] __alloc_pages [kernel] 0x7b (0xccbd1e98))
Nov 11 11:36:17 f1-sakurai kernel: Call Trace:   [<c013de4b>] __alloc_pages [kernel] 0x7b (0xccbd1e98))
Nov 11 11:36:17 f1-sakurai kernel: [__get_free_pages+16/32] __get_free_pages [kernel] 0x10 (0xccbd1ec0))
Nov 11 11:36:17 f1-sakurai kernel: [<c013e130>] __get_free_pages [kernel] 0x10 (0xccbd1ec0))
Nov 11 11:36:17 f1-sakurai kernel: [__pollwait+51/144] __pollwait [kernel] 0x33 (0xccbd1ec4))
Nov 11 11:36:17 f1-sakurai kernel: [<c01565a3>] __pollwait [kernel] 0x33 (0xccbd1ec4))
Nov 11 11:36:17 f1-sakurai kernel: [tcp_poll+46/336] tcp_poll [kernel] 0x2e (0xccbd1ed8))
Nov 11 11:36:17 f1-sakurai kernel: [<c020538e>] tcp_poll [kernel] 0x2e (0xccbd1ed8))
Nov 11 11:36:17 f1-sakurai kernel: [destroy_inode+61/80] destroy_inode [kernel] 0x3d (0xccbd1f00))
Nov 11 11:36:17 f1-sakurai kernel: [<c015b86d>] destroy_inode [kernel] 0x3d (0xccbd1f00))
Nov 11 11:36:17 f1-sakurai kernel: [sock_poll+31/48] sock_poll [kernel] 0x1f (0xccbd1f14))
Nov 11 11:36:17 f1-sakurai kernel: [<c01e266f>] sock_poll [kernel] 0x1f (0xccbd1f14))
Nov 11 11:36:17 f1-sakurai kernel: [<c01e266f>] sock_poll [kernel] 0x1f (0xccbd1f14))
Nov 11 11:36:17 f1-sakurai kernel: [do_pollfd+69/128] do_pollfd [kernel] 0x45 (0xccbd1f24))
Nov 11 11:36:17 f1-sakurai kernel: [<c0156e15>] do_pollfd [kernel] 0x45 (0xccbd1f24))
Nov 11 11:36:17 f1-sakurai kernel: [do_poll+134/224] do_pollfd [kernel] 0x106 (0xccbd1f40))
Nov 11 11:36:17 f1-sakurai kernel: [<c0156ed6>] do_pollfd [kernel] 0x106 (0xccbd1f40))
Nov 11 11:36:17 f1-sakurai kernel: [sys_poll+610/906] sys_poll [kernel] 0x262 (0xccbd1f6c))
Nov 11 11:36:17 f1-sakurai kernel: [<c0157192>] sys_poll [kernel] 0x262 (0xccbd1f6c))
Nov 11 11:36:17 f1-sakurai kernel: [filp_close+149/160] filp_close [kernel] 0x95 (0xccbd1f8c))
Nov 11 11:36:17 f1-sakurai kernel: [<c0145be5>] filp_close [kernel] 0x95 (0xccbd1f8c))
Nov 11 11:36:17 f1-sakurai kernel: [system_call+51/56] system_call [kernel] 0x33 (0xccbd1fc0))
Nov 11 11:36:17 f1-sakurai kernel: [<c0108be3>] system_call [kernel] 0x33 (0xccbd1fc0))
Nov 11 11:36:17 f1-sakurai kernel:
Nov 11 11:36:17 f1-sakurai kernel:
Nov 11 11:36:17 f1-sakurai kernel: Code: 0f 0b cb 00 e8 56 25 c0 83 ee 0c 4d 8b 06 8d 4d 01 d1 ef 89
Nov 11 11:36:20 f1-sakurai squid[2255]: Squid Parent: child process 9081 started
Nov 11 11:36:20 f1-sakurai (squid): Cannot open HTTP Port
Nov 11 11:36:20 f1-sakurai squid[2255]: Squid Parent: child process 9081 exited due to signal 6
Nov 11 11:36:23 f1-sakurai squid[2255]: Squid Parent: child process 9084 started
Nov 11 11:36:24 f1-sakurai squid[2255]: Squid Parent: child process 9084 exited due to signal 6
Nov 11 11:36:27 f1-sakurai squid[2255]: Squid Parent: child process 9087 started
Nov 11 11:36:27 f1-sakurai squid[2255]: Squid Parent: child process 9087 exited due to signal 6
Nov 11 11:36:30 f1-sakurai squid[2255]: Squid Parent: child process 9090 started
Nov 11 11:36:30 f1-sakurai squid[2255]: Squid Parent: child process 9090 exited due to signal 6
Nov 11 11:36:33 f1-sakurai squid[2255]: Squid Parent: child process 9093 started
Nov 11 11:36:34 f1-sakurai squid[2255]: Squid Parent: child process 9093 exited due to signal 6
Nov 11 11:36:30 f1-sakurai squid[2255]: Squid Parent: child process 9090 started
Nov 11 11:36:30 f1-sakurai squid[2255]: Squid Parent: child process 9090 exited due to signal 6
Nov 11 11:36:33 f1-sakurai squid[2255]: Squid Parent: child process 9093 started
Nov 11 11:36:34 f1-sakurai squid[2255]: Squid Parent: child process 9093 exited due to signal 6
Nov 11 11:36:34 f1-sakurai squid[2255]: Exiting due to repeated, frequent failures
Nov 11 11:36:37 f1-sakurai kernel:  <4>denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:02:56:61:c9:08:00 SRC=192.168.10.123 $
Nov 11 11:36:37 f1-sakurai kernel: denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:30:0a:15:f9:7e:08:00 SRC=10.0.0.2 DST=255.25$
Nov 11 11:36:37 f1-sakurai kernel: denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:02:56:61:c9:08:00 SRC=192.168.10.123 DST=$
0
 
wesly_chenCommented:
> kernel BUG at page_alloc.c:203!
It's well-known kernel bug. Usually it happens when machine is under high load or heavy traffic.

Please check
http://contribs.org/modules/phpwiki/index.php?Downloads
For kernel upgrade (or upgrade to 6.0.1)

Wesly
0
 
Renante EnteraAuthor Commented:
Hello wesly_chen!

Thanks for the information about giving me an idea on what "kernel BUG at page_alloc.c:203!" means...

Anyway, I've decided to reinstall the machine using SME 6.0.1.  As of now, it's under observation.

Perhaps, I will have to observe it for a week before I close this question.


Regards!
eNTRANCE2002 :-)
0
 
wesly_chenCommented:
> kernel BUG at page_alloc.c:203!
I saw this error messages on RedHat 7.3 with kernel version 2.4.14. After upgrade to latest one
(2.4.19 has already fix the bug) 2.4.20, things went normal.

Since SME server is a customized Linux software packages based on RedHat Linux,
you might want to check the kernel version as well.

Regards,

Wesly
0
 
Renante EnteraAuthor Commented:
Yesterday, we encounter again the Kernel Bug on our server.  It seems upgrading the server doesn't work out.  I will post again the log file.

Dec  2 10:09:44 f1-sakurai kernel: kernel BUG at page_alloc.c:213!
Dec  2 10:09:44 f1-sakurai kernel: invalid operand: 0000
Dec  2 10:09:44 f1-sakurai kernel: dmfe ipt_LOG ipt_MASQUERADE ipt_state ipt_TOS ip_conntrack_ftp ip_nat_ftp iptable_mangle iptable_nat ip_conntrack iptable_filter ip_tables ide-scsi scsi_mod i
Dec  2 10:09:44 f1-sakurai kernel: CPU:    0
Dec  2 10:09:44 f1-sakurai kernel: EIP:    0010:[rmqueue+553/784]    Not tainted
Dec  2 10:09:44 f1-sakurai kernel: EIP:    0010:[<c0135fc9>]    Not tainted
Dec  2 10:09:44 f1-sakurai kernel: EFLAGS: 00010086
Dec  2 10:09:44 f1-sakurai kernel:
Dec  2 10:09:44 f1-sakurai kernel: EIP is at rmqueue [kernel] 0x229 (2.4.20-18.7)
Dec  2 10:09:44 f1-sakurai kernel: eax: 00000020   ebx: c1000618   ecx: 00000000   edx: 0000001b
Dec  2 10:09:44 f1-sakurai kernel: esi: c02deb00   edi: 00000001   ebp: 00001000   esp: c692fde8
Dec  2 10:09:44 f1-sakurai kernel: ds: 0018   es: 0018   ss: 0018
Dec  2 10:09:44 f1-sakurai kernel: Process perl5.6.1 (pid: 5631, stackpage=c692f000)
Dec  2 10:09:44 f1-sakurai kernel: Stack: 00000000 0000001b 00000212 c02ded64 00000000 c02deb00 00001000 c02df3e0
Dec  2 10:09:44 f1-sakurai kernel:        0000030f 00000000 c013624b 00000d7a 00000020 c2d1eee8 00000001 c02df3d8
Dec  2 10:09:44 f1-sakurai kernel:        000001d2 c1003910 c2d1eee8 00104025 cc1abb00 c0128044 00000000 c01d1b2f
Dec  2 10:09:44 f1-sakurai kernel: Call Trace:   [__alloc_pages+123/848] __alloc_pages [kernel] 0x7b (0xc692fe10))
Dec  2 10:09:44 f1-sakurai kernel: Call Trace:   [<c013624b>] __alloc_pages [kernel] 0x7b (0xc692fe10))
Dec  2 10:09:44 f1-sakurai kernel: [do_anonymous_page+212/544] do_anonymous_page [kernel] 0xd4 (0xc692fe3c))
Dec  2 10:09:44 f1-sakurai kernel: [<c0128044>] do_anonymous_page [kernel] 0xd4 (0xc692fe3c))
Dec  2 10:09:44 f1-sakurai kernel: [__kfree_skb+271/288] __kfree_skb [kernel] 0x10f (0xc692fe44))
Dec  2 10:09:44 f1-sakurai kernel: [<c01d1b2f>] __kfree_skb [kernel] 0x10f (0xc692fe44))
Dec  2 10:09:44 f1-sakurai kernel: [do_no_page+60/624] do_no_page [kernel] 0x3c (0xc692fe60))
Dec  2 10:09:44 f1-sakurai kernel: [<c01281cc>] do_no_page [kernel] 0x3c (0xc692fe60))
Dec  2 10:09:44 f1-sakurai kernel: [sock_def_readable+34/80] sock_def_readable [kernel] 0x22 (0xc692fe88))
Dec  2 10:09:44 f1-sakurai kernel: [<c01d1462>] sock_def_readable [kernel] 0x22 (0xc692fe88))
Dec  2 10:09:44 f1-sakurai kernel: [handle_mm_fault+220/352] handle_mm_fault [kernel] 0xdc (0xc692feac))
Dec  2 10:09:44 f1-sakurai kernel: [<c01284dc>] handle_mm_fault [kernel] 0xdc (0xc692feac))
Dec  2 10:09:44 f1-sakurai kernel: [do_generic_file_read+541/1088] do_generic_file_read [kernel] 0x21d (0xc692fedc))
Dec  2 10:09:44 f1-sakurai kernel: [<c012b14d>] do_generic_file_read [kernel] 0x21d (0xc692fedc))
Dec  2 10:09:44 f1-sakurai kernel: [do_generic_file_read+1072/1088] do_generic_file_read [kernel] 0x430 (0xc692fee8))
Dec  2 10:09:44 f1-sakurai kernel: [<c012b360>] do_generic_file_read [kernel] 0x430 (0xc692fee8))
Dec  2 10:09:44 f1-sakurai kernel: [do_page_fault+378/1195] do_page_fault [kernel] 0x17a (0xc692ff08))
Dec  2 10:09:44 f1-sakurai kernel: [<c01145ea>] do_page_fault [kernel] 0x17a (0xc692ff08))
Dec  2 10:09:44 f1-sakurai kernel: [sys_read+226/240] sys_read [kernel] 0xe2 (0xc692ff6c))
Dec  2 10:09:44 f1-sakurai kernel: [<c013d672>] sys_read [kernel] 0xe2 (0xc692ff6c))
Dec  2 10:09:44 f1-sakurai kernel: [sys_brk+185/240] sys_brk [kernel] 0xb9 (0xc692ff94))
Dec  2 10:09:44 f1-sakurai kernel: [<c01287f9>] sys_brk [kernel] 0xb9 (0xc692ff94))
Dec  2 10:09:44 f1-sakurai kernel: [sys_munmap+50/80] sys_munmap [kernel] 0x32 (0xc692ffa4))
Dec  2 10:09:44 f1-sakurai kernel: [<c01296f2>] sys_munmap [kernel] 0x32 (0xc692ffa4))
Dec  2 10:09:44 f1-sakurai kernel: [do_page_fault+0/1195] do_page_fault [kernel] 0x0 (0xc692ffb0))
Dec  2 10:09:44 f1-sakurai kernel: [<c0114470>] do_page_fault [kernel] 0x0 (0xc692ffb0))
Dec  2 10:09:44 f1-sakurai kernel: [error_code+52/60] error_code [kernel] 0x34 (0xc692ffb8))
Dec  2 10:09:44 f1-sakurai kernel: [<c01089b4>] error_code [kernel] 0x34 (0xc692ffb8))
Dec  2 10:09:44 f1-sakurai kernel:
Dec  2 10:09:44 f1-sakurai kernel:
Dec  2 10:09:44 f1-sakurai kernel: Code: 0f 0b d5 00 f6 3d 23 c0 ff 74 24 08 9d c7 43 14 01 00 00 00
Dec  2 10:09:44 f1-sakurai kernel:  <1>Unable to handle kernel paging request at virtual address 0018efff
Dec  2 10:09:44 f1-sakurai kernel:  printing eip:
Dec  2 10:09:44 f1-sakurai kernel: c012809a
Dec  2 10:09:44 f1-sakurai kernel: *pde = 00000000
Dec  2 10:09:44 f1-sakurai kernel: Oops: 0002
Dec  2 10:09:44 f1-sakurai kernel: dmfe ipt_LOG ipt_MASQUERADE ipt_state ipt_TOS ip_conntrack_ftp ip_nat_ftp iptable_mangle iptable_nat ip_conntrack iptable_filter ip_tables ide-scsi scsi_mod i
Dec  2 10:09:44 f1-sakurai kernel: CPU:    0
Dec  2 10:09:44 f1-sakurai kernel: EIP:    0010:[do_anonymous_page+298/544]    Not tainted
Dec  2 10:09:44 f1-sakurai kernel: EIP:    0010:[<c012809a>]    Not tainted
Dec  2 10:09:44 f1-sakurai kernel: EFLAGS: 00010246
Dec  2 10:09:44 f1-sakurai kernel:
Dec  2 10:09:44 f1-sakurai kernel: EIP is at do_anonymous_page [kernel] 0x12a (2.4.20-18.7)
Dec  2 10:09:44 f1-sakurai kernel: eax: 00000000   ebx: c10005e0   ecx: 00000400   edx: 0000001a
Dec  2 10:09:44 f1-sakurai kernel: esi: c9905e64   edi: 0018efff   ebp: cc1a4100   esp: c60e5e40
Dec  2 10:09:44 f1-sakurai kernel: ds: 0018   es: 0018   ss: 0018
Dec  2 10:09:44 f1-sakurai kernel: Process perl5.6.1 (pid: 5629, stackpage=c60e5000)
Dec  2 10:09:44 f1-sakurai kernel: Stack: 00000246 0000030f 00000000 c013624b 00000001 0839934c c9905e64 cf6e6880
Dec  2 10:09:44 f1-sakurai kernel:        c01281cc cf6e6880 c3191600 c9905e64 c1ed6080 00000001 0839934c 00001000
Dec  2 10:09:44 f1-sakurai kernel:        00000000 401d5000 00001000 c0220970 c3191218 cf6e6884 cf6e6880 00000001
Dec  2 10:09:44 f1-sakurai kernel: Call Trace:   [__alloc_pages+123/848] __alloc_pages [kernel] 0x7b (0xc60e5e4c))
Dec  2 10:09:44 f1-sakurai kernel: Call Trace:   [<c013624b>] __alloc_pages [kernel] 0x7b (0xc60e5e4c))
Dec  2 10:09:44 f1-sakurai kernel: [do_no_page+60/624] do_no_page [kernel] 0x3c (0xc60e5e60))
Dec  2 10:09:44 f1-sakurai kernel: [<c01281cc>] do_no_page [kernel] 0x3c (0xc60e5e60))
Dec  2 10:09:44 f1-sakurai kernel: [rb_insert_color+112/240] rb_insert_color [kernel] 0x70 (0xc60e5e8c))
Dec  2 10:09:44 f1-sakurai kernel: [<c0220970>] rb_insert_color [kernel] 0x70 (0xc60e5e8c))
Dec  2 10:09:44 f1-sakurai kernel: [handle_mm_fault+220/352] handle_mm_fault [kernel] 0xdc (0xc60e5eac))
Dec  2 10:09:44 f1-sakurai kernel: [<c01284dc>] handle_mm_fault [kernel] 0xdc (0xc60e5eac))
Dec  2 10:09:44 f1-sakurai kernel: [do_mmap_pgoff+1175/1360] do_mmap_pgoff [kernel] 0x497 (0xc60e5ecc))
Dec  2 10:09:44 f1-sakurai kernel: [<c0128ee7>] do_mmap_pgoff [kernel] 0x497 (0xc60e5ecc))
Dec  2 10:09:44 f1-sakurai kernel: [do_mmap_pgoff+1184/1360] do_mmap_pgoff [kernel] 0x4a0 (0xc60e5ee0))
Dec  2 10:09:44 f1-sakurai kernel: [<c0128ef0>] do_mmap_pgoff [kernel] 0x4a0 (0xc60e5ee0))
Dec  2 10:09:44 f1-sakurai kernel: [do_page_fault+378/1195] do_page_fault [kernel] 0x17a (0xc60e5f08))
Dec  2 10:09:44 f1-sakurai kernel: [<c01145ea>] do_page_fault [kernel] 0x17a (0xc60e5f08))
Dec  2 10:09:44 f1-sakurai kernel: [sys_mprotect+288/521] sys_mprotect [kernel] 0x120 (0xc60e5f78))
Dec  2 10:09:44 f1-sakurai kernel: [<c012dfe0>] sys_mprotect [kernel] 0x120 (0xc60e5f78))
Dec  2 10:09:44 f1-sakurai kernel: [sys_brk+185/240] sys_brk [kernel] 0xb9 (0xc60e5f94))
Dec  2 10:09:44 f1-sakurai kernel: [<c01287f9>] sys_brk [kernel] 0xb9 (0xc60e5f94))
Dec  2 10:09:44 f1-sakurai kernel: [do_page_fault+0/1195] do_page_fault [kernel] 0x0 (0xc60e5fb0))
Dec  2 10:09:44 f1-sakurai kernel: [<c0114470>] do_page_fault [kernel] 0x0 (0xc60e5fb0))
Dec  2 10:09:44 f1-sakurai kernel: [error_code+52/60] error_code [kernel] 0x34 (0xc60e5fb8))
Dec  2 10:09:44 f1-sakurai kernel: [<c01089b4>] error_code [kernel] 0x34 (0xc60e5fb8))
Dec  2 10:09:44 f1-sakurai kernel:
Dec  2 10:09:44 f1-sakurai kernel:
Dec  2 10:09:44 f1-sakurai kernel: Code: f3 ab 8b 0d 30 b2 34 c0 8b 54 24 30 8b 02 c1 e8 0c 8d 14 c5
Dec  2 10:09:45 f1-sakurai kernel:  <4>denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:02:56:61:c9:08:00 SRC=203.167.85.123 DST=255.255.255.255 LEN=344 TOS=0x00 PREC=0x00 TTL=128 ID=8663 PROTO=UDP SPT=68 DPT=67 LEN=324
Dec  2 10:09:45 f1-sakurai kernel: denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:30:0a:15:f9:7e:08:00 SRC=10.0.0.2 DST=255.255.255.255 LEN=576 TOS=0x00 PREC=0x00 TTL=32 ID=5999 DF PROTO=UDP SPT=67 DPT=68 LEN=556
Dec  2 10:09:45 f1-sakurai kernel: denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:02:56:61:c9:08:00 SRC=203.167.85.123 DST=255.255.255.255 LEN=344 TOS=0x00 PREC=0x00 TTL=128 ID=8664 PROTO=UDP SPT=68 DPT=67 LEN=324
Dec  2 10:09:45 f1-sakurai kernel: denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:30:0a:15:f9:7e:08:00 SRC=10.0.0.2 DST=255.255.255.255 LEN=576 TOS=0x00 PREC=0x00 TTL=32 ID=30714 DF PROTO=UDP SPT=67 DPT=68 LEN=556
Dec  2 10:09:45 f1-sakurai kernel: denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:02:56:61:c9:08:00 SRC=203.167.85.123 DST=255.255.255.255 LEN=344 TOS=0x00 PREC=0x00 TTL=128 ID=8665 PROTO=UDP SPT=68 DPT=67 LEN=324
Dec  2 10:09:45 f1-sakurai kernel: denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:30:0a:15:f9:7e:08:00 SRC=10.0.0.2 DST=255.255.255.255 LEN=576 TOS=0x00 PREC=0x00 TTL=32 ID=15376 DF PROTO=UDP SPT=67 DPT=68 LEN=556
Dec  2 10:09:45 f1-sakurai kernel: denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:02:56:61:c9:08:00 SRC=203.167.85.123 DST=255.255.255.255 LEN=344 TOS=0x00 PREC=0x00 TTL=128 ID=8666 PROTO=UDP SPT=68 DPT=67 LEN=324
Dec  2 10:09:45 f1-sakurai kernel: denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:30:0a:15:f9:7e:08:00 SRC=10.0.0.2 DST=255.255.255.255 LEN=576 TOS=0x00 PREC=0x00 TTL=32 ID=36798 DF PROTO=UDP SPT=67 DPT=68 LEN=556
Dec  2 10:10:08 f1-sakurai kernel: denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:02:56:61:c9:08:00 SRC=203.167.85.123 DST=255.255.255.255 LEN=344 TOS=0x00 PREC=0x00 TTL=128 ID=8861 PROTO=UDP SPT=68 DPT=67 LEN=324
Dec  2 10:10:08 f1-sakurai kernel: denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:30:0a:15:f9:7e:08:00 SRC=10.0.0.2 DST=255.255.255.255 LEN=576 TOS=0x00 PREC=0x00 TTL=32 ID=13712 DF PROTO=UDP SPT=67 DPT=68 LEN=556
Dec  2 10:10:08 f1-sakurai kernel: denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:02:56:61:c9:08:00 SRC=203.167.85.123 DST=255.255.255.255 LEN=344 TOS=0x00 PREC=0x00 TTL=128 ID=8862 PROTO=UDP SPT=68 DPT=67 LEN=324
0
 
Renante EnteraAuthor Commented:
I just want to ask if wat does this log means.

New Log:

Dec  2 10:09:45 f1-sakurai kernel:  <4>denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:02:56:61:c9:08:00 SRC=203.167.85.123 DST=255.255.255.255 LEN=344 TOS=0x00 PREC=0x00 TTL=128 ID=8663 PROTO=UDP SPT=68 DPT=67 LEN=324
Dec  2 10:09:45 f1-sakurai kernel: denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:30:0a:15:f9:7e:08:00 SRC=10.0.0.2 DST=255.255.255.255 LEN=576 TOS=0x00 PREC=0x00 TTL=32 ID=5999 DF PROTO=UDP SPT=67 DPT=68 LEN=556

Old log:
Nov 11 11:43:12 f1-sakurai kernel: denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:02:56:61:c9:08:00 SRC=192.168.10.123 DST=$
Nov 11 11:43:12 f1-sakurai kernel: denylog:IN=eth1 OUT= MAC=ff:ff:ff:ff:ff:ff:00:30:0a:15:f9:7e:08:00 SRC=10.0.0.2 DST=255.25$

The computer who is using an ip address 203.167.85.123 and 192.168.1.123 is the same.  Is it possible that this particular Computer is the cause of the kernel bug of our Server???
0
 
jlevieCommented:
> The computer who is using an ip address 203.167.85.123 and 192.168.1.123 is the same.

Not necessarily. If those IP's are outside of your local network, and it sounds like that's the case, the MAC you see will be that of the next router upstream.

The back trace you show looks to me like it might be a hardware problem. Have you checked to be sure that all of the fans are operating properly. A "slow" fan that allows the CPU to overheat can cause odd problems like this. Once cooling has been ruled out as a cause I'd recommend running at least two passes of memtest86 to look for a memory, cache, or memory bus fault.
0
 
The--CaptainCommented:
My own kernel bug problem seems to have subsided (knock on wood) after asking my client to re-seat all component parts (so it *does* seem to be hardware-related).  Unfortunately for you, this is probably not related to your problem if you have no cause to suspect loose parts (the box I was working on was recently shipped from Chicago to Newark, so I was rather suspicious).

>The back trace you show looks to me like it might be a hardware problem. Have you checked to be sure that all of the fans
>are operating properly. A "slow" fan that allows the CPU to overheat can cause odd problems like this. Once cooling has been
>ruled out as a cause I'd recommend running at least two passes of memtest86 to look for a memory, cache, or memory bus
>fault.

That might be a problem if the box is already in production and there is no backup (or cold-standby, as there existed in my case).  Is there any way to check fan speeds somewhere in /proc, perhaps?  Also, memtest seems to require taking down the box - is there any way to run such tests without being on-site or shutting down the box (or is that like asking how to run fsck on a mounted partition?)

Cheers,
-Jon

0
 
jlevieCommented:
> That might be a problem if the box is already in production and there is no backup

Yep, that's a problem and then it becomes a question of how badly you want to fix the problem. It just depend on which is more painful. Taking the box down to work on it or living with the reboots.

> is there any way to run such tests without being on-site or shutting down the box

Not that know of.
0
 
wesly_chenCommented:
For CPU fan or hardware issue:
1. You might want to re-seat the memory, CPU heat sink and CPU, if you can.

2. Clean the dust in the box and on the CPU fan, add lubricant on CPU fan.

Those tricks work for me to prolong my hardware so I have pretty time to
get new equipment budget.

Wesly
0
 
Renante EnteraAuthor Commented:
Hello everybody!

As I continue with tracing the root cause of this problem.  I have found out that the cause is LAN card.  Actually, it occurs on two(2) linux servers and both of them have the same models of LAN card which is "Davicom".

With this, I try to change it with Realtek.  And for a week of observation, problem does not occur anymore.

Anyway, thanks for all your responses.


Regards!
eNTRANCE2002 :-)
0
 
wesly_chenCommented:
Glad to hear that you found the root problem and resolved it.

You might want to ask for refound
http://www.experts-exchange.com/Community_Support/

Regards,

Wesly
0
 
Renante EnteraAuthor Commented:
No need for refund ... :-)

Actually, I just reward all participants with points since I gather more ideas about this matter from all of you.

So ...
    Points for jlevie - http://www.experts-exchange.com/Operating_Systems/Linux/Q_21244478.html
    Points for  The--Captain - http://www.experts-exchange.com/Operating_Systems/Linux/Q_21244483.html

Again, thanks for all your help !
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

  • 6
  • 6
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now