Posts by Heart1010

    Hi,


    The following cronjob from i-mscp fails on two files....

    Code
    1. Subject: Cron <root@vsrvxyz> /usr/bin/nice -n 19 /usr/bin/find /var/log/imscp/* -maxdepth 1 -type f -mtime +7 -print | xargs -r /bin/rm/bin/rm: Entfernen von „/var/log/imscp/Htaccess_module_htaccess“ nicht möglich: Datei oder Verzeichnis nicht gefunden/bin/rm: Entfernen von „Schutz.log“ nicht möglich: Datei oder Verzeichnis nicht gefunden


    When I look into the imscp log folder I have this:


    "Htaccess_module_htaccess Schutz.log" file name looks strange, doesn't it? (also the other files all have 0 bytes) :huh:


    --
    Distribution in use (Identifiant and codename): Debian GNU/Linux 7 (wheezy)i-MSCP version in use (Version and codename): i-MSCP 1.2.0 Build: 20141230 Codename: AndromedaServer implementation in use: courier, Apache FPM

    Hi,


    wondering if the statistics shown when I login as admin (and click right at the top statistics - "Server Statistics") are calculated correct. After I update to v1.2.0 they became really really high (and going higher each day).


    When I saw that I also installed darkstat to be able to compare the traffic. Running darkstat for about 8 days shows me a total traffic of about 2GB on that really small vServer. When you have a look at that i-MSCP server statistics they are way higher than that (each day!).


    I only have ~5 domains on that dev server. When I login into each of that domains and look there in the i-MSCP statistic page, everything looks ok, small numbers as usual the last months. But as admin > statistics these values are really high.


    (adding all 5 domains i-mscp statistic values also are way smaller than that statistic summary I get shown as admin)


    --
    Distribution in use (Identifiant and codename): Debian GNU/Linux 7 (wheezy)
    i-MSCP version in use (Version and codename): i-MSCP 1.2.0 Build: 20141230 Codename: Andromeda
    Server implementation in use: courier, Apache FPM

    ...selbiges hier (1.2.0). Danke für die Infos!


    Ich hatte die zwei @10* Einträge gelöscht. Daraufhin kamen weitere Fehler

    Code
    1. # php -i | grep ConfigurePHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20100525/mysql.so' - /usr/lib/php5/20100525/mysql.so: undefined symbol: mysqlnd_connect in Unknown on line 0PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php5/20100525/mysqli.so' - /usr/lib/php5/20100525/mysqli.so: undefined symbol: mysqlnd_connect in Unknown on line 0# grep -Hrv ";" /etc/php5 | grep -i "extension="/etc/php5/mods-available/pdo.ini:extension=pdo.so/etc/php5/mods-available/imap.ini:extension=imap.so/etc/php5/mods-available/intl.ini:extension=intl.so/etc/php5/mods-available/mysqlnd.ini:extension=mysqlnd.so/etc/php5/mods-available/mcrypt.ini:extension=mcrypt.so/etc/php5/mods-available/mysqli.ini:extension=mysqli.so/etc/php5/mods-available/pdo_mysql.ini:extension=pdo_mysql.so/etc/php5/mods-available/mysql.ini:extension=mysql.so/etc/php5/mods-available/curl.ini:extension=curl.so/etc/php5/mods-available/gd.ini:extension=gd.so


    Ein

    Code
    1. # aptitude reinstall php5-mysqlnd


    legte dann wiederrum automatisch den @10* Eintrag an

    Code
    1. # l /etc/php5/conf.d/lrwxrwxrwx 1 root root 29 Jan 21 15:25 10-mysqlnd.ini -> ../mods-available/mysqlnd.ini....


    Also noch manuell den @20* Eintrag davon gelöscht

    Code
    1. # rm /etc/php5/conf.d/20-mysqlnd.ini


    ...und nun bleibt die Ausgabe von "php -i | grep Configure" auch leer (gut)!