Posts by fulltilt

  • https error 503

    IMSCP 1.3.7
    PHP FCGID
    Debian 8


    A customer reported many 503 error from his shop for connections via https.
    /var/log/apache2/example.com/error.log does not exist or is empty only access.log is available.
    Could this be related to the issue w/ the loop of the log mountpoints or should I set FcgidConnectTimeout to a higher value in fcgid_imscp.conf?


    Regards


    ### edit ###
    For now I have I have optimized Apache and changed the customer php-fcgi-starter to: export PHP_FCGI_MAX_REQUESTS=900
    source:
    https://designmeetscode.de/ser…esource-deadlock-avoided/


    Because of the empty error.log ... could be due to the fact that error reporting was turned off ...
    I'll keep you updated.

  • [NOT i-MSCP RELATED] PMA user can no longer delete tables

    @ Nuxwin, will you kill me now?
    I've found the reason for my PMA 403 errors ...
    Incredible ... but modsecurity has caused that!!!
    I use the panel redirect plugin and it seems nginx was overlapped by that ...
    I've put an exception into my mod-sec whitelist

  • unix:/opendkim/opendkim.sock: No such file or directory

    Quote from mrpink

    The output of /etc/default/opendkim please.


    cat /etc/default/opendkim

  • unix:/opendkim/opendkim.sock: No such file or directory

    see debian wiki
    https://wiki.debian.org/opendkim


    It only affects the main.cf

    Code
    1. non_smtpd_milters = unix:/opendkim/opendkim.socksmtpd_milters = unix:/opendkim/opendkim.sock

    I've tested with two different systems for both I had to change to inet socket in main.cf
    Distributor ID: Debian
    Description: Debian GNU/Linux 8.6 (jessie)
    Release: 8.6
    Codename: jessie


    @mrpink

    Code
    1. /var/www/imscp/gui/plugins/OpenDKIM/config.php
    4. 'OpenDKIM_Socket' => 'local:/var/spool/postfix/opendkim/opendkim.sock',
    5. PostfixMilterSocket' => 'unix:/opendkim/opendkim.sock',

  • unix:/opendkim/opendkim.sock: No such file or directory

    IMSCP 1.3.7
    Debian 8


    is there a bug in opendkim?
    Mails are not signed > DKIM check: neutral

    Code
    1. warning: connect to Milter service unix:/opendkim/opendkim.sock: No such file or directory
    Code
    1. ls -l /var/run/opendkimtotal 4-rw-r--r-- 1 root root 5 Nov 3 17:59 opendkim.pidls -l /var/spool/postfix/opendkimtotal 0


    Here's is a quick fix for opendkim ;-)

  • DF, MC very slow since VirtualFileSystem errors

    same problem occurs when changing PHP settings f.ex. switching error reporting on / off
    I can kill the mount loops w/
    umount -l /var/log/apache2/example.com
    but I'm not sure if the killed mountpoint needs to be re-created after that ... I guess it works without re-create it ...


    If there is a quick fix just point me to the right part which has to be changed ... I have some experience with Perl and PHP and I can handle w/ it.
    I do not want to disturb you at work.

  • DF, MC very slow since VirtualFileSystem errors

    Thank you Nuxwin!
    Yesterday I noticed that imscp_traffic was not started I have restarted the server and it looks good until now ... no more duplicate entries from df -a
    I have added a new customer too and everything seems to work.
    Maybe the reason for this is that imscp_traffic service was not started ...
    I guess it can stay that way until the next release.

  • DF, MC very slow since VirtualFileSystem errors

    it seems there is a loop running ...
    the output of df -a shows thousands of the same subdomain entrys

    Code
    1. df -a
    2. /dev/md2 483630616 147098292 311942244 33% /var/log/apache2/subdomain.domain.com
    3. /dev/md2 483630616 147098292 311942244 33% /var/log/apache2/subdomain.domain.com
    4. /dev/md2 483630616 147098292 311942244 33% /var/log/apache2/subdomain.domain.com
    5. /dev/md2 483630616 147098292 311942244 33% /var/log/apache2/subdomain.domain.com
    6. /dev/md2 483630616 147098292 311942244 33% /var/log/apache2/subdomain.domain.com
    7. /dev/md2 483630616 147098292 311942244 33% /var/log/apache2/subdomain.domain.com
    8. ...

    I was able to stop the loop by deleting the subdomain ..


    I will disable the edit button for subdomains until next release ;-)