SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

paperless-gpt: Add log file to service definition #870

New Issue
Open
opened 2025-11-20 04:55:30 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 04:55:30 -05:00
Owner
Copy Link

Originally created by @taker218 on GitHub (Apr 7, 2025).

🌟 Briefly describe the feature

Add a log file for the paperless-gpt container

📝 Detailed description

I just had a problem with my paperless-gpt running via the script and wanted to have a look at the logs.
I haven't found any log in the container and found a workaround in the paperless-gpt repo issues.

The workaround is:
journalctl -u paperless-gpt -f

But having a dedicated log file would be a lot easier in most instances.

For my case I added the following two lines to my paperless-gpt.service file:

StandardOutput=append:/var/log/paperless-gpt.log
StandardError=append:/var/log/paperless-gpt.log

This appends the log to the file.
To always create a new file when the container or service is started you could use the following.

StandardOutput=file:/var/log/paperless-gpt.log
StandardError=file:/var/log/paperless-gpt.log

Both versions are working just fine, I think the first one with appending the log, should be the standard here.

💡 Why is this useful?

I found some issues in the paperless-gpt repo of people wondering where the logs are stored, when running the lxc-container. Since paperless-gpt is designed to run as a docker container, the log output is going to STDOUT/STDERROR.
Having dedicated log files for it would make looking for the logs a lot easier.

Originally created by @taker218 on GitHub (Apr 7, 2025). ### 🌟 Briefly describe the feature Add a log file for the paperless-gpt container ### 📝 Detailed description I just had a problem with my paperless-gpt running via the script and wanted to have a look at the logs. I haven't found any log in the container and found a workaround in the paperless-gpt repo issues. The workaround is: `journalctl -u paperless-gpt -f` But having a dedicated log file would be a lot easier in most instances. For my case I added the following two lines to my paperless-gpt.service file: ``` StandardOutput=append:/var/log/paperless-gpt.log StandardError=append:/var/log/paperless-gpt.log ``` This appends the log to the file. To always create a new file when the container or service is started you could use the following. ``` StandardOutput=file:/var/log/paperless-gpt.log StandardError=file:/var/log/paperless-gpt.log ``` Both versions are working just fine, I think the first one with appending the log, should be the standard here. ### 💡 Why is this useful? I found some issues in the paperless-gpt repo of people wondering where the logs are stored, when running the lxc-container. Since paperless-gpt is designed to run as a docker container, the log output is going to STDOUT/STDERROR. Having dedicated log files for it would make looking for the logs a lot easier.
saavagebueno added the enhancement label 2025-11-20 04:55:30 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#870
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?