Posts by fulltilt

    I have updated 10 systems (OS update) 9 of those included a kernel update and one newer system without a kernel update. For the system w/o kernel update, a dialog window appeared and asked should the existing clamav config overwriten yes / no ... for all the other systems, no dialog window was displayed.

    I guess some startup parameters have changed, after a manual "service camav-milter restart" clamav seems to be working, but I have not tested a system reboot yet.

    - IMSCP: 1.5.3 (latest)

    - Distribution: Debian 9

    - Proftpd

    - PHP FPM

    - MariaDB 10.1

    - Dovecot

    - Roundcube

    - Web2FTP

    - Plugins:

    PMA Captcha, RoundCubePlugins, SpamAssassin , LetsEncrypt, PHPswitcher, ClamAV



    after a debian update (incl. clamav) and reboot today, the clamav-milter does not seem to start properly. I started the clamav daemon manually after the system reboot, seems to be running but somewhere it seems that something has changed in the start configurations.


    - IMSCP: 1.5.3 (latest)

    - Distribution: Debian 9

    - Proftpd

    - PHP FPM

    - MariaDB 10.1

    - Dovecot

    - Roundcube

    - Web2FTP

    - Plugins:

    PMA Captcha, RoundCubePlugins, SpamAssassin , LetsEncrypt, PHPswitcher, ClamAV



    currently dovecot seems to be producing a heavy load ... too many connections and processes

    is there a recommendation how to optimize it f.ex. lowering imap_hibernate_timeout

    which files do I have to edit?

    I'm not really an expert with dovecot configuration.

    - IMSCP: 1.5.3

    - Distribution: Debian 9

    - Proftpd

    - PHP FPM

    - MariaDB 10.1

    - Dovecot

    - Roundcube

    - Web2FTP

    - Plugins:

    PMA Captcha, RoundCubePlugins, SpamAssassin , LetsEncrypt, PHPswitcher, ClamAV


    since this morning I can no longer add new hostings to IMSCP (latest)

    Code
    1. [Tue May 7 09:12:25 2019] [fatal] iMSCP::DbTasksProcessor::_processModuleDbTasks: Modules::SSLcertificate::_loadData: DBD::mysql::db do failed: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version
    2. ...propagated at /var/www/imscp/engine/PerlLib/iMSCP/DbTasksProcessor.pm line 496, <$fh> line 184.

    libdbd-mysql-perl is already installed

    Something seems to have gone wrong w/ sury.org ... it worked until this morning and now I get many checksum errors for sury.org packages:

    is this archive already deactivated or can I add a new key and continue w/ the sury updates ...

    or should these sources be removed completely right now?


    Code
    1. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.sury.org/php stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743
    2. W: Failed to fetch https://packages.sury.org/php/dists/stretch/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY B188E2B695BD4743
    3. W: Some index files failed to download. They have been ignored, or old ones used instead.