starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 12 Packages Projects Releases 10 Wiki Activity

Systemd swallowing Copyparty logs #1505

New Issue
Closed
opened 2026-02-05 01:22:33 +03:00 by OVERLORD · 5 comments
OVERLORD commented 2026-02-05 01:22:33 +03:00
Owner
Copy Link

Originally created by @scallaway on GitHub (Aug 21, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Copyparty

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/addon/copyparty.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📝 Provide a clear and concise description of the issue.

When running the service, all the logs are swallowed so you don't get any indexing progress updates etc. and this also makes it impossible to get password hashing working.

🔄 Steps to reproduce the issue.

Start the service, look at the logs for the service.

❌ Paste the full error output (if available).

N/A

🖼️ Additional context (optional).

No response

Originally created by @scallaway on GitHub (Aug 21, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Copyparty ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/tools/addon/copyparty.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. When running the service, all the logs are swallowed so you don't get any indexing progress updates etc. and this also makes it impossible to get password hashing working. ### 🔄 Steps to reproduce the issue. Start the service, look at the logs for the service. ### ❌ Paste the full error output (if available). N/A ### 🖼️ Additional context (optional). _No response_
OVERLORD added the not a script issuequestion labels 2026-02-05 01:22:33 +03:00
OVERLORD commented 2026-02-05 01:22:44 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 21, 2025):

what do you mean swallowing?

Image

I can see logs just fine

@tremor021 commented on GitHub (Aug 21, 2025): what do you mean swallowing? <img width="801" height="201" alt="Image" src="https://github.com/user-attachments/assets/fab1a840-30df-4be3-8fa2-170de3b55a4b" /> I can see logs just fine
OVERLORD commented 2026-02-05 01:22:49 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 21, 2025):

idk what you mean, log work fine here.

@MickLesk commented on GitHub (Aug 21, 2025): idk what you mean, log work fine here.
OVERLORD commented 2026-02-05 01:22:52 +03:00
Author
Owner
Copy Link

@scallaway commented on GitHub (Aug 22, 2025):

Not sure why this was closed when I didn't even have a chance to respond to the comments?

I can see logs just fine

That's based on your copyparty config and is the output file.

I'm talking about the logs being shown in journalctl -u copyparty since the script installs this as a systemctl service.

It's very common for me to check the status of the logs for a service with systemctl status {service} as I find that quicker than diving into the full log file of the service.

@scallaway commented on GitHub (Aug 22, 2025): Not sure why this was closed when I didn't even have a chance to respond to the comments? > I can see logs just fine That's based on your copyparty config and is the output file. I'm talking about the logs being shown in `journalctl -u copyparty` since the script installs this as a `systemctl` service. It's very common for me to check the status of the logs for a service with `systemctl status {service}` as I find that quicker than diving into the full log file of the service.
OVERLORD commented 2026-02-05 01:22:56 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 22, 2025):

When I tested various uploads and moves, this would have massively inflated the journal, so there are static log paths. These are also easier to search through.

@MickLesk commented on GitHub (Aug 22, 2025): When I tested various uploads and moves, this would have massively inflated the journal, so there are static log paths. These are also easier to search through.
OVERLORD commented 2026-02-05 01:22:59 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Aug 22, 2025):

Not sure why this was closed when I didn't even have a chance to respond to the comments?

I can see logs just fine

That's based on your copyparty config and is the output file.

I'm talking about the logs being shown in journalctl -u copyparty since the script installs this as a systemctl service.

It's very common for me to check the status of the logs for a service with systemctl status {service} as I find that quicker than diving into the full log file of the service.

Hi, this is not "my" config, its script default configuration. The application logs out to:

/var/log/copyparty/copyparty.log
/var/log/copyparty/copyparty.err

So, everything works as expected and its closed because it works exactly as written in the script.

@tremor021 commented on GitHub (Aug 22, 2025): > Not sure why this was closed when I didn't even have a chance to respond to the comments? > > > I can see logs just fine > > That's based on your copyparty config and is the output file. > > I'm talking about the logs being shown in `journalctl -u copyparty` since the script installs this as a `systemctl` service. > > It's very common for me to check the status of the logs for a service with `systemctl status {service}` as I find that quicker than diving into the full log file of the service. Hi, this is not "my" config, its script default configuration. The application logs out to: ``` /var/log/copyparty/copyparty.log /var/log/copyparty/copyparty.err ``` So, everything works as expected and its closed because it works exactly as written in the script.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
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
🛑 Failure to comply with the guidelines
No Label not a script issue question
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1505
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?