Problem to connet after installation

Discussion in 'Installation/Configuration' started by mklomp, May 26, 2016.

  1. mklomp

    mklomp New Member

    Hello,
    I just installed ispconfig on a new installed Debian 8 machine using this tutorial. After the installation I wasn't able to connect to the webinterface listening on port 8080. So I tried to restart my Apache2 and I encountered this Problem:
    Code:
    [email protected]:/# systemctl status apache2.service -l
    ● apache2.service - LSB: Apache2 web server
       Loaded: loaded (/etc/init.d/apache2)
       Active: failed (Result: exit-code) since Thu 2016-05-26 16:38:32 EDT; 48s ago
      Process: 27477 ExecStart=/etc/init.d/apache2 start (code=exited, status=1/FAILURE)
    
    May 26 16:38:32 Michel-SRV systemd[1]: Starting LSB: Apache2 web server...
    May 26 16:38:32 Michel-SRV apache2[27477]: Starting web server: apache2/bin/echo: error while loading shared libraries: libc.so.6: cannot open shared object file: Cannot allocate memory
    May 26 16:38:32 Michel-SRV apache2[27477]: The apache2 configtest failed. .../bin/echo: error while loading shared libraries: libc.so.6: cannot open shared object file: Cannot allocate memory
    May 26 16:38:32 Michel-SRV apache2[27477]: Output of config test was:
    May 26 16:38:32 Michel-SRV apache2[27477]: cat: error while loading shared libraries: libc.so.6: cannot open shared object file: Cannot allocate memory
    May 26 16:38:32 Michel-SRV apache2[27477]: rm: error while loading shared libraries: libc.so.6: cannot open shared object file: Cannot allocate memory
    May 26 16:38:32 Michel-SRV systemd[1]: apache2.service: control process exited, code=exited status=1
    May 26 16:38:32 Michel-SRV systemd[1]: Failed to start LSB: Apache2 web server.
    May 26 16:38:32 Michel-SRV systemd[1]: Unit apache2.service entered failed state.
    I do not have any idea on how to fix the Problem.
    Thanks for your help,
    Michel K
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Seems as if your server has not enough RAM. Hos much ram do you have?
     
  3. mklomp

    mklomp New Member

    2Gb
    Should be enough.
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Thats hould be enough, but apache does not start as it ahs not enough ram. Try to restart your server / vm.
     
  5. mklomp

    mklomp New Member

    Hello,
    I just restarted to VM, but the Problem is still the same.

    I just recognized, that when I try to install something using apt-get install I'm getting also an error.
    Code:
    Job for amavis.service failed. See 'systemctl status amavis.service' and 'journalctl -xn' for details.
    invoke-rc.d: initscript amavis, action "start" failed.
    
    Code:
    [email protected]:~# systemctl status amavis.service
    ● amavis.service - LSB: Starts amavisd-new mailfilter
       Loaded: loaded (/etc/init.d/amavis)
       Active: failed (Result: exit-code) since Fri 2016-05-27 07:42:31 EDT; 39s ago
      Process: 2814 ExecStart=/etc/init.d/amavis start (code=exited, status=1/FAILURE)
    
    May 27 07:42:31 Michel-SRV amavis[2814]: Starting amavisd: head: cannot open '/etc/mailname' for reading: No such file or directory
    May 27 07:42:31 Michel-SRV amavis[2814]: The value of variable $myhostname is "Michel-SRV", but should have been
    May 27 07:42:31 Michel-SRV amavis[2814]: a fully qualified domain name; perhaps uname(3) did not provide such.
    May 27 07:42:31 Michel-SRV amavis[2814]: You must explicitly assign a FQDN of this host to variable $myhostname
    May 27 07:42:31 Michel-SRV amavis[2814]: in /etc/amavis/conf.d/05-node_id, or fix what uname(3) provides as a host's
    May 27 07:42:31 Michel-SRV amavis[2814]: network name!
    May 27 07:42:31 Michel-SRV amavis[2814]: (failed).
    May 27 07:42:31 Michel-SRV systemd[1]: amavis.service: control process exited, code=exited status=1
    May 27 07:42:31 Michel-SRV systemd[1]: Failed to start LSB: Starts amavisd-new mailfilter.
    May 27 07:42:31 Michel-SRV systemd[1]: Unit amavis.service entered failed state.
    
    I also have already completly reinstalled the VM and reinstalled ispconfig, without any change.
    Michel K.
     

    Attached Files:

  6. mklomp

    mklomp New Member

    Ok, I just tried to install on my mäin Server and do not had any problems.
    Thanks anyway
     
  7. florian030

    florian030 ISPConfig Developer ISPConfig Developer

    Amavis did not start because your server has no fqdn. Open /etc/amavis/conf.d/05-node_id and set the hostname - or correct your setup.
     
  8. Gwyneth Llewelyn

    Gwyneth Llewelyn New Member

    I haven't used Apache in a while (I'm a nginx convert :) ) but I seem to remember that Apache wouldn't start without a FQDN, either.
     

Share This Page