You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After doing a down and up or just a restart of "mailserver2/mailserver" container, the container running into the issue that s6 service does not start properly.
mailserver-1 | s6-svc: fatal: unable to control /services/rsyslogd: supervisor not listening
mailserver-1 | s6-svc: fatal: unable to control /services/unbound: supervisor not listening
mailserver-1 | s6-svwait: fatal: unable to s6_svstatus_read: No such file or directory
It seems that only a restart of the host system ensures that the container can start normally again without errors. We also tried to restart the docker service, but this seems not to be working properly.
Steps to reproduce
docker compose down && docker compose up
docker restart docker-mailserver-1
Expected results
All services starting without issues
Actual results
S6 running into issues on startup
mailserver-1 | s6-svc: fatal: unable to control /services/rsyslogd: supervisor not listening
mailserver-1 | s6-svc: fatal: unable to control /services/unbound: supervisor not listening
mailserver-1 | s6-svwait: fatal: unable to s6_svstatus_read: No such file or directory
Debugging information
#docker compose logs mailserver -f
mailserver-1 | [INFO] MariaDB/PostgreSQL hostname not found in /etc/hosts
mailserver-1 | [INFO] Container IP found, adding a new record in /etc/hosts
mailserver-1 | [INFO] Redis hostname not found in /etc/hosts
mailserver-1 | [INFO] Container IP found, adding a new record in /etc/hosts
mailserver-1 | [INFO] Search for SSL certificates generated by Traefik
mailserver-1 | [INFO] acme.json found with Traefik v2 format, dumping into pem files
mailserver-1 | [INFO] Live Certificates match
mailserver-1 | [INFO] Starting services
mailserver-1 | s6-svc: fatal: unable to control /services/rsyslogd: supervisor not listening
mailserver-1 | s6-svc: fatal: unable to control /services/unbound: supervisor not listening
mailserver-1 | s6-svwait: fatal: some services reported permanent failure or their supervisor died
Interestingly enough, I sometimes get the same error message when starting the docker container, version 1.1.18: unable to control /services/rsyslogd: supervisor not listening
Accessing a shell within the container - after startup finished - and starting the rsyslog service then succeeds.
Classification
Reproducibility
Docker information
Description
After doing a down and up or just a restart of "mailserver2/mailserver" container, the container running into the issue that s6 service does not start properly.
It seems that only a restart of the host system ensures that the container can start normally again without errors. We also tried to restart the docker service, but this seems not to be working properly.
Steps to reproduce
docker compose down && docker compose up
docker restart docker-mailserver-1
Expected results
All services starting without issues
Actual results
S6 running into issues on startup
Debugging information
Configuration (docker-compose.yml, traefik.toml...etc)
The text was updated successfully, but these errors were encountered: