GetSwapSpaceError -- I'm not sure why this is happening.

[KevDog]

Hi, the specs of my system are listed below - however I have 64Gb of RAM. The problem I'm having is with one of my created freebsd jails -- it's only purpose is to perform a clamav on the entire system once a week. The actual clamscan I'm finding takes about 2-3 days to do -- perhaps this is the problem. Anyway what I'm noticing is that after about 2-3 weeks worth of runs, the entire FreeNAS system comes to a crawl and I get the getswap space error indicating I'm out of swap space. Perhaps I've configured things incorrectly, however this shouldn't happen. Any suggestions should be helpful

 

[eldo]

Are you running any VMs?
The only time I had a lot of swap errors like you're having is when I had provisioned my VMs with too much RAM and it was interfering with FreeNAS' operation.

 

[KevDog]

Thanks for reply. I'm running three VMs -- two Ubuntu and one Arch Linux - however each is allocated 2048 Mib of RAM. My problem is specifically with the freebsd jail that runs ClamAV. If I dont run this jail, I never have a problem. Is there something about ClamAV that makes it memory hungry?

 

[eldo]

I've never been much for molluscs, don't have any experience with clams.
Seriously though, I've never touched ClamAV.

While you're having the problem, can you get to a shell and check out the jail's memory usage?
I'm not sure the best method to do this, but I do know that when I run htop in a jail, it only shows the jail's processes.

The only other thing I can think of would be to stop the VMs and see how the system behaves.

You might try posting some of the ram usage trends via the reporting tab or the netdata service.
https://www.ixsystems.com/documentation/freenas/11.2-U4.1/services.html#netdata

I'm not sure what it might uncover, but there's a chance the various trends might help.

Good luck, and please report back if you do find the issue and resolve it.

 

[KevDog]

While you're having the problem, can you get to a shell and check out the jail's memory usage?
I'm not sure the best method to do this, but I do know that when I run htop in a jail, it only shows the jail's processes.

When I'm having a problem or get the error message, the system is completely unusable -- I have to power down the entire system. The clamav needs to do like 2-3 scans before the system locks. What I'll do is go through one pass and then see if something is still tied up in memory.

 

[KevDog]

Ok - I rebooted the system and then the freebsd jail ran the clamscan -- here is a snippet of my look -- It takes 4 days to perform the scan -- and I keep getting a wake up received signal --- any reason why? (I've only posted a few of the wakeup notifications contained within the log -- the email I receive when the scan is done is very very long.

Code:

Scan being started on ClamAV-FreeBSD-jail@10.0.1.155

ClamAV Scan started at: 2019-06-09 02:00:00

ClamAV Scan finished at: 2019-06-13 06:41:13

--------------------------------------
ClamAV Scan Summary
--------------------------------------
Engine version: 0.101.2
Scanned directories: 82199
Scanned files: 1216932
Infected files: 21
Not removed: 21
Data scanned: 4510864.36 MB
Data read: 2489868.97 MB (ratio 1.81:1)
Time: 362472.205 sec (6041 m 12 s)


--------------------------------------
freshclam log file
--------------------------------------
freshclam daemon 0.101.2 (OS: freebsd11.2, ARCH: amd64, CPU: amd64)
ClamAV update process started at Tue Jun  4 08:20:11 2019
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
Downloading daily-25458.cdiff [100%]
Downloading daily-25459.cdiff [100%]
Downloading daily-25460.cdiff [100%]
Downloading daily-25461.cdiff [100%]
Downloading daily-25462.cdiff [100%]
Downloading daily-25463.cdiff [100%]
Downloading daily-25464.cdiff [100%]
Downloading daily-25465.cdiff [100%]
Downloading daily-25466.cdiff [100%]
Downloading daily-25467.cdiff [100%]
Downloading daily-25468.cdiff [100%]
Downloading daily-25469.cdiff [100%]
Downloading daily-25470.cdiff [100%]
daily.cld updated (version: 25470, sigs: 1588120, f-level: 63, builder: raynman)
bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
Database updated (6154463 signatures) from database.clamav.net (IP: 104.16.219.84)
Clamd successfully notified about the update.
--------------------------------------
Update process terminated
--------------------------------------
freshclam daemon 0.101.2 (OS: freebsd11.2, ARCH: amd64, CPU: amd64)
ClamAV update process started at Tue Jun  4 08:29:35 2019
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
daily.cld is up to date (version: 25470, sigs: 1588120, f-level: 63, builder: raynman)
bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
--------------------------------------
Received signal: wake up
ClamAV update process started at Tue Jun  4 10:29:35 2019
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
daily.cld is up to date (version: 25470, sigs: 1588120, f-level: 63, builder: raynman)
bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
--------------------------------------
Received signal: wake up
ClamAV update process started at Tue Jun  4 12:29:35 2019
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
daily.cld is up to date (version: 25470, sigs: 1588120, f-level: 63, builder: raynman)
bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
--------------------------------------
Received signal: wake up
ClamAV update process started at Tue Jun  4 14:29:35 2019
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
daily.cld is up to date (version: 25470, sigs: 1588120, f-level: 63, builder: raynman)
bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
--------------------------------------
Received signal: wake up
ClamAV update process started at Tue Jun  4 16:29:35 2019
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
daily.cld is up to date (version: 25470, sigs: 1588120, f-level: 63, builder: raynman)
bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
--------------------------------------
Received signal: wake up
ClamAV update process started at Tue Jun  4 18:29:35 2019
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
daily.cld is up to date (version: 25470, sigs: 1588120, f-level: 63, builder: raynman)
bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
--------------------------------------
Received signal: wake up
ClamAV update process started at Tue Jun  4 20:29:36 2019
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
daily.cld is up to date (version: 25470, sigs: 1588120, f-level: 63, builder: raynman)
bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
--------------------------------------
Received signal: wake up
ClamAV update process started at Tue Jun  4 22:29:36 2019
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
daily.cld is up to date (version: 25470, sigs: 1588120, f-level: 63, builder: raynman)
bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
--------------------------------------
Received signal: wake up
ClamAV update process started at Wed Jun  5 00:29:36 2019
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
daily.cld is up to date (version: 25470, sigs: 1588120, f-level: 63, builder: raynman)
bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
--------------------------------------
Received signal: wake up
ClamAV update process started at Wed Jun  5 02:29:36 2019
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
daily.cld is up to date (version: 25470, sigs: 1588120, f-level: 63, builder: raynman)
bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
--------------------------------------
Received signal: wake up
ClamAV update process started at Wed Jun  5 04:29:36 2019
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
Downloading daily-25471.cdiff [100%]
daily.cld updated (version: 25471, sigs: 1588778, f-level: 63, builder: raynman)
bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
Database updated (6155121 signatures) from database.clamav.net (IP: 104.16.218.84)
Clamd successfully notified about the update.
--------------------------------------
Received signal: wake up
ClamAV update process started at Wed Jun  5 06:29:59 2019
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
daily.cld is up to date (version: 25471, sigs: 1588778, f-level: 63, builder: raynman)
bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
--------------------------------------
Received signal: wake up
ClamAV update process started at Wed Jun  5 08:29:59 2019
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
daily.cld is up to date (version: 25471, sigs: 1588778, f-level: 63, builder: raynman)
bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
--------------------------------------
Received signal: wake up
ClamAV update process started at Wed Jun  5 10:29:59 2019
main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
daily.cld is up to date (version: 25471, sigs: 1588778, f-level: 63, builder: raynman)
bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)