bin/logs Script Fails to Display Logs on Host, Logs Only Accessible Inside Container Description
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start by reading the bin/logs script and compare its log lookup with the /var/log/overleaf files visible after running bin/shell. Reproduce bin/logs web on the host and confirm that it returns the container's web.log contents; the issue is done when host-side log retrieval works, including follow mode.
Written by the indexing model from the issue text.
Description
I am using the Overleaf Toolkit to deploy Overleaf Community Edition (CE) via Docker. When attempting to view logs using the bin/logs script on the host machine (e.g., bin/logs -f web), the output is blank. However, I can find and view the log files (e.g., /var/log/overleaf/web.log) inside the container's shell after executing bin/shell. This indicates that logs are being generated but are not accessible via the bin/logs script as expected.
This issue hinders debugging and monitoring from the host machine, as I must manually enter the container to access logs. I believe this could be a configuration or scripting issue with the Toolkit's log retrieval mechanism.
as6325400@overleaf:~/overleaf-toolkit$ bin/logs web
as6325400@overleaf:~/overleaf-toolkit$ sudo bin/shell
root@60fd7209b119:/overleaf# ls -l /var/log/overleaf
total 220
-rw-r--r-- 1 root root 348 May 29 12:06 chat.log
-rw-r--r-- 1 root root 22994 May 29 12:06 clsi.log
-rw-r--r-- 1 root root 356 May 29 12:06 contacts.log
-rw-r--r-- 1 root root 808 May 29 13:05 cron-deactivate-projects.log
-rw-r--r-- 1 root root 404 May 29 12:20 cron-delete-projects.log
-rw-r--r-- 1 root root 772 May 29 12:15 cron-delete-users.log
-rw-r--r-- 1 root root 2868 May 29 13:00 cron-project-history-periodic-flush.log
-rw-r--r-- 1 root root 3232 May 29 12:06 docstore.log
-rw-r--r-- 1 root root 872 May 29 12:06 document-updater.log
-rw-r--r-- 1 root root 3530 May 29 12:06 filestore.log
-rw-r--r-- 1 root root 3856 May 29 12:06 history-v1.log
-rw-r--r-- 1 root root 1034 May 29 12:06 notifications.log
-rw-r--r-- 1 root root 370 May 29 12:06 project-history.log
-rw-r--r-- 1 root root 782 May 29 12:45 project-history-retry-hard.log
-rw-r--r-- 1 root root 743 May 29 12:30 project-history-retry-soft.log
-rw-r--r-- 1 root root 10829 May 29 12:38 real-time.log
-rw-r--r-- 1 root root 7102 May 29 12:38 web-api.log
-rw-r--r-- 1 root root 121835 May 29 13:01 web.log
root@60fd7209b119:/overleaf#
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 310
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from overleaf/toolkit
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
All issues in overleaf/toolkit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
community-scripts/ProxmoxVE#17425 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
danielmiessler/LifeOS#2218 ·
-
docs(agents): strengthen the no-backslash-escaped-backticks rule with an issue-creation example Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
technical-debt
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
ll7/robot_sf_ll7#9560 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·