Clamd error in Proxmox MailGateway

[nick]

Hi All,

I just see that in all messages I receive a clamd error (see attachment).

Where to search the error?

I use PMG installed in PVE1.4
Version (package/version/build) proxmox-mailgateway/2.3/4009

 

[nick]

OK, I just restart the clamav-deamon service and the error it's gone. I need to do something more?

I will look to the log files and see what happen next days!

 

[dietmar]

OK, I just restart the clamav-deamon service and the error it's gone. I need to do something more?

Are there any hints in syslog?

 

[nick]

what log do you need?

 

[dietmar]

Please send me all syslog files /var/log/syslog* - please tar/gzip them and send directly to dietmar@proxmox.com

 

[nick]

sorry for delay! I just send you the mail. For more detail, mail me.

 

[nick]

I just see in this morning that the PMG crash...and not work anymore.
So, I restore the machine from backup and next year we will investigate the cause of the error.

 

[dietmar]

I just see in this morning that the PMG crash...and not work anymore.

What do you mean by 'crash' - do you have the syslogs?

So, I restore the machine from backup and next year we will investigate the cause of the error.

You assigned enough memory to the container?

 

[nick]

the machine start but not working! WebUI not work and also no mail goes trough him.

I can connect trough SSH - this work.

For this machine I have allocated 512MB.

 

[dietmar]

For this machine I have allocated 512MB.

Minimum is 1024MB (512RAM+512SWAP)

 

[nick]

Minimum is 1024MB (512RAM+512SWAP)

This is the configuration! 512MB RAM + 512MB Swap

 

[dietmar]

This is the configuration! 512MB RAM + 512MB Swap

This is really strange, because I cant find anything int the logs you sent. If nothing helps, try to run inside a KVM guest.

 

[nick]

I will send you also the last syslog...last 24h

The strange part is that since yesterday I receive few messages from root...that can't be delivered.

The machine is intact! we will analyze what happen next year This is also the first time when a OpenVZ machine broke...without a logic reason.

Anyway, we will see what happen...