The service 'clamav-freshclam' on server * is currently down

Yes Richard, thanks, but snapshots are not available on hybrid vps (my case). I don't know if it is possible to take a snapshot from my vps in worst scenario. That is why I asked for what crucial files should not be missing in backup procedure.
 
That is what the official Alma site is pointing to, so probably that is a good one.

Maybe @Active8 has some additional tips to what I mentioned about which crucial files at least to backup.
 
Thanks Richard!

Is there any option to disable this two services as "down" ? I dit not find the way to removed them from DA build from new UI.
Some terminal command to disable and kill them (temporally)?
 
You're welcome.
As for the status commands, you might want to remove them from the /usr/local/directadmin/data/admin/services.status file so they won't be shown.
You can also use this command for the time being, just to be sure.

Code: 
cd /usr/local/directadmin/custombuild
./build set clamav no
./build set clamav_exim no

You can enable them later again when needed.
 
Unfortunately,I am still having problems after fixing my issues with clamav, I keep getting a ton of messages "The service 'clamd@scan' on server XYZ is currently down". When I check DA, however, it seems to be running fine. Any ideas?
 
The history of my clamav installation is on page 2 of this thread (in case you want to check). The distro is CentOS 7 and according to the custombuild logs, clamav was fully removed before reinstallation.

This seems to be happening at random hours (5:26, 7:23, 8:46, 9:55). One day I get a lot of these messages, on another, not so many.
 
Ah oke I didn't read previous posts so did not know that. Since you said it was fixed then, did it suddenly start happening again?
It shouldn't happen though.

Can you check the /usr/local/directadmin/data/admin/services.status file to see if it only contains these two concerning clamav?
clamd@scan=ON clamav-freshclam=ON

And which DA version are you running?
Still got the feeling something old is left somewhere.

Maybe @zEitEr has some idea about this happening? I'm not that into clamav.
 
Hi Richard,

There seems to be a misunderstanding, so let me elaborate. Orignally, clamav wouldn't run - that problem was fixed (install worked, and clamav shows up in DA services as running, including PID). Ever since that fix, however, I am receiving those error messages.

EDIT: I thought the messages were false alarm (hence my post) but I checked the message log and it seems like the "new" clamd is using all the memory on the server and is killed every time it does so.

Feb 19 23:09:23 server kernel: OOM killed process 12233 (clamd) total-vm:1517180kB, anon-rss:1288724kB, file-rss:1620kB Feb 19 23:09:23 server systemd: [email protected]: main process exited, code=killed, status=9/KILL Feb 19 23:09:23 server systemd: Unit [email protected] entered failed state. Feb 19 23:09:23 server systemd: [email protected] failed. Feb 19 23:09:24 server systemd: [email protected] holdoff time over, scheduling restart. Feb 19 23:09:24 server systemd: Stopped clamd scanner (scan) daemon. Feb 19 23:09:24 server systemd: Starting clamd scanner (scan) daemon...
 
Still couldn't find a fix for the "new" clamd running out of memory. I'm on a VPS with 6 GB of RAM. Is that considered "not enough" these days, i.e. does everyone here who doesn't have issues have more ram than that?

Code: 
free -m
              total        used        free      shared  buff/cache   available
Mem:           6144        3317         742         616        2083        2209
Swap:             0           0           0
 
ClamAV is taking roughly 1.2 GB on our servers, you are sure nothing is used for cache ?

EDIT: I see that its cached = 2083 MB so nothing to worry about then , but you should add SWAP like @jamgames2 suggest
 
Last edited:
Seems like I can't add swap due to the fact that it's a VPS (limitations of OpenVZ or similar).

EDIT: Just as a note for anyone with similar issues, I ended up rebooting the server, and didn't have those problems since (I guess that freed up more memory). But I'm still receiving 1-2 messages per day that freshclam or clamd are down. Unlike before the reboot, there are no more OOM messages, and syslog doesn't want to be more specific about the reason.

Code: 
Apr  4 01:26:59 server freshclam: Update process terminated
Apr  4 01:26:59 server systemd: Stopping ClamAV virus database updater...
Apr  4 01:26:59 server systemd: Stopped ClamAV virus database updater.
Apr  4 01:26:59 server systemd: Started ClamAV virus database updater.
Apr  4 01:26:59 server freshclam: ClamAV update process started at Tue Apr  4 01:26:59 2023
Apr  4 01:26:59 server freshclam: daily.cld database is up-to-date (version: 26864, sigs: 2028069, f-level: 90, builder: raynman)
Apr  4 01:26:59 server freshclam: main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr)
Apr  4 01:26:59 server freshclam: bytecode.cvd database is up-to-date (version: 334, sigs: 91, f-level: 90, builder: anvilleg)

Code: 
Apr  6 01:27:24 server freshclam: Received signal: wake up
Apr  6 01:27:24 server freshclam: daily.cld database is up-to-date (version: 26866, sigs: 2028394, f-level: 90, builder: raynman)
Apr  6 01:27:24 server freshclam: main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr)
Apr  6 01:27:24 server freshclam: bytecode.cvd database is up-to-date (version: 334, sigs: 91, f-level: 90, builder: anvilleg)
Apr  6 01:29:06 server systemd: Stopping clamd scanner (scan) daemon...
Apr  6 01:29:08 server systemd: Stopped clamd scanner (scan) daemon.
Apr  6 01:29:08 server systemd: Starting clamd scanner (scan) daemon...
Apr  6 01:29:42 server systemd: Started clamd scanner (scan) daemon.
Apr  6 01:29:43 server systemd: Stopping clamd scanner (scan) daemon...
Apr  6 01:29:47 server systemd: Stopped clamd scanner (scan) daemon.
Apr  6 01:29:48 server systemd: Starting clamd scanner (scan) daemon...
Apr  6 01:30:17 server systemd: Started clamd scanner (scan) daemon.
 
Last edited:
LibClamAV Warning: Detected duplicate databases /var/lib/clamav/bytecode.cvd and /var/lib/clamav/bytecode.cld, please manually remove one of them
LibClamAV Warning: Detected duplicate databases /var/lib/clamav/bytecode.cvd and /var/lib/clamav/bytecode.cld, please manually remove one of them

CentOS 7 - I get this error from multiple servres too.
 
SupermanInNY said:
I get this error from multiple servres too.
Click to expand...
I had this too on the Centos 7 servers, but the solution is stated in the warning.
I've removed the bytecode.cld file and after that all was fine. You can also remove both, if all is well the bytecode.cvd will be created again when Clamav gets the new definitions. Backup the file before trying just to be sure.
 
Hello, I got the same problem on a CentOS 7 server with epel installed and trying to install clamav gave me the "no package available" error.
I only needed to uninstall and then reinstall epel to solve the problem using @Richard G suggestion

Code: 
yum remove epel-release
yum install epel-release
yum install clamav-server clamav-data clamav-update clamav-filesystem clamav clamav-scanner-systemd clamav-devel clamav-lib clamav-server-systemd
cd /usr/local/directadmin/custombuild
./build update
./build clamav
 
Strator said:
Odd stuff. Seems like the epel repository was somehow... broken. In the end, running the following steps fixed it.

Then I installed and started clamav via DA and everything is fine again now.

Thanks for your assistance - always a huge help to have someone consider possible options.
Click to expand...

This works! fix all issues with PHP 5.6 installation, mcrypt, exim and clamav
 
You must log in or register to reply here.
Back
Top