Basic Max Troubleshooting

Logged in user: max
Base directory: /opt/answerrocket
View running Docker containers: docker ps

Restarting Docker

To restart the containers:

./scripts/prod-compose.sh restart

To fully bring the containers down and back up (some config changes and issues require this rather than a restart):

./scripts/prod-compose.sh down
./scripts/prod-compose.sh up -d

The -d flag stands for "detached." It brings up the containers without your terminal session being attached to them.

Investigating Issues

1. Check container health

Start by viewing all running Docker containers to see if any are unhealthy:

docker ps

Six containers are required for Max to run as expected:

nginx
webhost
rocketfleet
maxappserver
rabbit
mongodb

Additional containers can be running without causing issues.

2. Check Docker logs

For any unhealthy container, check its logs:

docker logs [container]

Replace [container] with the name of the container you are investigating, such as ar-webhost-1.

To cut down on clutter, use these flags:

-f follows the logs live
--tail [number] shows only the last X lines

Example:

docker logs -f --tail 50 ar-webhost-1

Tip: You may still want to check the logs for healthy containers. Occasionally the logs contain relevant errors even when the container reports as healthy.

3. Check application logs

Application logs live in volumes/logs. The most relevant files are:

MaxAppServer.log
max_log-[date].txt for the date you are investigating

The archive/ directory inside logs/ contains dated MaxAppServer log files for previous dates.