You can use the bin/logs script to view logs for the services.Basic usage examples:
# View the web service logsbin/logs web# Show helpbin/logs --help# View logs for multiple services at oncebin/logs filestore docstore web clsi# Follow log output (like tail -f)bin/logs -f filestore docstore web clsi# Limit the number of lines printed (default 20)bin/logs -n 50 web# Show all log linesbin/logs -n all web# Redirect output to a filebin/logs -n all web > web.log# Last 100 lines of the MongoDB log, and only the lines with errorsbin/logs -n 100 mongobin/logs -n all mongo | grep -i -E 'error|fatal'
You can use the bin/logs script to view logs for the following services: clsi, contacts, docstore, document-updater, filestore, git-bridge, mongo, notifications, real-time, redis, spelling, tags, track-changes, web, web-api, history-v1, project-history.
Docker containers are ephemeral, which means files/directories created inside the container during runtime (including log files) will be discarded if the container is recreated (for example, when running bin/up). To retain log files between container recreations:
Set the environment variable OVERLEAF_LOG_PATH in the config/overleaf.rc file used by the Toolkit. This should be the directory on the host that will be bind-mounted to the log directory inside the sharelatex container.
After changing this and running bin/up -d, log files will be persisted on the host and accessible directly.
You must set the owner of the host logs directory used for the bind-mount to the www-data user (uid=33) and ensure permissions are drwxr-xr-x (755).Example: