sharelatex instead of overleaf in path names.Running Overleaf with an NFS filesystem
Running Overleaf with an NFS filesystem
docker-compose based setups, we suggest just overriding the bind-mount from NFS, which avoids changing paths in the application. Here’s an example of a docker-compose config excerpt with the use of a scratch disk that is mounted at /scratch:Running Overleaf on Windows or macOS results in the mongo service not starting
Running Overleaf on Windows or macOS results in the mongo service not starting
mongo service may fail to restart, with an error:config/docker-compose.override.yml, merging with any existing configuration:Upgrading to Redis 6.2 results in a restart loop
Upgrading to Redis 6.2 results in a restart loop
docker logs redis command to output a copy of the logs.If you see the line Fatal: Can't initialize Background Jobs, the full output will look something like this:Incorrect orientation of template gallery preview/thumbnail images
Incorrect orientation of template gallery preview/thumbnail images
/var/lib/overleaf/data/template_files/.We recommend backing up this folder before making any changes.You’ll need to follow the steps below for each affected template:Find the template IDNavigate to your instance’s template gallery (/templates/all), open an affected template, and copy the ID from the URL (for example: https://your-instance-url/templates/6645d346c224815e9460a695).Run the correction commandRun the following command from the Docker host (replace the template ID with the one you copied and update the path if appropriate):docker exec sharelatex /bin/bash -c “mogrify -rotate 90 /var/lib/overleaf/data/template_files/6645d346c224815e9460a695_*{thumbnail,preview}”Reference: https://docs.overleaf.com/on-premises/support/troubleshooting#incorrect-orientation-of-template-gallery-preview-thumbnail-imagesPlease verify that you have enabled system calls. For pdflatex, this is 'pdflatex -shell-escape'.
Please verify that you have enabled system calls. For pdflatex, this is 'pdflatex -shell-escape'.
\write18 command is disabled by default in the Community Edition due to all compiles happening within the same sharelatex container; this is the safer default.If you wish to enable it for pdflatex, create a latexmkrc file in the root of your project with the following content:bin/up fails with unable to upgrade to tcp, received 409 or OCI runtime exec failed after "Initiating Mongo replica set..."
bin/up fails with unable to upgrade to tcp, received 409 or OCI runtime exec failed after "Initiating Mongo replica set..."
mongo container keeps crashing and restarting. bin/up starts MongoDB and then runs a command inside it, which fails while the container restarts. bin/docker-compose ps shows the mongo service as Restarting.To find the actual cause, read the MongoDB log:- The CPU has no AVX support. MongoDB 5.0 and later need AVX on x86-64, and the log shows
MongoDB 5.0+ requires a CPU with AVX support. In a virtual machine, set the CPU type tohostso that AVX is passed through. - Linux kernel 6.19 to 7.0.13. MongoDB refuses to start on these kernels. See Software requirements for the workaround.
- The data was created by an older MongoDB version. MongoDB 8.0 cannot open data from 4.4 or 5.0 directly. Upgrade one major version at a time, see Updating MongoDB.
The log shows "Running Overleaf Community Edition, skipping TexLive checks"
The log shows "Running Overleaf Community Edition, skipping TexLive checks"
OVERLEAF_IS_SERVER_PRO is not true, which is the case in the Ayakaleaf Pro image. Ayakaleaf Pro does not need this variable, so leave it unset.The container stops at 910_initiate_doc_version_recovery or exits with code 2
The container stops at 910_initiate_doc_version_recovery or exits with code 2
*** Running /etc/my_init.d/<script>.... 910_initiate_doc_version_recovery only has work to do on instances that once ran Overleaf 5.0.1. On any other instance it prints No recovery of doc versions needed. and the start continues. Its output also goes to data/history/doc-version-recovery.log in OVERLEAF_DATA_PATH.The exit code and the end of bin/docker-compose logs --tail=100 sharelatex tell what happened:- Exit code 2, and the log ends with
*** Init system aborted.: the container was stopped, for example bybin/stop,docker stopor Ctrl+C onbin/up. The script in the lastRunningline is only the one that was running at that moment, it did not fail. Start the container again withbin/up -dand let the start finish. - Exit code 1, and the log shows
*** /etc/my_init.d/<script> failed with status <n>: that script failed, and its error is in the lines just above. If910_initiate_doc_version_recoveryfailed withDetected unflushed changes while recovering doc versions, the instance ran 5.0.1 and still has unflushed edits; follow the official Doc version recovery guide.
"Restricted, sorry you don’t have permission to load this page"
"Restricted, sorry you don’t have permission to load this page"
create-user --admin command, see User management. In the development environment (develop/), admin pages also need ADMIN_PRIVILEGE_AVAILABLE=true in develop/dev.env; the Ayakaleaf Pro image already sets it.
