To change for a too long time

    Base system was Ubuntu 13.10, i-MSCP 1.1.0 without any specific tuning exept Zend & ioncube
    Production hosting server
    Ubuntu was updated to 14.04 LTS without errors, but apache hasn't started
    After that was problem with detection, which has been solved with

    Code
    1. apt-get remove lsb-release


    On the step 19 (i-mscp 1.1.3/1.1.5 both) for the one of the domains (each time the same) i have tochange process for a very long time (maximum for a half of an hour, before i killed it).
    What it can be?
    PS Customers made a lot of wrong dirs in the domain root (where htdocs is situated)? but cleanup didn't solve the problem. :/

    hmm, finally it's done fot the 1.1.3 during 50 minutes.
    Updating to 1.1.5...
    /usr/bin/named -4 -u bind has 5-6 child processes but not loadind the CPU (about 2%)
    What is the chown -h -R... And it's at the same time with bind processes...

    I can say solved, but the problem was in the size of site. It's really very hard work to chown -R about 2GB of small php files, also system can't delegate cpu power to this process (???) Also for such products it may be difficult to backup.

    Hello ;


    About the first error (disto detection), this occur in some case when you update your distro. Generally, rebooting the system after the update solve the problem.


    The process can take several minutes depending of the number of customers you have. One thing you must know is that during each update, the installer sets the permissions on the Web folder directories recursively. The same thing is done on the /var/mail/virtual/* directories. This task can take several time. In near future, I'll add an option which allow to skip that step.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    SSH key for online support
    Quote from Nuxwin

    Hello ;


    About the first error (disto detection), this occur in some case when you update your distro. Generally, rebooting the system after the update solve the problem.


    So it was not solved after reboot (string says that '%name of the distro%' is not supported, I met it as for 13.10 as for 14.04solved ONLY by deleting lsb-release).

    Quote from Nuxwin

    The process can take several minutes depending of the number of customers you have. One thing you must know is that during each update, the installer sets the permissions on the Web folder directories recursively. The same thing is done on the /var/mail/virtual/* directories. This task can take several time. In near future, I'll add an option which allow to skip that step.


    It's very annoying when updating one of the customers, when it's size about only 2 GB takes about an hour. I have no rights to control my customers of quoted disk space usage. it's legal. :(

    Re;


    Don't worry, in next release will be added an option such as --skip-permissions, which will allow you to skip the permission settings process on Web folders and mail directories. With such option, the process will really be cheap in term of time and IO access. Of course, if some of your customer's permissions are wrong, you'll have to fix them manually.


    About the first error (distro detection), This was surely due to a mix of packages (old version, new version) in your sources.list file. Indeed, lsb_release is using apt-cache policy to determine your distro... In some cases, the process fail because the algorithm in use is not free of any errors. It's a know issue...

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    SSH key for online support

    To summarize about lsb_release :



    You can find the same warning in the official lsb_release source code ;)

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    SSH key for online support

    Don't keep in your mind, just an idea...
    Maybe it will be a good option for subdomains to choose what to backup. Problem is the same, but with backup, dayly and by cron.
    Sometimes vip-users need to make for example image gallery with 2-4GB of pictures, but it will be compressing several minutes. In example we don't need to backup pictures, but needs to backup site & database.
    So, I must create another customer for this customer called "img.customer.tld" without backups. Sometimes it's hard to explain why like that...

    I agreed, the backup feature is really a mess. This is really more a resource killer than other thing.
    We can add an option which should allow to exclude some filetype and directories as well. Maybe you can create a ticket for that?

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

    SSH key for online support