Is better to wait for the never version.
I don't want to compile it myself. To install the plugin i'd edit the file "/var/www/imscp/gui/plugins/ClamAV/backend/ClamAV.pm" after uploading
This works to finish the installation of the plugin.
It isn't fine but it works
That 'is exactly how I've solved the problem temporarily for one of my client... We're sharing the same brain or what?
If i run "freshclam" i got this message
Code
- Wed Mar 27 20:01:49 2019 -> ClamAV update process started at Wed Mar 27 20:01:49 2019
- Wed Mar 27 20:01:49 2019 -> ^Your ClamAV installation is OUTDATED!
- Wed Mar 27 20:01:49 2019 -> ^Local version: 0.100.2 Recommended version: 0.101.2
- Wed Mar 27 20:01:49 2019 -> DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
- Wed Mar 27 20:01:49 2019 -> main.cld is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
- Wed Mar 27 20:01:49 2019 -> daily.cld is up to date (version: 25401, sigs: 1532768, f-level: 63, builder: raynman)
- Wed Mar 27 20:01:49 2019 -> bytecode.cld is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
And the return code is "1"
Exactly what I said in my previous post. Problem: There is no relevant message helping us to fix the the issue... If you figure out, you're welcome.
Good evening,
This is a problem with freshclam... When updating database, exit code is always 1 but I don't see relevant error message that could help fixing the problem.
Good morning,
Nothing really grave. Just do:
See also: https://linux-audit.com/how-to…-key-keyexpired-with-apt/
I manual download old libicu52 version and install it.I try install now.
Thanks Nuxwin it worked like a charm! Thanks for the great support!
You're welcome.
Thread closed.
Good evening,
This is because they have removed the icu-config executable in latest libicu-dev package (as provided by Ondrey Sury repository).
Please do the following:
Create the following APT preferences file: /etc/apt/preferences.d/phpswitcher
with the following content:
Once done, execute apt-get update && apt-get dist-upgrade. This should downgrade the relevant packages. Then, once the packages were downgraded, retry.
Habe das gleiche Problem seit ein paar Tagen wie hast du es gefixed?
Please have a look at https://serverfault.com/questi…-not-at-maxrequestworkers and also to the official Apache2 documentation.
True ... but I really do not know ..., perhaps doing some test .. as I say I was surprised to see it in the Apache folder.
Thanks for everything
Antonio
You're welcome.
the problem was solved by disabling the apache php7.3 module .. I did not think it was enabled when reconfiguring
thanks to everyone
Yes, that module is not managed by current i-MSCP version. It will be managed in the next maintenance release. Anyway, if the module is there, that mean you have installed it somehow.
