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 14 Packages Projects Releases 10 Wiki Activity

Slskd fails to start due to YAML config misconfiguration #998

New Issue
Closed
opened 2026-02-04 22:27:44 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-04 22:27:44 +03:00
Owner
Copy Link

Originally created by @shunakiyama on GitHub (May 22, 2025).

✅ Have you read and understood the above guidelines?

yes

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

slskd

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

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/slskd.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.

While using the slskd LXC container script the slskd service will fail to start as it cannot find the picture described in the soulseek yaml segment:

soulseek:
   address: vps.slsknet.org
   port: 2271
   username: ~
   password: ~
   description: |
     A slskd user. https://github.com/slskd/slskd
   picture: path/to/slsk-profile-picture.jpg

Default picture is not provided with the container making it fail while at starting the service. Commenting out the picture parameter will circumvent the issue.

I recomend not setting this by default and let the user change it.

🔄 Steps to reproduce the issue.

  1. Install the LXC container with provided bash script
  2. Start the container
  3. The slskd service will fail to start here and while running sudo systemctl restart slskd

❌ Paste the full error output (if available).

May 12 19:33:39 slskd slskd[136]: Invalid configuration:
May 12 19:33:39 slskd slskd[136]:   Soulseek:
May 12 19:33:39 slskd slskd[136]:     The Picture field specifies a non-existent file '/opt/slskd/path/to/slsk-profile-picture.jpg'.
May 12 19:33:39 slskd systemd[1]: slskd.service: Deactivated successfully.
May 12 19:33:39 slskd systemd[1]: slskd.service: Scheduled restart job, restart counter is at 1.

🖼️ Additional context (optional).

No response

Originally created by @shunakiyama on GitHub (May 22, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? slskd ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/slskd.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. While using the slskd LXC container script the slskd service will fail to start as it cannot find the picture described in the `soulseek` yaml segment: ``` soulseek: address: vps.slsknet.org port: 2271 username: ~ password: ~ description: | A slskd user. https://github.com/slskd/slskd picture: path/to/slsk-profile-picture.jpg ``` Default picture is not provided with the container making it fail while at starting the service. Commenting out the `picture` parameter will circumvent the issue. I recomend not setting this by default and let the user change it. ### 🔄 Steps to reproduce the issue. 1. Install the LXC container with provided bash script 2. Start the container 3. The slskd service will fail to start here and while running `sudo systemctl restart slskd` ### ❌ Paste the full error output (if available). ``` May 12 19:33:39 slskd slskd[136]: Invalid configuration: May 12 19:33:39 slskd slskd[136]: Soulseek: May 12 19:33:39 slskd slskd[136]: The Picture field specifies a non-existent file '/opt/slskd/path/to/slsk-profile-picture.jpg'. May 12 19:33:39 slskd systemd[1]: slskd.service: Deactivated successfully. May 12 19:33:39 slskd systemd[1]: slskd.service: Scheduled restart job, restart counter is at 1. ``` ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bug label 2026-02-04 22:27:44 +03:00
OVERLORD commented 2026-02-04 22:28:03 +03:00
Author
Owner
Copy Link

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

@vhsdream

@MickLesk commented on GitHub (May 22, 2025): @vhsdream
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 bug
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#998
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?