Issue With LibClamAV and Memory Upgrades
Hello all, wondering if anyone has see this issue in their logs and may know how to fix it? I've tried to find my clamav folder on my server to see if I could change the memory settings but I have been unsuccessful in locating it. Not even sure if it is the problem but thought I'd try it.
I am not seeing this everyday in Log Watch but occasionally it shows up with different websites that use CleanTalk. I've also create a support ticket with CleanTalk but their solution didn't work and they told me to try increasing the memory in clamav.
Any ideas or suggestions greatly appreciated.
AlmaLinux v8.10.0 STANDARD
cPanel Version 124.0.23
Apache Version 2.4.62
Database Version 8.0.41
Architecture x86_64
Kernel Version 4.18.0-477.27.2.el8_8.x86_64
Php version: 8.2
**Unmatched Entries**
Activating the newly loaded database...
LibClamAV Warning: fmap_readpage: pread fail: asked for 1 bytes @ offset 2736, got 0
LibClamAV Warning: fmap_readpage: pread fail: asked for 3843 bytes @ offset 0, got 0
LibClamAV Warning: fmap_readpage: pread fail: asked for 689 bytes @ offset 0, got 0
LibClamAV Warning: fmap: attempted oof mapping
LibClamAV Error: CRITICAL: fmap() failed
/home//public_html/cleantalk/data/cron_data.php: Can't allocate memory ERROR
-
Hey there! This seems more like an issue with the PHP settings on the server. What is the PHP memory_limit value for this particular domain? Are you able to raise that to see if that changes the behavior in any way?
1 -
cPRex, thanks for the reply and sorry for the delay in responding. I checked the memory limits for the domains in question and they're set to 512mb for both post max and memory limit. Should I try setting them higher? I would have thought that would be sufficient though as the cron_data.php file is only 688kb according to filezilla.
0 -
The size of the file itself doesn't matter, as it's more about what that PHP script is doing in the background. I'd try bumping that limit and if that doesn't change the behavior then it may be best to create a ticket.
1 -
cPRex, thanks again for your reply. I will try bumping the limits but haven't seen them in the logs for a few days now.
See these every day though:
LibClamAV Warning: fmap_readpage: pread fail: asked for 1 bytes @ offset 2736, got 0
LibClamAV Warning: fmap_readpage: pread fail: asked for 3843 bytes @ offset 0, got 0
LibClamAV Warning: fmap_readpage: pread fail: asked for 689 bytes @ offset 0, got 0
LibClamAV Warning: fmap: attempted oof mapping0 -
I'm honestly not sure - do they seem to correlate with any particular work you're doing with cPanel when they appear?
1 -
cPRex, I couldn't tell you whether it is cPanel related as I only check my logs every morning before I start my day and that is when I see them.
I do notice that ClamAV doesn't always update and sometimes it takes a couple of day before it does. I migrated over from Centos to Alma Linux because Centos quit developing so I thought it may be related to that as I don't remember ever seeing those errors in my logs before.
Just thought I'd check here to see if anyone else was seeing the same logs. Not sure if it is serious and needs fixing but it has been this way for a while now and I haven't noticed any issues with the server.
0 -
After some more research it looks like this is a known issue that you can ignore:
https://github.com/tquizzle/clamav-alpine/issues/3
so I wouldn't worry about those as they have been happening intermittently for years.
1 -
cPRex, thanks for that.
0 -
Sure thing!
0
Please sign in to leave a comment.
Comments
9 comments