starred/ProxmoxVE

Fork 0

mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-04-25 17:26:03 +03:00

[GH-ISSUE #3721] paperless-gpt: Add log file to service definition #771

New issue

Closed

opened 2026-02-26 12:46:36 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 12:46:36 +03:00

Owner

Originally created by @taker218 on GitHub (Apr 7, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/3721

🌟 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). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/3721 ### 🌟 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.

kerem

2026-02-26 12:46:36 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-26 12:46:36 +03:00

Author

Owner

@tremor021 commented on GitHub (Apr 7, 2025):

Makes sense, we will add it to the script.

Thank you for your feedback

@tremor021 commented on GitHub (Apr 7, 2025): Makes sense, we will add it to the script. Thank you for your feedback

kerem referenced this issue

2026-02-26 13:31:37 +03:00

[PR #771] [CLOSED] Fix Alpine Vaultwarden Install Script #2868

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ProxmoxVE#771

No description provided.

Rows
Columns