What does status unhealthy mean, esp. for mailserver-mda, and how to avoid it? #132
Comments
|
Hey! |
|
Thank you for the hint! It is always the same: What can I do about it? I notice that the load of the machine is decently high. Can this be the cause? If so, how to alleviate it? |
|
It sure looks like the problem is related to load. Load is low right now, I will check what happens if load is high again and I do not stop and start -- behavior should be the same. I will have to wait for a week or so and then for days load will be high again. |
|
@kklepper yes, it seems to be the load issue. |
|
It turns out that load is not the issue. I got one email with load 0.79 so far. But even if state is healthy, there are errors in the log as I witnessed right now (time is UTC): To me it looks like the last error results in a healthy state, though. Confusing. The mail was triggered at 16:50 local time, so the following excerpt applies: What to learn from this? |
|
status is healthy but the log does not look nice, in particular the last line:
|
What does
|
Do I understand correctly?MTA delivers mail, MDA distributes this mail to users? As I send an email if I detect As I receive very little mail on this account, can it be that the errors are triggered because there is no mail to be delivered? |
|
As i understand - MDA does:
MTA:
I also have aborted logins in MDA logs, i think it is spammers trying to send emails via our servers. As for unhealthy state - i got some situations on a weak hosting VPS - especially the antivirus got too high cpu usage showing in htop. And again: Mail amount should not affect the errors at all... |
|
Thank you very much, vassad! Spam does not seem to be the issue.
This may very well be the case and would explain the errors and why normal business is ok. I think I have learned something and should just check |
|
@kklepper Glad if i could help :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://github.com/jeboehm/docker-mailserver/wiki/Troubleshooting
Describe the bug
A clear and concise description of what the bug is.
I stumbled upon this problem by chance when I realized I could not start the webmail client.
It turned out
docker-mailserver_webwas unhealthy. Remedy was to stop and restart the service.In order to monitor this, I installed a cron job to be run every 5 minutes to check all mailserver jobs for healthy-ness; restart them if unhealthy and notify via email.
After a few days it turns out that it is only
docker-mailserver_mdawhich falls into unhealthy-state, but this happens pretty often, several dozen times a day, mostly at least once every hour. As the job runs once per 5 minutes, it also happens that the script is triggered 2 or 3 times in a row, so stopping and starting may not help always.To Reproduce
Steps to reproduce the behavior:
I do not know what
unhealthymeans especially fordocker-mailserver_mdaand how it is triggered.Also I do not know if an unhealthy
docker-mailserver_mdahas any bad consequences like an unhealthydocker-mailserver_webhas.Expected behavior
A clear and concise description of what you expected to happen.
Once healthy, a container should stay healthy.
Screenshots
If applicable, add screenshots to help explain your problem.
Docker environment (please complete the following information):
docker infomail 20:03:51 :~# docker info
Client:
Context: default
Debug Mode: false
Plugins:
app: Docker App (Docker Inc., v0.9.1-beta3)
buildx: Build with BuildKit (Docker Inc., v0.5.1-docker)
scan: Docker Scan (Docker Inc.)
Server:
Containers: 24
Running: 24
Paused: 0
Stopped: 0
Images: 109
Server Version: 20.10.6
Storage Driver: overlay2
Backing Filesystem: xfs
Supports d_type: true
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: active
NodeID: ipd46l0g26uldgf5lzoca2dkz
Is Manager: true
ClusterID: m7r3cr8atcih1i8gqcind6f4m
Managers: 1
Nodes: 1
Default Address Pool: 10.0.0.0/8
SubnetSize: 24
Data Path Port: 4789
Orchestration:
Task History Retention Limit: 5
Raft:
Snapshot Interval: 10000
Number of Old Snapshots to Retain: 0
Heartbeat Tick: 1
Election Tick: 10
Dispatcher:
Heartbeat Period: 5 seconds
CA Configuration:
Expiry Duration: 3 months
Force Rotate: 0
Autolock Managers: false
Root Rotation In Progress: false
Node Address: 217.160.241.84
Manager Addresses:
217.160.241.84:2377
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 05f951a3781f4f2c1911b05e61c160e9c30eaa8e
runc version: 12644e614e25b05da6fd08a38ffa0cfe1903fdec
init version: de40ad0
Security Options:
seccomp
Profile: default
Kernel Version: 4.18.0-240.22.1.el8_3.x86_64
Operating System: CentOS Linux 8
OSType: linux
Architecture: x86_64
CPUs: 4
Total Memory: 7.562GiB
Name: mail
ID: WOR3:ER2I:UNFU:R3IN:TVMJ:A5RJ:DEFC:J7UQ:KFJK:CFYX:KGEK:K4QF
Docker Root Dir: /var/lib/docker
Debug Mode: false
Username: kklepper
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
docker-compose versionmail 20:16:08 :~# docker-compose version
docker-compose version 1.29.2, build 5becea4c
docker-py version: 5.0.0
CPython version: 3.7.10
OpenSSL version: OpenSSL 1.1.0l 10 Sep 2019
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: