Posts by Grex

  • update 1.2.11 to 1.2.12 failed (php-fpm.pool.default)

    Hi,


    thank you! Now I get another error :( (maybe bad day today...):

    Code
    1. ERROR] iMSCP::Stepper::step: Could not restart the imscp_network service: iMSCP::Provider::Service::Sysvinit::_exec: start: Job failed to start at /tmp/imscp_1.2.12/imscp-1.2.12/engine/PerlLib/iMSCP/Service.pm line 207.autoinstaller::Functions::install: An error occurred while performing installation steps


    If I try to start by myself with service imscp_network start, it comes:


    Code
    1. start: Job failed to start

    I haven't found any log file for imscp_network at /var/log/imscp

  • update 1.2.11 to 1.2.12 failed (php-fpm.pool.default)

    Hi,


    first, I got an error because I had a file called imscp under /tmp/

    Code
    1. ERROR] iMSCP::Stepper::step: Could not create /tmp/imscp: Already exists as file. at /tmp/imscp_1.2.12/imscp-1.2.12/engine/PerlLib/iMSCP/Dir.pm line 210.autoinstaller::Functions::build: An error occurred while performing build steps


    After deleting this file and run autoinstall again, I get the error, that php-fpm.pool.default does not exists:


    Code
    1. [ERROR] iMSCP::File::get: Unable to open /etc/imscp/php-fpm/php-fpm.pool.default: No such file or directory
    2. Servers::httpd::apache_php_fpm::buildConfFile: Unable to read /etc/imscp/php-fpm/php-fpm.pool.default
    3. autoinstaller::Functions::install: An error occurred while performing installation steps

    What I have to do, that it will work? I cannot find the default file.

  • dovecot config

    EDIT:
    Thanks that helpded me, the imscp-autoinstall is located on /imscp-autoinstall (yes at root)
    It asked me "do you want to continue setup (after installing packages), I choosed NO and now it works!

  • dovecot config

    Hello,


    today I did a mistake. I removed a package that included dovecot!
    I installed it again, but now the mails are not working.


    The reinstalling made a dovecot.conf.bak that conaints the old configuration. I enabled this of rename it to dovecot.conf
    The sql file for dovecot is the same as before (all datas are entered)


    Now if I'm reciving an mail I get an SASL error:
    Dec 27 00:14:23 sa-rl postfix/smtpd[26346]: connect from mail-wi0-f177.google.com[209.85.212.177]
    Dec 27 00:14:23 sa-rl postfix/smtpd[26346]: warning: SASL: Connect to private/auth failed: No such file or directory
    Dec 27 00:14:23 sa-rl postfix/smtpd[26346]: fatal: no SASL authentication mechanisms
    Dec 27 00:14:24 sa-rl postfix/master[25303]: warning: process /usr/lib/postfix/smtpd pid 26346 exit status 1
    Dec 27 00:14:24 sa-rl postfix/master[25303]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling


    There is no auth folder/file at /var/spool/postfix/private
    How I can fix this issue?

  • Apache Logs

    Great!,



    thanks for informing! I didn't know, that would be created in the daily cron, I'm sry. I will change it, that there will be the monthly log.


    Thanks!

  • Apache Logs

    Quote from Nuxwin


    Hello ;


    You are talking about what logs exactly ? Those under /var/log/apache2 or those that are under /var/www/virtual/<domain.tld>/logs ???


    Hello,


    thanks for replying in the german corner!


    I'm talking about /var/www/virtual/<domain.tld>/logs


    I tought there should be the access and error each vhost at this directory, isn't it?
    At the moment there are no own log files for each vhost, there are all in one at /var/log/apache2/other_vhosts_access.log and error-default.log


    I want to create two logs (access and error) for each vhost/domain and will be located in /var/www/virtual/<domain.tld>/logs



    Have a nice weekend.

  • Apache Logs

    Hi,


    habe i-mscp erfolgreich an einem Debian 6.0 64 Bit Sys installiert, jedoch hab ich ncoh ein kleines Problem...
    Es handelt sich darum, dass die logs in der jeweiligen virtualhosts leer sind (keine Dateien vorhanden im logs Ordner).


    In den vhosts vom apache2 config sind keine Logeinträge vorhanden, dann ist die Ursache schonmal klar.


    Nun die Frage: Soll ich selbst die Log configs in den jeweiligen vhosts vornehmen, oder gibt es irgendwo eine Einstellung (die ich nicht gefunden habe).


    Thanks und schönes Wochenende,
    Grex


    EDIT: Habe die i-mscp 1.0.3.0 Stable Version. (Build 20120323)