Some serious help in apache....

Discussion in 'Apache' started by desiguru, Feb 25, 2007.

0
  1. #1
    Since last few day I have been noticing apache down time every hour and then automatically it goes up online by itself. I have posted my error logs here can someone please take a look at it and help me out here.....


    [Sun Feb 25 20:16:04 2007] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
    [Sun Feb 25 20:16:04 2007] [notice] Apache/1.3.37 (Unix) PHP/4.4.4 FrontPage/5.0.2.2510 mod_ssl/2.8.28 OpenSSL/0.9.7a configured -- resuming normal operations
    [Sun Feb 25 20:16:04 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
    [Sun Feb 25 20:16:04 2007] [notice] Accept mutex: sysvsem (Default: sysvsem)
    [Sun Feb 25 21:15:43 2007] [notice] SIGUSR1 received. Doing graceful restart
    [Sun Feb 25 21:15:44 2007] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
    [Sun Feb 25 21:15:44 2007] [notice] Apache/1.3.37 (Unix) PHP/4.4.4 FrontPage/5.0.2.2510 mod_ssl/2.8.28 OpenSSL/0.9.7a configured -- resuming normal operations
    [Sun Feb 25 21:15:44 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
    [Sun Feb 25 21:15:44 2007] [notice] Accept mutex: sysvsem (Default: sysvsem)
    [Sun Feb 25 21:33:18 2007] [notice] SIGHUP received. Attempting to restart
    [Sun Feb 25 21:33:18 2007] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
    [Sun Feb 25 21:33:18 2007] [notice] Apache/1.3.37 (Unix) PHP/4.4.4 FrontPage/5.0.2.2510 mod_ssl/2.8.28 OpenSSL/0.9.7a configured -- resuming normal operations
    [Sun Feb 25 21:33:18 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
    [Sun Feb 25 21:33:18 2007] [notice] Accept mutex: sysvsem (Default: sysvsem)
    [Sun Feb 25 21:40:05 2007] [notice] SIGHUP received. Attempting to restart
    [Sun Feb 25 21:40:05 2007] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
    [Sun Feb 25 21:40:06 2007] [notice] Apache/1.3.37 (Unix) PHP/4.4.4 FrontPage/5.0.2.2510 mod_ssl/2.8.28 OpenSSL/0.9.7a configured -- resuming normal operations
    [Sun Feb 25 21:40:06 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
    [Sun Feb 25 21:40:06 2007] [notice] Accept mutex: sysvsem (Default: sysvsem)
    [Sun Feb 25 22:16:15 2007] [notice] SIGUSR1 received. Doing graceful restart
    [Sun Feb 25 22:16:16 2007] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
    [Sun Feb 25 22:16:16 2007] [notice] Apache/1.3.37 (Unix) PHP/4.4.4 FrontPage/5.0.2.2510 mod_ssl/2.8.28 OpenSSL/0.9.7a configured -- resuming normal operations
    [Sun Feb 25 22:16:16 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
    [Sun Feb 25 22:16:16 2007] [notice] Accept mutex: sysvsem (Default: sysvsem)
    [Sun Feb 25 23:15:22 2007] [notice] SIGUSR1 received. Doing graceful restart
    [Sun Feb 25 23:15:22 2007] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
    [Sun Feb 25 23:15:23 2007] [notice] Apache/1.3.37 (Unix) PHP/4.4.4 FrontPage/5.0.2.2510 mod_ssl/2.8.28 OpenSSL/0.9.7a configured -- resuming normal operations
    [Sun Feb 25 23:15:23 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
    [Sun Feb 25 23:15:23 2007] [notice] Accept mutex: sysvsem (Default: sysvsem)
    [Mon Feb 26 00:16:00 2007] [notice] SIGUSR1 received. Doing graceful restart
    [Mon Feb 26 00:16:01 2007] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
    [Mon Feb 26 00:16:01 2007] [notice] Apache/1.3.37 (Unix) PHP/4.4.4 FrontPage/5.0.2.2510 mod_ssl/2.8.28 OpenSSL/0.9.7a configured -- resuming normal operations
    [Mon Feb 26 00:16:01 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
    [Mon Feb 26 00:16:01 2007] [notice] Accept mutex: sysvsem (Default: sysvsem)
    [Mon Feb 26 01:16:12 2007] [notice] SIGUSR1 received. Doing graceful restart
    [Mon Feb 26 01:16:12 2007] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
    [Mon Feb 26 01:16:12 2007] [notice] Apache/1.3.37 (Unix) PHP/4.4.4 FrontPage/5.0.2.2510 mod_ssl/2.8.28 OpenSSL/0.9.7a configured -- resuming normal operations
    [Mon Feb 26 01:16:12 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
    [Mon Feb 26 01:16:12 2007] [notice] Accept mutex: sysvsem (Default: sysvsem)
    [Mon Feb 26 01:28:06 2007] [notice] SIGHUP received. Attempting to restart
    [Mon Feb 26 01:28:06 2007] [alert] httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
    [Mon Feb 26 01:28:07 2007] [notice] Apache/1.3.37 (Unix) PHP/4.4.4 FrontPage/5.0.2.2510 mod_ssl/2.8.28 OpenSSL/0.9.7a configured -- resuming normal operations
    [Mon Feb 26 01:28:07 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
    [Mon Feb 26 01:28:07 2007] [notice] Accept mutex: sysvsem (Default: sysvsem)
     
    desiguru, Feb 25, 2007 IP
  2. tespio

    tespio Peon

    Messages:
    16
    Likes Received:
    2
    Best Answers:
    0
    Trophy Points:
    0
    #2
    I think you have logrotate (tool to rotate the logs so you dont get a huge big log file) added to your crontab jobs that is doing this. This is most common with some webhosting automation panels like cPanel etc. I cant see any important info except the alert about not being able to determine server's fully qualified domain name which isnt itself a big deal. However you mgith want to do that too.

    Hope this helps you
     
    tespio, Feb 26, 2007 IP