pfSense com erro de swap

willian_wcg

Bom dia pessoal.
Hoje o pfsense amanheceu com esses erros em tela:

Mar 29 03:31:02 kernel swap_pager_getswapspace(20): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(18): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(9): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(3): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(20): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(18): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(9): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(3): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(20): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(18): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(9): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(3): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(20): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(18): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(9): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(3): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(20): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(18): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(9): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(3): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(20): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(18): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(9): failed
Mar 29 03:31:02 kernel swap_pager_getswapspace(3): failed

Mar 29 03:34:10 kernel pid 30100 (e2guardian), uid 106, was killed: out of swap space

parece-me que é falta de espaço na SWAP, mas a máqui tem 16GB de RAM e uma area de SWAP de 3.8GB.
Tbm está claro q o e2Guardian encheu esse espaço, tem como limitar o tamanho do SWAP para o s2?

@marcelloc help me please!

thiago.informc

Bom dia, aqui acontece a mesma coisa, estou com o e2guardian, e depois da alguns dias funcionando a navegação trava, alguns protocolos da rede funcionam, mas a navegação só volta se o servidor for reiniciado, estou com o mesmo erro em 2 servidores diferentes.