The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Dedicated Server Issues

Discussion in 'General Discussion' started by netrix37, Jul 16, 2006.

  1. netrix37

    netrix37 Member

    Joined:
    Jul 13, 2006
    Messages:
    14
    Likes Received:
    0
    Trophy Points:
    1
    Let me start by saying I'm pretty close to a total CPanel/WHM newbie and this is also my first time with a dedicated server. With that said about a week ago I purchased a dedicated server through serverbeach and when I first logged in it appeared that they hadn't properly installed the license (as I got that error about it checking with cpanel's servers every 30 seconds). I submited a ticket and that went away. Then probably sometime the next day I noticed the machine itself was rebooting with the following error being emailed to me.

    cpsrvd failed @ Thu Jul 13 18:04:10 2006. A restart was attempted automagicly.

    After a little digging I found this in /var/messages:

    Jul 15 12:32:08 server1 kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
    Jul 15 12:32:08 server1 kernel: printing eip:
    Jul 15 12:32:08 server1 kernel: c030a3a1
    Jul 15 12:32:08 server1 kernel: *pde = 3a862067
    Jul 15 12:32:08 server1 kernel: Oops: 0002 [#1]
    Jul 15 12:32:08 server1 kernel: Modules linked in: loop iptable_filter ip_tables md5 ipv6 sunrpc dm_mirror dm_mod button battery ac ohci_hcd ehci_hcd forcedet
    h tg3 floppy ext3 jbd sata_nv libata sd_mod scsi_mod
    Jul 15 12:32:08 server1 kernel: CPU: 0
    Jul 15 12:32:08 server1 kernel: EIP: 0060:[<c030a3a1>] Not tainted VLI
    Jul 15 12:32:08 server1 kernel: EFLAGS: 00210212 (2.6.9-34.EL)
    Jul 15 12:32:08 server1 kernel: EIP is at unix_copy_addr+0x2e/0x3e
    Jul 15 12:32:08 server1 kernel: eax: 0000001c ebx: e3a8f2f4 ecx: 00000007 edx: e3a8f040
    Jul 15 12:32:08 server1 kernel: esi: f4bf3dcc edi: 00000000 ebp: 00000004 esp: f633be18
    Jul 15 12:32:08 server1 kernel: ds: 007b es: 007b ss: 0068
    Jul 15 12:32:08 server1 kernel: Process httpd (pid: 21963, threadinfo=f633b000 task=f630f3a0)
    Jul 15 12:32:08 server1 kernel: Stack: e3a8f280 e42a1940 c030a855 00000001 7fffffff fffffff5 00000001 00000000
    Jul 15 12:32:08 server1 kernel: 80000000 f633be8c f633beac f6294640 0000098c 00000065 00000065 00000000
    Jul 15 12:32:08 server1 kernel: 00000000 00000000 00000000 00000001 c03865c0 00000000 f633bef8 f633beac
    Jul 15 12:32:08 server1 kernel: Call Trace:
    Jul 15 12:32:08 server1 kernel: [<c030a855>] unix_stream_recvmsg+0x215/0x398
    Jul 15 12:32:08 server1 kernel: [<c02ac415>] sock_aio_read+0x10d/0x11b
    Jul 15 12:32:08 server1 kernel: [<c0148c5e>] __generic_file_aio_read+0x160/0x17a
    Jul 15 12:32:08 server1 kernel: [<c0168a6a>] do_sync_read+0x97/0xc9
    Jul 15 12:32:08 server1 kernel: [<c011e867>] autoremove_wake_function+0x0/0x2d
    Jul 15 12:32:08 server1 kernel: [<c0168b62>] vfs_read+0xc6/0xe2
    Jul 15 12:32:08 server1 kernel: [<c0168d65>] sys_read+0x3c/0x62
    Jul 15 12:32:08 server1 kernel: [<c0311443>] syscall_call+0x7/0xb
    Jul 15 12:32:08 server1 kernel: Code: 56 c7 40 04 00 00 00 00 8b 82 cc 01 00 00 85 c0 74 26 8b 40 04 8b 39 89 41 04 8b 82 cc 01 00 00 8d 70 0c 8b 40 04 89 c1
    c1 e9 02 <f3> a5 a8 02 74 02 66 a5 a8 01 74 01 a4 5e 5f c3 55 89 cd 57 56
    Jul 15 12:32:08 server1 kernel: <0>Fatal exception: panic in 5 seconds
    Jul 15 12:38:33 server1 syslogd 1.4.1: restart.

    So I went ahead and again submitted a ticket to serverbeach's support staff. Here is the response I got.

    ---
    Sorry for the confusion, we went ahead and replaced all of your servers
    hardware with the exception of your harddrive to eliminate any possible
    hardware issue. Please let us know if you have any more issues.

    If you have any questions or concerns, please let us know. Thank you for
    choosing ServerBeach.

    Best Regards,

    ServerBeach Support
    A Peer 1 Company
    ---

    My question is does this sound kinda fishy to anyone else? Ever since they did whatever it is they did the machine has been up so I'm not neccessarily unhappy just would like to get someone elses opinion on the matter. Thanks in advance!
     
  2. nxds

    nxds Well-Known Member

    Joined:
    Jan 6, 2006
    Messages:
    53
    Likes Received:
    0
    Trophy Points:
    6
    Looks like the kernel paniced which is what happens when an unrecoverable error occurs. It could well have been due a hardware problem like bad memory or a dodgy nic so the support guys have done the right thing.
     
Loading...

Share This Page