Troubleshooting

Messages seawall prints when something stops it. Each comes with what to run next.

First checks

seawall doctor      # permissions, access to Docker, sudo, Portainer and Grafana
seawall status      # what needs attention
seawall audit -n 20 # the last changes seawall made

init

MessageDo
is in the docker group, but this login started before thatLog out and back in. Then run seawall init --yes again. Steps already done show ✓.
SEAWALL_PORTAINER_PASSWORD must be 12 characters or moreUse a longer password, or leave the variable unset to type it.
A step failsinit stops at the first failure. Fix what it names and run it again. It carries on from that step.

Deploys and updates

MessageDo
X's disk copy differs from what's deployed: `seawall stack diff X` shows howRun seawall stack diff X. Then end the drift with stack reconcile X --take disk or --take deployed.
X hasn't settled: its health check says …The deploy went through and the container isn't healthy. Read seawall stack logs X. Roll back with stack rollback X --yes.
X hasn't settled: it keeps restartingThe container exits after it starts. Its logs say why.
killed X (it wouldn't stop)The container ignored the stop signal for its grace period. With "Operation not permitted" in the lines it logged, its start script lacks KILL. Run stack harden X.
this change is severe: add --confirm X to make it without a terminalA severe change needs a name typed as well as --yes. The plan says which. On a terminal you type it. In a script pass --confirm X.
the disk copy wasn't updatedThe run was interrupted after Portainer took over. Run the stack reconcile it names.
X builds app (build:). Portainer can't build from its copy.Run the stack with Compose. Add X = "compose" under [manager.stacks]. If it runs already, move it with stack migrate X --to compose.
Portainer has a stack X and X's containers also run from …Portainer and a folder both run the stack. Choose one and remove the other by hand.
X is partly up (some containers exist). Deploy with --start.An earlier deploy stopped halfway. Deploy it running with --start.
X would publish ports already in useAnother container or process holds a host port the stack publishes. Stop it first. game up moves a game to the next free port instead.

Reports

MessageDo
no Loki data source in GrafanaGrafana has no Loki data source. Add one in Grafana.
no answer from LokiGrafana answered and its Loki query failed. Check the Loki container.
no answer from GrafanaGrafana is down or its login changed. Check its container with seawall stack ls.
couldn't read the containersA Docker call failed. Run docker ps as your user.
couldn't read the stack listPortainer didn't answer. Check its container and its token with seawall doctor.
no factsThe facts timer hasn't run. Check systemctl status seawall-facts.timer.
the update check hasn't runRun seawall images check or wait for its 06:00 UTC timer.
no config repoSet paths.config_repo.