Posts by Revi

Revi · Feb 5th 2022

Leider fühle ich mich mittlerweile auch gezwungen auch mal etwas dazu zu sagen.

Ich habe wie 101host über einige "Vorgängerprodukte" mit hin zu i-MSCP gewechselt. Hier habe ich im Laufe der Zeit auch einige kostenpflichtige Plugins gekauft die einfach nur praktisch sind.

Jedoch ist mit einem Alter von mittlerweile über 3 Jahren seit dem letzten Release nun die Grenze auch für mich absolut überschritten diese Software weiter guten Gewissens einsetzen zu können. Ich kann durchaus nachvollziehen dass ein grundlegendes Neuschreiben einer solchen "Applikation" unendlich viel Arbeit ist und lange dauert, vor Allem, wenn man dies augenscheinlich allein nebenbei macht. Dennoch ist es für die bestehende Community einfach aus allen möglichen Gründen der Informations- und IT-Sicherheit einfach unmöglich, weiter auf ein solches Produk zu setzen. Der mehr als berechtigte Wunsch nach einer zumindest groben RoadMap wird leider nur mit einem "das sage ich Euch nicht" abgeschmettert. Auf der anderen Seite kommen plötzlich wieder Ankündigungen, welche OS zukünftig unterstützt werden.

Versteht mich bitte nicht falsch, ich kenne leider KEIN annähernd super Produkt wie i-MSCP im Bezug auf Integration und Bedienung und Verwaltung und habe es wirklich sehr viele Jahre extrem geliebt. Ich setze i-MSCP rein privat ein. Im dienstlichen Bereich bin ich aber als IT-Projektleiter auch entsprechend "vorbelastet" dass ich jetzt auch für mich privat die Entscheidung treffen musste, dass ich dieses Verhalten nicht mehr ruhigen Gewissens akzeptieren kann und sehe daher leider mich zum Abschied gezwungen.

In Zeiten der Super-Schwachstellen wie Log4J (auch wenn hier gerade nicht betroffen) und System- oder Service Anpassungen die ebenfalls in den bezahlten Plugins umgesetzt werden müssen (wie z.B. LetsEncrypt - SSL certificate is not valid ) muss man einfach wissen woran man ist. und das ist man bei i-MSCP leider Gottes so schwer es mir auch fällt nicht mehr. Meine persönliche Prognose ist daher, dass nuxwin hier den vollständigen bisherigen Community-Stamm verlieren wird und mit dem neuen Produkt i-HMS komplett neu anfangen darf. Hierfür drücke ich ihm die Daumen, in wieviel Jahren das dann auch immer starten mag, wir wissen es ja nicht ...

Vielen Dank an alle die mir in den vielen Jahren hier Unterstützung geboten haben!

Revi · Dec 30th 2019

Okay, I did it.

But nevertheless it woult be nice to release the new version in the future ...

Revi · Dec 26th 2019

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 ?

Revi · Dec 23rd 2019

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.

Revi · Dec 23rd 2019

While trying to resolve the Problems with MariaDB 10.2 vs. libmariadbclient18 I bricked the whole database configuration so that I had to hard-reinstall the vServer.

After that, this problem was solved, too.

Revi · Dec 22nd 2019

I just recognized that even dovecot-mysql is not longer installed and I cannot reinstall it because of the missing libmariadbclient18 and so no eMail transmission is possible

Revi · Dec 22nd 2019

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?

Revi · Dec 20th 2019

Goog evening.

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

Code

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

Oliver

Revi · Apr 23rd 2017

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

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

I thank you a lot for your hours

Revi · Apr 22nd 2017

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:

Code

