Server is missing from ISPConfig 3

Discussion in 'Installation/Configuration' started by DinethH, Jul 21, 2014.

  1. DinethH

    DinethH New Member

    Recently I added firewall rules using ISPConfig->System->Firewall. And they worked fine, it seems.

    Then I rebooted the server and now the "server" is missing from ISPConfig, which means I cannot add new sites/databases etc. Then I removed the firewall instructions and it did not make any changes.

    I used the template given by the dedicated server provider to install Debian 7 with ISPConfig 3.0.5.4p1. So I did not configure the bindings or anything manually.

    Any way to solve this issue without having to re-install ISPConfig?
     
  2. srijan

    srijan New Member HowtoForge Supporter

    Which webserver you are using?

    Please check webserver service is running status
     
  3. DinethH

    DinethH New Member

    Apache. Yes, it is running.
     
  4. srijan

    srijan New Member HowtoForge Supporter

    Do you find any errors in error.log for apache
     
  5. DinethH

    DinethH New Member

    I do see a bunch of "[client: xxx.xxx.xxx] request failed: error reading the headers" statements.
     
  6. srijan

    srijan New Member HowtoForge Supporter

    Please paste your error.log for apache
     
  7. DinethH

    DinethH New Member

    Code:
    [Sun Jul 20 06:25:14 2014] [notice] Digest: generating secret for digest authentication ...
    [Sun Jul 20 06:25:14 2014] [notice] Digest: done
    [Sun Jul 20 06:25:14 2014] [error] python_init: Python version mismatch, expected '2.7.2+', found '2.7.3'.
    [Sun Jul 20 06:25:14 2014] [error] python_init: Python executable found '/usr/bin/python'.
    [Sun Jul 20 06:25:14 2014] [error] python_init: Python path being used '/usr/lib/python2.7/:/usr/lib/python2.7/plat-linux2:/usr/lib/python2.7/lib-tk:/usr/lib/python2.7/lib-old:/usr/lib/python2.7/lib-dynload'.
    [Sun Jul 20 06:25:14 2014] [notice] mod_python: Creating 8 session mutexes based on 150 max processes and 0 max threads.
    [Sun Jul 20 06:25:14 2014] [notice] mod_python: using mutex_directory /tmp
    [Sun Jul 20 06:25:14 2014] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
    [Sun Jul 20 06:25:14 2014] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
    [Sun Jul 20 06:25:14 2014] [notice] Apache/2.2.22 (Debian) DAV/2 mod_fcgid/2.3.6 PHP/5.4.4-14+deb7u12 mod_python/3.3.1 Python/2.7.3 mod_ruby/1.2.6 Ruby/1.8.7(2012-02-08) mod_scgi/1.13 mod_ssl/2.2.22 OpenSSL/1.0.1$
    [Sun Jul 20 06:25:14 2014] [warn] long lost child came home! (pid 5832)
    [Sun Jul 20 06:29:48 2014] [error] [client 178.131.30.199] request failed: error reading the headers, referer: http://northamericanproxy.com/browse.php?u=GKBYKSExIhtOXFm6kWeg7zqt1q8yojiIw8Kno614xW2M0ox%2FPTJIboA0$
    [Sun Jul 20 06:34:05 2014] [error] [client 178.131.30.199] request failed: error reading the headers, referer: http://northamericanproxy.com/browse.php?u=GKBYLCExJgVCWFfn0WC1rjqhw6Ap5DCMmo6ku%2BE%2B%2ByzTnJYsNi9V$
    [Sun Jul 20 06:58:39 2014] [error] [client 130.149.221.188] Invalid method in request quit
    [Sun Jul 20 06:59:04 2014] [error] [client 178.131.30.199] request failed: error reading the headers, referer: http://northamericanproxy.com/browse.php?u=GKBYPCM7NQUFT179mnq9si7i07FuqBffka%2Fy84pAvwGD2KEpdhUJcpBe$
    [Sun Jul 20 07:09:40 2014] [error] [client 39.44.202.195] request failed: error reading the headers
    [Sun Jul 20 07:11:48 2014] [error] [client 87.255.57.169] Invalid URI in request POST P/1.1
    [Sun Jul 20 07:12:09 2014] [error] [client 39.44.202.195] request failed: error reading the headers
    [Sun Jul 20 07:16:53 2014] [error] [client 39.44.202.195] request failed: error reading the headers
    [Sun Jul 20 07:17:54 2014] [error] [client 39.44.202.195] request failed: error reading the headers
    [Sun Jul 20 07:22:33 2014] [error] [client 39.44.202.195] request failed: error reading the headers
    [Sun Jul 20 07:34:59 2014] [warn] mod_fcgid: process 23984 graceful kill fail, sending SIGKILL
    [Sun Jul 20 07:56:12 2014] [error] [client 151.240.76.0] request failed: error reading the headers
    [Sun Jul 20 07:56:12 2014] [error] [client 151.240.76.0] request failed: error reading the headers
    [Sun Jul 20 07:56:13 2014] [error] [client 151.240.76.0] request failed: error reading the headers
    [Sun Jul 20 07:56:13 2014] [error] [client 151.240.76.0] request failed: error reading the headers
    [Sun Jul 20 07:56:13 2014] [error] [client 151.240.76.0] request failed: error reading the headers
    [Sun Jul 20 07:57:17 2014] [error] [client 151.240.76.0] request failed: error reading the headers
    [Sun Jul 20 07:57:46 2014] [error] [client 151.240.76.0] request failed: error reading the headers
    [Sun Jul 20 07:58:56 2014] [error] [client 151.240.76.0] request failed: error reading the headers
    [Sun Jul 20 08:48:23 2014] [error] [client 213.140.59.147] request failed: error reading the headers
    [Sun Jul 20 08:48:29 2014] [error] [client 213.140.59.147] request failed: error reading the headers
    [Sun Jul 20 08:48:30 2014] [error] [client 213.140.59.147] request failed: error reading the headers
    [Sun Jul 20 08:48:30 2014] [error] [client 213.140.59.147] request failed: error reading the headers
    [Sun Jul 20 08:48:38 2014] [error] [client 213.140.59.147] request failed: error reading the headers
    [Sun Jul 20 08:48:38 2014] [error] [client 213.140.59.147] request failed: error reading the headers
    [Sun Jul 20 08:48:39 2014] [error] [client 213.140.59.147] request failed: error reading the headers
    [Sun Jul 20 08:48:47 2014] [error] [client 213.140.59.147] request failed: error reading the headers
    [Sun Jul 20 08:48:48 2014] [error] [client 213.140.59.147] request failed: error reading the headers
    [Sun Jul 20 08:48:48 2014] [error] [client 213.140.59.147] request failed: error reading the headers
    [Sun Jul 20 08:48:48 2014] [error] [client 213.140.59.147] request failed: error reading the headers
    [Sun Jul 20 08:48:49 2014] [error] [client 213.140.59.147] request failed: error reading the headers
    
     
  8. DinethH

    DinethH New Member

    FYI: Existing websites work fine.
     
    Last edited: Jul 21, 2014
  9. till

    till Super Moderator Staff Member ISPConfig Developer

    You will have to restore the missing database record from a mysql backup of the ispconfig database. the database table is named "server". Do you have a recent backup of all mysql databases of your server? If not, have a look at /var/backup to see if there is any backup folder with name starting with "ispconfig" there.
     
  10. DinethH

    DinethH New Member

    That seemed to do the trick.. Thanks.
     

Share This Page