Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: hacktorious on January 07, 2004, 05:55:13 PM

Title: server goes down
Post by: hacktorious on January 07, 2004, 05:55:13 PM

I am having an issue with version 6 of SME.  The server runs fine for several days then suddenly I can no longer remotely connect or do anything.  
The server consol is also blank, where it would normally have a login screen.  Has anyone seen this before?  Does anyone have any suggestions?

Title: Re: server goes down
Post by: PeterG on January 07, 2004, 06:36:51 PM

What do the logs say?

hint: they are in /var/log

PeterG.

Title: Re: server goes down
Post by: hacktorious on January 07, 2004, 07:04:28 PM

This is all I could find that looked out of place:

httpd/error_log
[Tue Jan  6 12:03:55 2004] [notice] child pid 1559 exit signal Segmentation fault (11)

httpd/admin_error_log:
Use of uninitialized value in concatenation (.) or string at /etc/e-smith/web/panels/manager/cgi-bin/viewlogfiles line 301.

Title: Segmentation fault (was Re: server goes down)
Post by: George on January 08, 2004, 02:01:14 AM

hacktorious wrote:
 
> httpd/error_log
> [Tue Jan  6 12:03:55 2004] [notice] child pid 1559 exit
> signal Segmentation fault (11)

Usually means a hardware problem.

Title: Re: Segmentation fault (was Re: server goes down)
Post by: delosbomos on January 08, 2004, 02:35:28 PM

I had the same problem updating from 5.6 to 6.0.
Suddenly the server went down and I could not connect, not remotely
and not even local. The computer didn't go off.

What helped for me was to disable the power savings in the bios of the server.
For some reasion the server in 6.0 didn't wake up on LAN activity or in 5.6 the server
never went into power-saving state.

Maybe this helps for you to.

Title: Re: Segmentation fault (was Re: server goes down)
Post by: hacktorious on January 11, 2004, 05:06:58 PM

I have disabled the power and plug-n-play options in the bios and the problem still occurs.  Here is the latest from the messages log file.

Jan 10 18:34:06 apollo kernel:  <1>Unable to handle kernel paging request at virtual address 10fd7008
Jan 10 18:34:06 apollo kernel:  printing eip:
Jan 10 18:34:06 apollo kernel: c0115533
Jan 10 18:34:06 apollo kernel: *pde = 00000000
Jan 10 18:34:06 apollo kernel: Oops: 0000
Jan 10 18:34:06 apollo kernel: appletalk 8139too mii ide-scsi scsi_mod ide-cd cdrom hid input printer usb-uhci usbcore ext3 jbd  
Jan 10 18:34:06 apollo kernel: CPU:    0
Jan 10 18:34:06 apollo kernel: EIP:    0010:[__wake_up+51/176]    Not tainted
Jan 10 18:34:06 apollo kernel: EIP:    0010:[]    Not tainted
Jan 10 18:34:06 apollo kernel: EFLAGS: 00010083
Jan 10 18:34:06 apollo kernel:
Jan 10 18:34:06 apollo kernel: EIP is at __wake_up [kernel] 0x33 (2.4.20-18.7)
Jan 10 18:34:06 apollo kernel: eax: 56d4a408   ebx: c381ffff   ecx: 10fd7008   edx: 56d4a408
Jan 10 18:34:06 apollo kernel: esi: 00000046   edi: 00000001   ebp: c09cde2c   esp: c09cde14
Jan 10 18:34:06 apollo kernel: ds: 0018   es: 0018   ss: 0018
Jan 10 18:34:06 apollo kernel: Process lpq (pid: 5598, stackpage=c09cd000)
Jan 10 18:34:06 apollo kernel: Stack: 00000282 00000001 d2887370 d3be3ac0 c278f5c0 7fffffff c09cde60 c01ce322
Jan 10 18:34:06 apollo kernel:        7fffffff c09cde60 c02108dc c09cdf00 d3be3ac0 c0210ae6 d3be3ac0 00000000
Jan 10 18:34:06 apollo kernel:        00000011 d3db1080 c5382ac0 ffffff91 c0108904 c09cde70 00000002 000001da
Jan 10 18:34:06 apollo kernel: Call Trace:   [sock_def_readable+34/80] sock_def_readable [kernel] 0x22 (0xc09cde30))
Jan 10 18:34:06 apollo kernel: Call Trace:   [] sock_def_readable [kernel] 0x22 (0xc09cde30))
Jan 10 18:34:06 apollo kernel: [unix_stream_connect+236/880] unix_stream_connect [kernel] 0xec (0xc09cde3c))
Jan 10 18:34:06 apollo kernel: [] unix_stream_connect [kernel] 0xec (0xc09cde3c))
Jan 10 18:34:06 apollo kernel: [unix_stream_connect+758/880] unix_stream_connect [kernel] 0x2f6 (0xc09cde48))
Jan 10 18:34:06 apollo kernel: [] unix_stream_connect [kernel] 0x2f6 (0xc09cde48))
Jan 10 18:34:06 apollo kernel: [error_code+52/60] error_code [kernel] 0x34 (0xc09cde64))
Jan 10 18:34:06 apollo kernel: [] error_code [kernel] 0x34 (0xc09cde64))
Jan 10 18:34:06 apollo kernel: [file_read_actor+96/208] file_read_actor [kernel] 0x60 (0xc09cde98))
Jan 10 18:34:06 apollo kernel: [] file_read_actor [kernel] 0x60 (0xc09cde98))
Jan 10 18:34:06 apollo kernel: [vsnprintf+656/992] vsnprintf [kernel] 0x290 (0xc09cdeac))
Jan 10 18:34:06 apollo kernel: [] vsnprintf [kernel] 0x290 (0xc09cdeac))
Jan 10 18:34:06 apollo kernel: [sys_connect+83/112] sys_connect [kernel] 0x53 (0xc09cdee8))
Jan 10 18:34:06 apollo kernel: [] sys_connect [kernel] 0x53 (0xc09cdee8))
Jan 10 18:34:06 apollo kernel: [do_setitimer+162/240] do_setitimer [kernel] 0xa2 (0xc09cdf78))
Jan 10 18:34:06 apollo kernel: [] do_setitimer [kernel] 0xa2 (0xc09cdf78))
Jan 10 18:34:06 apollo kernel: [sys_socketcall+139/464] sys_socketcall [kernel] 0x8b (0xc09cdf8c))
Jan 10 18:34:06 apollo kernel: [] sys_socketcall [kernel] 0x8b (0xc09cdf8c))
Jan 10 18:34:06 apollo kernel: [system_call+51/56] system_call [kernel] 0x33 (0xc09cdfc0))
Jan 10 18:34:06 apollo kernel: [] system_call [kernel] 0x33 (0xc09cdfc0))
Jan 10 18:34:06 apollo kernel:
Jan 10 18:34:06 apollo kernel:
Jan 10 18:34:06 apollo kernel: Code: 8b 01 85 45 ec 74 4f 31 c0 9c 5e fa c7 01 00 00 00 00 8b 51

Title: Re: Segmentation fault (was Re: server goes down)
Post by: hacktorious on January 11, 2004, 08:57:57 PM

I think it is due to the printer I have installed, but I am not quite sure why.