Brand new Debian 9 install using auto installer script taking a huge amount of time to get to login

Discussion in 'Installation/Configuration' started by adamjedgar, Jun 24, 2019.

  1. adamjedgar

    adamjedgar Member

    I have just run a brand new debian 9 ISPConfig auto installer
    IT is taking a huge amount of time to get to login screen, and then comes back with a wrong password after another huge amount of time when i try to login.

    i have other servers that are with the same provider that i can run alongside this in my browser and they login fast.

    Something seriously wrong with this automated install...any ideas? (i have ssh access)

    >> Initial configuration

    Operating System: Debian 9.0 (Stretch) or compatible

    Following will be a few questions for primary configuration so be careful.
    Default values are in [brackets] and can be accepted with <ENTER>.
    Tap in "quit" (without the quotes) to stop the installer.
    Configuring Postgrey
    Configuring Postfix
    Generating a RSA private key
    .......................................................++++
    ......................................................................................++++
    writing new private key to 'smtpd.key'
    -----
    Configuring Dovecot
    Configuring Spamassassin
    Configuring Amavisd
    Configuring Getmail
    Configuring Jailkit
    Configuring Pureftpd
    Configuring BIND
    Configuring Apache
    Configuring vlogger
    Configuring Ubuntu Firewall
    Configuring Fail2ban
    Configuring Apps vhost
    Installing ISPConfig




    Generating RSA private key, 4096 bit long modulus
    ....++++
    .............++++
    e is 65537 (0x010001)
    writing RSA key


    Configuring DBServer
    Installing ISPConfig crontab
    Installing ISPConfig crontab
    no crontab for root
    no crontab for getmail
    Detect IP addresses
    Restarting services ...
    Job for amavis.service failed because the control process exited with error code.
    See "systemctl status amavis.service" and "journalctl -xe" for details.
    Installation completed.
    Restarting Apache... Restarting apache2 (via systemctl): apache2.service.
    [DONE]

    Restarting Amavisd... [DONE]

    ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")

    Well done! ISPConfig installed and configured correctly :D

    Now you can access to your ISPConfig installation at: https://server3.domain.com:8080 or https://4paddress:8080
    The default ISPConfig Username is: admin
    and the Password is: admin
    Warning: This is a security risk. Please change the default password after your first login.

    You will need to edit the username and password in /var/lib/roundcube/plugins/ispconfig3_account/config/config.inc.php of the roundcube user, as the one you set in ISPconfig

    You can visit the GitHub repository at: https://github.com/servisys/ispconfig_setup/
     
  2. adamjedgar

    adamjedgar Member

    hmmm, thats strange...i performed a hard restart and its now working???
     
  3. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    This error may have been the reason. Maybe mysql or mariadb was not running?
    You could have checked with
    Code:
    systemctl --state=failed
    if some services were not running.
    Reboot often solves these services not running problems, unless there is a permanent reason the service can not start.
     
  4. adamjedgar

    adamjedgar Member

    It's just surprising this required a hard reboot to correct a failed state straight after the installer process finished?

    Do you think this could have been a low resource issue? (It's on a fresh 1cpu 1gb ram vps)
     
  5. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    The installer itself should run fine with 1 GB RAM. I have not used the
    myself, but reading this forum indicates that script may fail sometimes, but these failures are not reported to the user. So maybe something went wrong with the autoinstaller, causing database to not run properly.
    Depending on what you run on that host 1 GB may or may not be sufficient. But with 2 or 3 GB swap, it should run just fine, that is no "out of memory" errors. When the system is running, you can monitor memory and swap use and other resource usage to determine if something is running out.
     

Share This Page