Server shutdown

Discussion in 'Installation/Configuration' started by SilentHunter, Jun 3, 2013.

  1. SilentHunter

    SilentHunter New Member

    Hi *,

    I have a little problem, but I don't know if it could be a hardware problem or it is caused by ISPConfig.

    In the last week I had to start my complete Server manually, because the server was completely shutdown. This happened three times now.

    Now I am investigating the problem and found this in the syslog:

    Code:
    Jun  3 04:51:53 zealand pure-ftpd: (?@79.XX.CC.253) [INFO] New connection from 79.XX.CC.253
    Jun  3 04:51:53 zealand pure-ftpd: (?@79.XX.CC.253) [INFO] zibijo.wggselb is now logged in
    Jun  3 04:51:53 zealand pure-ftpd: (zibijo.wggselb@79.XX.CC.253) [INFO] Logout.
    Jun  3 04:52:01 zealand /USR/SBIN/CRON[5856]: (root) CMD (/usr/local/ispconfig/server/server.sh > /dev/null 2>> /var/log/ispconfig/cron.log)
    Jun  3 13:49:24 zealand kernel: imklog 4.6.4, log source = /proc/kmsg started.
    Jun  3 13:49:24 zealand rsyslogd: [origin software="rsyslogd" swVersion="4.6.4" x-pid="1050" x-info="http://www.rsyslog.com"] (re)start
    Jun  3 13:49:24 zealand kernel: [    0.000000] Initializing cgroup subsys cpuset
    Jun  3 13:49:24 zealand kernel: [    0.000000] Initializing cgroup subsys cpu
    Jun  3 13:49:24 zealand kernel: [    0.000000] Linux version 2.6.32-5-amd64 (Debian 2.6.32-48squeeze1) (dannf@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Feb 25 00:26$
    Jun  3 13:49:24 zealand kernel: [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=UUID=5b81c72a-5ac4-4436-96c3-7e5deddc7fb0 ro
    Jun  3 13:49:24 zealand kernel: [    0.000000] KERNEL supported cpus:
    Jun  3 13:49:24 zealand kernel: [    0.000000]   Intel GenuineIntel
    Jun  3 13:49:24 zealand kernel: [    0.000000]   AMD AuthenticAMD
    Jun  3 13:49:24 zealand kernel: [    0.000000]   Centaur CentaurHauls
    
    At 5 am the server was no longer reachable via ping command and in this logfile you can see the that the last entry was:

    Code:
    Jun  3 04:52:01 zealand /USR/SBIN/CRON[5856]: (root) CMD (/usr/local/ispconfig/server/server.sh > /dev/null 2>> /var/log/ispconfig/cron.log)
    Can it be an ISPConfig problem? I am using the latest version v3.0.5.2
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Its unlikely thats this is a ispconfig problem as ispconfig is not able to shutdown a server. The cron line you posted is a cronjob that runs once every minute, so its no indication that you found it in the log near the timeyour problem occurs. There are no ispconfig cronjobs that start just at 5 am.
     
  3. SilentHunter

    SilentHunter New Member

    Do you think that might be a hardware problem?
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Dos it happen regularily alwaysat the same time or at different times or was it just the first time that this happened?
     
  5. SilentHunter

    SilentHunter New Member

    No it is not regular, it happens suddenly and unexpected, without any reasons (no traffic, no logins, nothing). And the technician in the datacenter says, that the server is turned off. It is the third time this is happening.
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    But if the server is turned off by software (e.g. shutdown command) then you should see the shutdown sequence in the log which is not the case here. The log you posted looks more like if someone unplugged the power cable or a hard shutdown trough a ipmi console or a instability in the power supply to me.
     
  7. SilentHunter

    SilentHunter New Member

    Yes, I agree with you. That were also my thoughts.
    Thanks for your opinion. I will confrontate the provider with these arguments...
     
  8. Zippy

    Zippy Member

    I have the same problem and have researched it to no avail. I was told it could be a temperature issue but I have not had any such issues until I moved the server to a new location. Now I am stuck as to what is causing the shutdown. Just because it does not show up in the log file does not mean it is NOT a software problem though correct?

    Thanks
     

Share This Page