root@srv:~# cat /etc/debian_version
8.7 Codename: jessie
The Logfile /var/logs/imscp_panel.log is empty
root@srv:~# php -v
PHP 5.6.30-10+0~20170412071212.32+jessie~1.gbp3dd061 (cli)
root@srv:~# service imscp_panel status
? imscp_panel.service - PHP FastCGI process Manager Daemon for i-MSCP FrontEnd
Loaded: loaded (/etc/systemd/system/imscp_panel.service; enabled)
Active: failed (Result: exit-code) since Sat 2017-04-22 13:37:05 CEST; 4h 51min ago
Main PID: 513 (code=exited, status=203/EXEC)
Apr 22 13:37:05 srv systemd[1]: Starting PHP FastCGI process Manager Daemon for i-MSCP FrontEnd...
Apr 22 13:37:05 srv systemd[1]: imscp_panel.service: main process exited, code=exited, status=203/EXEC
Apr 22 13:37:05 srv systemd[1]: Failed to start PHP FastCGI process Manager Daemon for i-MSCP FrontEnd.
Apr 22 13:37:05 srv systemd[1]: Unit imscp_panel.service entered failed state.
root@srv:~# service imscp_panel start
Job for imscp_panel.service failed. See 'systemctl status imscp_panel.service' and 'journalctl -xn' for details.
root@srv:~# systemctl status imscp_panel.service
? imscp_panel.service - PHP FastCGI process Manager Daemon for i-MSCP FrontEnd
Loaded: loaded (/etc/systemd/system/imscp_panel.service; enabled)
Active: failed (Result: exit-code) since Sat 2017-04-22 18:28:41 CEST; 29s ago
Process: 6482 ExecStart=/usr/local/sbin/imscp_panel --nodaemonize --fpm-config /usr/local/etc/imscp_panel/php-fpm.conf -c /usr/local/etc/imscp_panel/php.ini (code=exited, status=203/EXEC)
Main PID: 6482 (code=exited, status=203/EXEC)
Apr 22 18:28:41 srv systemd[1]: imscp_panel.service: main process exited, code=exited, status=203/EXEC
Apr 22 18:28:41 srv systemd[1]: Failed to start PHP FastCGI process Manager Daemon for i-MSCP FrontEnd.
Apr 22 18:28:41 srv systemd[1]: Unit imscp_panel.service entered failed state.
root@srv:~# journalctl -xn
-- Logs begin at Sat 2017-04-22 13:37:01 CEST, end at Sat 2017-04-22 18:29:40 CEST. --
Apr 22 18:29:17 srv authdaemond[604]: restarting authdaemond children
Apr 22 18:29:17 srv authdaemond[604]: modules="authmysql authpam", daemons=5
Apr 22 18:29:17 srv authdaemond[604]: Uninstalling authmysql
Apr 22 18:29:17 srv authdaemond[604]: Uninstalling authpam
Apr 22 18:29:17 srv authdaemond[604]: Installing libauthmysql
Apr 22 18:29:17 srv postfix/smtpd[6489]: disconnect from unknown[80.82.70.210]
Apr 22 18:29:17 srv authdaemond[604]: Installation complete: authmysql
Apr 22 18:29:17 srv authdaemond[604]: Installing libauthpam
Apr 22 18:29:17 srv authdaemond[604]: Installation complete: authpam
Apr 22 18:29:40 srv sshd[6496]: Received disconnect from 221.229.162.204: 11: [preauth]

Display More

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

I thank you a lot!

Greetings from Bonn, Germany,
Revi

Posts by Revi

i-HMS ersetzt i-mscp? Weiter kostenfrei?

SpamAssassin Update v2.0.1 to 2.1.0

SpamAssassin Update v2.0.1 to 2.1.0

Update Loop: mariadb-client-core-10.2 vs. libmariadbclient18

LetsEncrypt installation failed on line 266.

Update Loop: mariadb-client-core-10.2 vs. libmariadbclient18

Update Loop: mariadb-client-core-10.2 vs. libmariadbclient18

LetsEncrypt installation failed on line 266.

Admin Panel: Error 502 Bad Gateway after Update 1.4.3

Admin Panel: Error 502 Bad Gateway after Update 1.4.3