ISPConfig Is Completely Breaking Down

Discussion in 'General' started by iratik, Jun 29, 2007.

  1. iratik

    iratik New Member

    First ISPConfig completely corrupts my /etc/passwd file (I'm quite sure that this was a result of ISPconfig as it happened immediately after updating the password on an one of 12 email accounts on one of 15 domains) the /etc/passwd file then only contained entries for one domain - and all system accounts including root were lost and replaced by accounts from web2.

    I cannot restart my system because I'm quite confident that i'll never be able to get to root again , i've got root terminals up and i can't close them because i'm still getting this error after attempting to scavange together the original /etc/passwd configuration by updating a password of one email of each domain. Now email is working, but i'm still getting
    sudo: pam_authenticate: Authentication service cannot retrieve authentication info.

    When i reset all those passwords - the ability to use ProxyPass and ProxyPassReverse in the additional directives section is commented out.. And worst of all - i depend heavily on these directives (to forward requests to mongrel instances to support rubyonrails on ispconfig) and must continuously manually edit the vhosts configuration to keep this directives in place and keep ispconfig from overwriting the file without these directives.

    Please Help Me, We've been using ISPConfig in production for over a year and a half now .. Perhaps the newest version does not have these restrictions on extra apache directives.. I need help bad though.........
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    There is no such restriction in none of the ISPConfig versions. ISPConfig only comments out directives that would cause apache to fail when it is restarted.

    To your password problem, I guess the structure of your /etc/passwd or /etc/shadow file was corrupted bfeore you edited the user. Please check your passwd and group file with the commands:

    pwck
    grpck
     
  3. iratik

    iratik New Member

    Here is what's happening in the Apache directives (Optional) section

    # ProxyPass / http://localhost:3000/ # NOT SUPPORTED! # NOT SUPPORTED!
    # ProxyPassReverse / http://localhost:3000/ # NOT SUPPORTED! # NOT SUPPORTED!
     
  4. iratik

    iratik New Member

    pwck, grpck

    [email protected]:/etc/apache2/vhosts# pwck
    user lp: directory /var/spool/lpd does not exist
    user news: directory /var/spool/news does not exist
    user uucp: directory /var/spool/uucp does not exist
    user list: directory /var/list does not exist
    user irc: directory /var/run/ircd does not exist
    user gnats: directory /var/lib/gnats does not exist
    user nobody: directory /nonexistent does not exist
    user dhcp: directory /nonexistent does not exist
    user syslog: directory /home/syslog does not exist
    user klog: directory /home/klog does not exist
    user admin: directory /home/admin does not exist
    user faxmaster: directory /var/spool/hylafax does not exist
    user clamav: no group 114
    user clamav: directory /var/lib/clamav does not exist
    pwck: no changes


    grpck
    nothing
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    Thats not a restriction. I explained it above.
     
  6. iratik

    iratik New Member

    But it doesn't cause apache2 to crash on restart! When i add the directives manually to the vhost config - and restart apache2... everything works fine - so why is ispconfig commenting them out still?
     
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    Because apache reports that it will not be able to start in this configuration when it is queried with the "httpd -t" command.
     
  8. iratik

    iratik New Member

    output of httpd -t

    [email protected]:/etc/apache2/vhosts# cat Vhosts_ispconfig.conf | grep ProxyPass
    ProxyPass / http://localhost:3000/
    ProxyPassReverse / http://localhost:3000/
    ProxyPass / http://localhost:266/
    ProxyPassReverse / http://localhost:266/
    ProxyPass / http://localhost:2656/
    ProxyPassReverse / http://localhost:2656/
    [email protected]:/etc/apache2/vhosts# httpd -t
    [Fri Jun 29 12:08:29 2007] [warn] module cache_module is already loaded, skipping
    httpd: Could not determine the server's fully qualified domain name, using 127.0.0.1 for ServerName
    Syntax OK
    [email protected]:/etc/apache2/vhosts# cat Vhosts_ispconfig.conf | grep ProxyPass
    ProxyPass / http://localhost:3000/
    ProxyPassReverse / http://localhost:3000/
    ProxyPass / http://localhost:266/
    ProxyPassReverse / http://localhost:266/
    ProxyPass / http://localhost:2656/
    ProxyPassReverse / http://localhost:2656/
    [email protected]:/etc/apache2/vhosts#
     
  9. iratik

    iratik New Member

    Is there a way to non-destructively update ispconfig to the newest version

    Is there a way to non-destructively update ispconfig to the newest version?
     
  10. till

    till Super Moderator Staff Member ISPConfig Developer

    Please fix this warning.

    The ispconfig update is non distructive. You can not avid to replace the files of a application with nwer versions when you want to update it.
     

Share This Page