System corrupted, after poweroff.

Discussion in 'General' started by Isai, Mar 23, 2018.

  1. Isai

    Isai New Member

    On the Digital Ocean droplet, using Ubuntu 16.04.4, after installing ISPConfig, through this shellscript and giving the command poweroff, to create the snapshot, the system returns corrupted and I lose all my Droplet. This has already occurred 5X. Do I need to stop some service before sending poweroff?

    ShellScript Git --> servisys/ispconfig_setup
     
  2. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    I use command
    Code:
    shutdown -h now
    to cleanly stop the host. Give that a try.
     
  3. Isai

    Isai New Member

    I will take a test! Thank you!
     
  4. Isai

    Isai New Member

    Did not work! Droplet corrupted
     
  5. Isai

    Isai New Member

    I did a test with Debian 9 and everything seems to work fine, after poweroff, with ISPConfig3.
    The problem is in Ubuntu + ISPConfig, installed from the self-installing shellscript. (Apache or Nginx
    Dovecot or Courier
    Quota
    Jailkit
    Squirrelmail or Roundcube
    PHPMyadmin
    MySQL
    PHP7.0
    Postfix
    MTA
    AntiVirus
    Fail2ban
    WebStats
    Metronom
    LetsEncrypt
    ISPConfig3)
    Another detail I realized is that ISPConfig hangs when I call the "poweroff" if the Droplet has only 1GB of memory. And that's what corrupts the system.

    Keep my answer to future users who have the same problem.

    ISPConfig3, installed by shellscript, only works well with Debian and with Droplet from 2BG+ of memory.

    Best Regards!
    Isai
     
  6. ahrasis

    ahrasis Active Member

    It's probably better not to rely on installation script. Or may be double check whether it really conforms to ISPConfig perfect server guides or manuals. So far, I do not have problem with Ubuntu + ISPConfig and even intend to upgrade to 18.04 once the stable upgrade is released.
     
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    ISPConfig is not a daemon, so it can not hang. I guess you mix up ISPConfig with another daemon that got installed by the script which hangs. Your problem seems to be an issue in the digital ocean technology. I use ISPConfig on various virtualization solutions and have not seen a corrupted system yet.
     
  8. Isai

    Isai New Member

    Let me correct .... "Ubuntu lock when the call poweroff ..."
     
  9. Isai

    Isai New Member

    Have you ever needed to call poweroff on Ubuntu on a Digital Ocean droplet with ISPConfig installed by shellscript?
     
  10. ahrasis

    ahrasis Active Member

    Nope. I don't use their vps. The only vps I used is amazon and the script worked just fine.

    But I also did check and confirmed all softwares needed are properly installed afterwards.

    My view, contact your service providers and ask them instead. They may know.
     
  11. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    Have you checked everything works after the installation script? For example, disk is not full, the script actually did finish without errors, apt-get upgrade or apt-get install does not show packages that are half installed, etc. I suspect the system was broken before shutdown, so it was not the shutdown or poweroff that did the damage.
     
    ahrasis and till like this.
  12. till

    till Super Moderator Staff Member ISPConfig Developer

    And also check /etc/fstab
     
    ahrasis likes this.
  13. ahrasis

    ahrasis Active Member

    I just remember helping someone in installing a server in Scaleway (two/three months ago) using the same script, it was fine also. Try Taleman and till suggestions above.
     
  14. iqpascal

    iqpascal New Member HowtoForge Supporter

    I am playing around with ISPConfig in both single setup as well als multi server setup on Digital Ocean (And Vultr too) and I do not recognize these issues.
     

Share This Page