Posts by Revi

    In Nov'18 (Thread IP-1808) an SpamAssassin Update was "announced" for the soon available SpamAssassin Plugin in Version 2.1.0.


    I still run SpamAssassin 2.0.1, flooding my logfile with spamd[23783]: auto-whitelist: sql-based get_addr_entry ... none: SQL error: Unknown column 'last_hit' in 'order clause'


    So my Question: Does it make more sense to alter my database manually or should I wait for the release 2.1.0 ?

    Interesting Problem... Trying to solve the problem I recognized that more and more problems occurred wihle (re)installing related packages. so I bricked my Server installation an had to hard-reinstall the whole vServer.

    BUT up to yesterday the installation with MariaDB 10.2 worked fine, today I was even able to install iMSCP with 10.2 but installation with 10.1 worked fine.

    I'm just trying to update my i-MCSP Installation from 1.5.3 Build: 20180516 to Build 20181208.


    During this Update the installer always stops because of "unmet dependencies", an now the installatin loop begins:


    iMSCP Update Error 1.png


    root@srv2:~# apt-get update

    Hit:1 http://security.debian.org/debian-security stretch/updates InRelease

    Hit:2 http://mirror.netcologne.de/mariadb/repo/10.2/debian stretch InRelease

    Hit:3 https://packages.sury.org/php stretch InRelease

    Ign:4 http://ftp.us.debian.org/debian stretch InRelease

    Hit:5 http://ftp.us.debian.org/debian stretch Release

    Reading package lists... Done



    root@srv2:~# apt-get upgrade

    Reading package lists... Done

    Building dependency tree

    Reading state information... Done

    Calculating upgrade... Done

    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.



    root@srv2:~# apt update

    Hit:1 http://security.debian.org/debian-security stretch/updates InRelease

    Hit:2 http://mirror.netcologne.de/mariadb/repo/10.2/debian stretch InRelease

    Hit:3 https://packages.sury.org/php stretch InRelease

    Ign:4 http://ftp.us.debian.org/debian stretch InRelease

    Hit:5 http://ftp.us.debian.org/debian stretch Release

    Reading package lists... Done

    Building dependency tree

    Reading state information... Done

    All packages are up to date.



    root@srv2:~# apt upgrade

    Reading package lists... Done

    Building dependency tree

    Reading state information... Done

    Calculating upgrade... Done

    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.



    root@srv2:~# apt install mariadb-client-10.2

    Reading package lists... Done

    Building dependency tree

    Reading state information... Done

    Recommended packages:

    libdbd-mysql-perl libterm-readkey-perl

    The following NEW packages will be installed:

    mariadb-client-10.2

    0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.

    Need to get 0 B/1,111 kB of archives.

    After this operation, 23.9 MB of additional disk space will be used.

    Selecting previously unselected package mariadb-client-10.2.

    (Reading database ... 53994 files and directories currently installed.)

    Preparing to unpack .../mariadb-client-10.2_10.2.30+maria~stretch_amd64.deb ...

    Unpacking mariadb-client-10.2 (10.2.30+maria~stretch) ...

    Processing triggers for man-db (2.7.6.1-2) ...

    Setting up mariadb-client-10.2 (10.2.30+maria~stretch) ...




    root@srv2:~/i-MSCP-imscp-19f9902# perl imscp-autoinstall -d


    iMSCP Update Error 2.png



    root@srv2:~# apt install libmariadb3

    Reading package lists... Done

    Building dependency tree

    Reading state information... Done

    libmariadb3 is already the newest version (10.2.30+maria~stretch).

    libmariadb3 set to manually installed.

    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.



    root@srv2:~# apt install libmariadbclient18

    Reading package lists... Done

    Building dependency tree

    Reading state information... Done

    The following package was automatically installed and is no longer required:

    libreadline5

    Use 'apt autoremove' to remove it.

    The following packages will be REMOVED:

    libmariadb3 mariadb-client-10.2 mariadb-client-core-10.2

    The following NEW packages will be installed:

    libmariadbclient18

    0 upgraded, 1 newly installed, 3 to remove and 0 not upgraded.

    Need to get 0 B/782 kB of archives.

    After this operation, 28.0 MB disk space will be freed.

    Do you want to continue? [Y/n] y

    (Reading database ... 54030 files and directories currently installed.)

    Removing mariadb-client-10.2 (10.2.30+maria~stretch) ...

    Removing mariadb-client-core-10.2 (10.2.30+maria~stretch) ...

    Removing libmariadb3 (10.2.30+maria~stretch) ...

    Selecting previously unselected package libmariadbclient18:amd64.

    (Reading database ... 53976 files and directories currently installed.)

    Preparing to unpack .../libmariadbclient18_10.1.41-0+deb9u1_amd64.deb ...

    Unpacking libmariadbclient18:amd64 (10.1.41-0+deb9u1) ...

    Setting up libmariadbclient18:amd64 (10.1.41-0+deb9u1) ...

    Processing triggers for libc-bin (2.24-11+deb9u4) ...

    Processing triggers for man-db (2.7.6.1-2) ...



    root@srv2:~/i-MSCP-imscp-19f9902# perl imscp-autoinstall -d


    iMSCP Update Error 1.png


    Does anyone has a great idea how to solve this issue? <X

    Goog evening.


    I just bought the LetsEncrypt Plugin and tried to install it. But it always just ends in an unexpected Error:

    Code
    1. Plugin::LetsEncrypt::enable: E: Unable to correct problems, you have held broken packages. at /var/www/imscp/gui/plugins/LetsEncrypt/backend/LetsEncrypt.pm line 266

    But even after reading some posts like LetsEncrypt 3.5.0 install fails (due to SSL version?) on Debian 9.11 and "all Debian updates" I was not able solve the problem.


    I'm not quite sure which information you need to help me so I just give you some input:

    vServer: Debian 9.11

    i-MSCP 1.5.3 Build: 20180516 Codename: Ennio Morricone

    LetsEncrypt: 3.5.0 (Build 2018071900)


    Thanks for your Help :thumbsup:

    Oliver

    @Nuxwin worked hard on my Server to find and resolve the problem :thumbup:


    However this could happen there was a bad symlink for the panel PHP binary ;(


    Just about the history of this Server:
    Fresh Installation with Debian Jessie 8 and i-mscp 1.2.17 in 03/2016
    Update to i-mscp 1.3.7 in 11/2017
    Update to i-mscp 1.4.3 yesterday.


    I got the advice from @Nuxwin to update more often :idea:


    I thank you a lot for your hours :thumbsup:

    Dear Nuxwin and UncleJ ,


    thanks for your patience, information and Engagement.


    I searched in different logfiles and collected the hopefull needed information for you.


    So here is what i found out:




    Beside this I sent an eMail to Nuxwin for the chance that you would ckeck some things at the server yourself <3


    I thank you a lot!



    Greetings from Bonn, Germany,
    Revi