I can't comment on this particular error but 2G of RAM is definitely insufficient and I believe 4G would be as well when freshclam is applying updates to the database as there would be 2 copies of it in RAM.
Dave. On 2022-03-17 07:25, Stephen Scotter via clamav-users wrote: > Hi, > > I noticed Clamd has unexpectantly died on two of my virtual machines. > Investigating lead me to find similar errors in the logs on both hosts around > the times I know clamd died (I'm monitoring for the existence of a clamd > process with zabbix but only got around to investigating today due to other > commitments) > > > System1 > Virtual Machine > CPU : 1 socket / 2 cores > RAM : 2GB Ram (I must have been feeling frugal on the day I created that VM) > OS : Debian 10 / buster > Clam : ClamAV 0.103.5/26484/Thu Mar 17 08:28:38 2022 > > Mar 13 13:14:27 System1 clamd[9495]: LibClamAV Warning: fmap_readpage: pread > fail: asked for 901703 bytes @ offset 4096, got 0 > Mar 13 13:14:27 System1 clamd[9495]: LibClamAV Error: fmap_get_MD5: error > reading while generating hash! > Mar 13 13:14:27 System1 systemd[1]: clamav-daemon.service: Main process > exited, code=killed, status=11/SEGV > Mar 13 13:14:27 System1 systemd[1]: clamav-daemon.service: Failed with result > 'signal'. > > System2 > Virtual Machine > 1 socket / 2 cores > 4GB Ram (This is our standard allocation; This VM isn't in production yet and > isn't doing anything) > OS : Debian 11 / bullseye > Clam : ClamAV 0.103.5/26484/Thu Mar 17 08:28:38 2022 > > > Mar 9 19:56:17 System2 clamd[541]: LibClamAV Warning: fmap_readpage: pread > fail: asked for 455239 bytes @ offset 450560, got 0 > Mar 9 19:56:17 System2 clamd[541]: LibClamAV Error: fmap_get_MD5: error > reading while generating hash! > Mar 9 19:56:17 System2 kernel: [19292.532221] clamd[6494]: segfault at 0 ip > 00007f73de568a08 sp 00007f73777fd410 error 4 in > libclamav.so.9.0.5[7f73de491000+11d000] > Mar 9 19:56:17 System2 systemd[1]: clamav-daemon.service: Main process > exited, code=killed, status=11/SEGV > Mar 9 19:56:17 System2 systemd[1]: clamav-daemon.service: Failed with result > 'signal'. > Mar 9 19:56:17 System2 systemd[1]: clamav-daemon.service: Consumed 20min > 43.611s CPU time. > > This feels like it could be related to a lack of RAM? Would anyone be able to > confirm I'm on the right track before shutdown the VMs to I allocate Ram? > > Cheers > > Steve > > _______________________________________________ > > clamav-users mailing list > clamav-users@lists.clamav.net > https://lists.clamav.net/mailman/listinfo/clamav-users > > > Help us build a comprehensive ClamAV guide: > https://github.com/vrtadmin/clamav-faq > > http://www.clamav.net/contact.html#ml _______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
