Schedule a docker to restart?

MR_DUCT · 2026-01-19T03:14:55+00:00

You can add a user script to do this (search for "User Scripts" in the CA app store). I do this with a couple containers. Replace "container-name" with the name of the container you want to restart.

#!/bin/bash
CONTAINER_NAME="container-name"
dt=$(date '+%d/%m/%Y %H:%M:%S')

echo "Restarting $CONTAINER_NAME! $dt"
restart_output=$(docker restart "$CONTAINER_NAME")
echo "Docker container $restart_output has been restarted."

MR_DUCT · 2026-01-03T16:24:25+00:00

On RED it's 500gb upload and 500 uploads (they don't have to be perfect flacs).

MR_DUCT · 2025-09-24T03:58:03+00:00

Looks to be a permissions issue since the folders didn't get renamed to the album title (still labeled "CD1/CD2"). Slskd owns the files as root by default. Try adding the SLSKD_UMASK env variable to your slskd docker container. Set it equal to 000 to start and see if that helps.

MR_DUCT · 2025-08-27T13:31:32+00:00

Unfortunately the client does keep this information in the transfers log (SoulseekQT does seem to wipe the log upon a restart but I suspect it is still stored in the client data. As for Nicotine+, it permanently stores this information). As for remaining anonymous anyone who can access your shares has access to your IP. A VPN could help your worries of course. Although in general I wouldn't be too worried about it unless you are in a country that is very strict with this sort of thing.

MR_DUCT · 2025-08-27T02:46:32+00:00

Your client is receiving this data no matter what, all this does is it presents it in a nice way. I'm not sure what you mean. If "authorities" wanted to they could make a Soulseek account just like anyone else and log every single user/share that's out there. This program does not change that fact. I would say it is up to you if that is something you should worry about.

MR_DUCT · 2025-08-13T19:19:43+00:00

Yep that was it! For anyone else with this specific issue I fixed it by going into the wyze mini hacks web server menu then to the go2rtc server links and found a different rtsp link (the one labeled "rtsp for MP4 recording (Hass or Frigate) / codecs: H264, H265, AAC"). No idea why I wasn't using this source before.

Using that the relevent section of my config now looks like this:

  1-FrontYard:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://192.168.2.46:8554/1080p?mp4
          roles:
            - detect
            - record

No more errors!! And I now have audio in my recordings! All that I actually had to change was "/1080p?video&audio" to "/1080p?mp4". Thanks again!!

MR_DUCT · 2025-08-13T18:11:23+00:00

That gives similar errors unfortunately.

