Hello All,

It's been a while since i've been on this forum & posted a thread - I apologise if this has been posted and answered already (I did search, honest...) I have searched various forums and via search engines.

I'm running 2 * Centos 6.9 (Final) servers. The one with the issue acts as a backup server and FTP server for my domain. The clamdscan clamd daemon rather than clamav is used to automatically scan all files after they have been uploaded.

The following depicts an existing folder structure & filename:

/media/FTP_WIN1/WINDOWS_DATA/DATA/USB_DRIVE/IMAGES/RAW02/RAW02_210816offline_C_full_b1_s1_v1.tib with RAW02_210816offline_C_full_b1_s1_v1.tib referring to the filename.

On scanning the file I receieve the following error message:

/media/FTP_WIN1/WINDOWS_DATA/DATA/USB_DRIVE/IMAGES/RAW02/RAW02_210816offline_C_full_b1_s1_v1.tib: Can't allocate memory ERROR

I have confirmed that if I shorten the filename whilst maintaining the exisiting folder structure, it works perfectly; and if I copy the file maintaining the original name to a higher parent folder and then scan it - this also works. This indicates that the total no. of characters combined in the folders / sub-folders and filename itself are causing the issue.

The clamd.conf configuration file contains the entry

# Stop daemon when libclamav reports out of memory condition.
ExitOnOOM no

Enabling this option does not prevent the above condition occuring.

Thanks for reading this & once again I apologise if this has been raised before.

Has anyone any ideas / suggestions to resolve the issue?

Regards,

Rawcous!!!

What does the log say?

Hello Mr Awesome,

Thanks for coming back to me. Unfortunately there does not seem to be any log entries generated that correspond with this particular issue other than that reported in clamd.log which I have provided.

In addition I have found that if I use clamscan instead of clamdscan then it works perfectly in all situations. I prefer to use the daemon alternative as it is quicker and does not require the use of a ridiculously long command line as it takes its input from a configuration file.

Regards,

Rawcous!