Unable to start httpd suddenly. /var/log/ispconfig corrupt. suexec failure.

Discussion in 'Installation/Configuration' started by sprion, Mar 15, 2013.

  1. sprion

    sprion New Member

    After the recent upgrade... CentOS release 5.8 (Final) 64 bit

    My sites have been running on Ispconfig 3 for a while now, but suddenly the sites no longer respond.

    On restart, httpd fails to start.

    By disabling the 'ErrorLog' apache directives in each site's .vhost file,
    allowed the site to run for a moment before they stopped responding.

    Tracing that, I found the ispconfig log folder at /var/log/ispconfig had become inaccessible/invalid.


    server log:
    =====
    return code: 1
    suexec failure: could not open log file
    =====

    My service provider has not been able to fix the problems, does anyone have any ideas? Thanks!
     
    Last edited: Mar 15, 2013
  2. sprion

    sprion New Member

    *bump* Require help to get my sites back online..
     
  3. falko

    falko Super Moderator

    Have you tried to disable SuExec?
     
  4. sprion

    sprion New Member

    Thanks!

    I did this:

    1. locate where is suexec by running the following:

    whereis suexec

    return
    suexec: /usr/sbin/suexec /usr/share/man/man8/suexec.8.gz

    2. rename the suexec to suexec_old
    mv /usr/sbin/suexec /usr/sbin/suexec_old

    3. restart httpd
    service httpd restart


    and everything works.. BUT for a while... then websites become unresponsive again after a few minutes/hits~
    what else would I have to do? What could be the perfect/proper fix?

    Anyway, /var/log/ispconfig became inaccessible again, so i deleted it and created a new '/var/log/ispconfig' folder,
    then downloaded latest Ispconfig, and ran 'php -q update.php'

    Everything is working now.. but suexec remains disabled.

    Please advise! thanks~~
     
    Last edited: Mar 16, 2013
  5. till

    till Super Moderator

    ensure that suexec is present and that the log file is owned by user ispconfig.
     
  6. sprion

    sprion New Member

    Hello till,

    what do you mean by ensuring it is present? I had it disabled.

    Code:
    [root@spark ~]# service httpd restart
    Stopping httpd:                                            [  OK  ]
    Starting httpd: Warning: SuexecUserGroup directive requires SUEXEC wrapper.
    Warning: SuexecUserGroup directive requires SUEXEC wrapper.
    Warning: SuexecUserGroup directive requires SUEXEC wrapper.
    Warning: SuexecUserGroup directive requires SUEXEC wrapper.
    Warning: SuexecUserGroup directive requires SUEXEC wrapper.
    Warning: SuexecUserGroup directive requires SUEXEC wrapper.
                                                               [  OK  ]

    Also, how would I go about making ispconfig own the log file?
    thank you.
     
    Last edited: Mar 20, 2013
  7. sprion

    sprion New Member

    My sites died again. AND /var/log/ispconfig became invalid and inaccessible again.

    I had to delete and recreate an empty folder.
     
  8. SamTzu

    SamTzu HowtoForge Supporter

    Clearly something is generating a lot of error messages (maybe file permissions/user rights?)
    You should probably try to fix suexec.
    It seems that is causing the errors.
     
    Last edited: Mar 20, 2013

Share This Page