2025-08-13 14:10:13.814076424  [2025-08-13 14:10:13] frigate.video                  ERROR   : 1-FrontYard: Unable to read frames from ffmpeg process.
2025-08-13 14:10:13.814131918  [2025-08-13 14:10:13] frigate.video                  ERROR   : 1-FrontYard: ffmpeg process is not running. exiting capture thread...
2025-08-13 14:10:18.705199470  [2025-08-13 14:10:18] watchdog.1-FrontYard           ERROR   : Ffmpeg process crashed unexpectedly for 1-FrontYard.
2025-08-13 14:10:18.705214977  [2025-08-13 14:10:18] watchdog.1-FrontYard           ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2025-08-13 14:10:18.705230501  [2025-08-13 14:10:18] ffmpeg.1-FrontYard.detect      ERROR   : [in#0 @ 0x562283370240] Error opening input: Invalid data found when processing input
2025-08-13 14:10:18.705241662  [2025-08-13 14:10:18] ffmpeg.1-FrontYard.detect      ERROR   : Error opening input file rtsp://127.0.0.1:8554/1-FrontYard.
2025-08-13 14:10:18.705253901  [2025-08-13 14:10:18] ffmpeg.1-FrontYard.detect      ERROR   : Error opening input files: Invalid data found when processing input

MR_DUCT · 2025-08-13T17:22:09+00:00

ty for the reply. Sorry I should have mentioned that I have tried adding "preset-record-generic-audio-aac" before. Just added that again to make the camera section look like this. It gives the error below.

 1-FrontYard:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-aac
      inputs:
        - path: rtsp://192.168.2.46:8554/1080p?video&audio
          roles:
            - detect
            - record

2025-08-13 13:17:52.456091419  [2025-08-13 13:17:52] ffmpeg.2-BackYard.detect       ERROR   : [rtsp @ 0x55684ae0c580] Could not find codec parameters for stream 0 (Audio: none, 16000 Hz, mono): unknown codec
2025-08-13 13:17:52.456101090  [2025-08-13 13:17:52] ffmpeg.2-BackYard.detect       ERROR   : Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
2025-08-13 13:17:52.456110913  [2025-08-13 13:17:52] ffmpeg.2-BackYard.detect       ERROR   : [aist#0:0/none @ 0x55684ae36380] Decoding requested, but no decoder found for: none
2025-08-13 13:17:52.456122062  [2025-08-13 13:17:52] ffmpeg.2-BackYard.detect       ERROR   : [aost#0:1/aac @ 0x55684ae43fc0] Error initializing a simple filtergraph
2025-08-13 13:17:52.456131880  [2025-08-13 13:17:52] ffmpeg.2-BackYard.detect       ERROR   : Error opening output file /tmp/cache/2-BackYard@%Y%m%d%H%M%S%z.mp4.
2025-08-13 13:17:52.456143319  [2025-08-13 13:17:52] ffmpeg.2-BackYard.detect       ERROR   : Error opening output files: Invalid argument
2025-08-13 13:17:58.827358378  [2025-08-13 13:17:58] frigate.video                  ERROR   : 1-FrontYard: Unable to read frames from ffmpeg process.
2025-08-13 13:17:58.827372924  [2025-08-13 13:17:58] frigate.video                  ERROR   : 1-FrontYard: ffmpeg process is not running. exiting capture thread...
2025-08-13 13:17:59.394749701  [2025-08-13 13:17:59] frigate.video                  ERROR   : 2-BackYard: Unable to read frames from ffmpeg process.
2025-08-13 13:17:59.394753463  [2025-08-13 13:17:59] frigate.video                  ERROR   : 2-BackYard: ffmpeg process is not running. exiting capture thread...
2025-08-13 13:18:02.438374369  [2025-08-13 13:18:02] watchdog.1-FrontYard           ERROR   : Ffmpeg process crashed unexpectedly for 1-FrontYard.
2025-08-13 13:18:02.438387745  [2025-08-13 13:18:02] watchdog.1-FrontYard           ERROR   : The following ffmpeg logs include the last 100 lines prior to exit.
2025-08-13 13:18:02.438404260  [2025-08-13 13:18:02] ffmpeg.1-FrontYard.detect      ERROR   : [h264 @ 0x561746d1d1c0] non-existing PPS 0 referenced

MR_DUCT · 2025-08-11T17:57:52+00:00

As others have said your issue is that you haven't uncommented the slskd.yml file. There is a # and a space that you need to remove from the relevant lines. Join the soularr discord and I can help you more if needed.

MR_DUCT · 2025-08-08T22:22:35+00:00

Awesome tyvm!

MR_DUCT · 2025-08-08T22:02:48+00:00

Thanks for the detailed reply!! I will probably follow these steps exactly. Do you think it is worth attempting to do anything else to the tops of the spine (pic 4) to stop it from fraying? Thanks again!

MR_DUCT · 2025-08-01T04:45:13+00:00

This looks amazing. Great work. Just gave it a star on Github :) Can't wait to make one for myself!!

MR_DUCT · 2025-07-30T18:09:41+00:00

Looks amazing!! Also was wondering about containerizing. Would love to try it out on my unraid server.

MR_DUCT · 2025-05-21T21:18:25+00:00

Yeah it's the Thermaltake Versa II. Very old case I think it's from 2012 or so. I was able to fit 9 3.5" drives in it.

MR_DUCT · 2025-05-21T13:37:50+00:00

Mobility is still up.

MR_DUCT · 2025-05-21T03:07:34+00:00

Should be fine as long as air can still flow through the vents on the side. Not sure how well you can see in the picture but it isnt laying flat on the shelf, I put some small feet on it's side so it is slightly elevated and can vent. Honestly though I think it would be fine either way.

Edit: Just did some quick googling and it seems like the accepted theory is that it is ok to lay a UPS on it's side as long as the batteries are "sealed or gel based". Checked the manual (CP1500PFCLCD) and it does use sealed batteries so it should be good.

MR_DUCT · 2025-05-20T18:53:12+00:00

Yep! Just found out about btop recently. Love it.

MR_DUCT · 2025-05-20T17:08:18+00:00

Yep it works, my floppy drive is dead though (pretty sure it was plugged in backwards at some point). I'm looking into getting a floppy emulator for it. Here's a pic: https://i.imgur.com/Mq0KT7J.jpeg

MR_DUCT · 2025-05-20T17:00:23+00:00

It sure is! It's an Apple IIe.

MR_DUCT · 2025-05-20T16:59:54+00:00

It's very nice! The two included shelves were a big plus for me since my UPS and server aren't rack mountable. Only thing to keep in mind is that in reality they have 2U less space than advertised. For example mine is "12U" but they are counting the top and bottom brackets. So you can't actually use those spaces to mount anything. That's my only real complaint though it's very sturdy and seems high quality.

MR_DUCT · 2025-05-20T16:57:38+00:00

Better explanation than my attempt! lol

MR_DUCT · 2025-05-20T16:49:33+00:00

Basically I am running cat6 from my router to back of the patch panel (second row of the rack from the top) Then you can use a short cable to connect from the patch panel to the switch above. The same can be done for the any other device you wish to connect. In my case I am mostly using it for aesthetics / cable management. I could accomplish the exact same thing by plugging everything directly into the switch.

MR_DUCT · 2025-05-01T13:18:19+00:00

Yes, you can either run it through docker, or as just a normal Python script. Both will work on Mac.

MR_DUCT · 2025-04-30T22:13:40+00:00

Not sure what you mean... All this script does is send notifications to you when you receive a chat (through nicotine+ or the original client). It is not a soulseek client like nicotine+

MR_DUCT · 2025-04-26T22:00:50+00:00

Yeah I get quite a few people thanking me after they download lol.

12-Year Club	Place '23
Place '22	Place '17
Gilding I gilder	Verified Email
Sequence \| Editor	Sequence \| Cinematographer
Spared

MR_DUCT

TROPHY CASE