Ultimative verbose logging

[setiseta]

Hi,

I'm using your amavis for my mail service.
And i have seen the output is very heavy.
today it killes me 2 containers running on different hosts with your image.
could it be cause of the ultimative logging?
the container hangs around and wont be stopped.

have you encountered a similar problem?

Thx for help.

[jheretic]

Hi setiseta,

You are correct that there is quite a lot of logging output. Using debug logging with amavisd was something of a stopgap. At the time I was putting together this container, I couldn't get useful logging output from the container at all without putting amavis in debug mode. However, I may revisit this to see if it is still necessary, or if there's another way around it.

I have not experienced similar issues with this container, although if you have partitions or volumes filling up with logs then I suppose an open file descriptor could potentially cause something to hang. I have pretty aggressive log rotation running on my production system though, and consequently haven't seen any problems with logs.

I have occasionally seen issues with containers hanging on docker after a system upgrade, but it's not something unique to this container or even to containers I've created. It has sometimes led me to have to restart the docker daemon.

I will however revisit the logging to see if I can turn down the verbosity from 'debug'.