-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker Plex Service Kill Command Update (LinuxServer.io) #172
Comments
Cool. Thank you for letting me know. I'll update right away. Expect an update (Aug 28/29) |
I've never been able to get the script to stop plex correctly (in a linuxserver.io docker on unraid) and the command seems to change every time I need to run it. Rest of the script is awesome and I've used it multiple times so hopefully this fixes it and the command stops changing. And reading the install instructions I think I have the files in the wrong spot. They are supposed to be next to /config and mine are in there. Hopefully that is my main issue. |
|
I just created a new LSIO plex container. This is what I see:
Given you state /run versus /var/run, I have no problem adding support for that variant. Can you confirm?
|
The full sequence:
|
I've updated the general path testing to look at both older and newer (?) path -- which I can't yet confirm in my own new container. Please test the DBRepair.sh from this branch https://github.com/ChuckPa/PlexDBRepair/tree/chuckpa/update-linuxserver-svc |
Hey, Testing that branch I get: But adding another |
1, Yes, I forgot to close that with
|
For 2: I am not sure how you would other than maybe try one after the other instead of replacing. It might have something to do with Docker Read-Only Root FS and s6
So maybe that logic. Also in the Docker Container, PID 1 shows
|
@ChuckPa I just wanted to let you know that the current script works with Unraid version 6.12.13 and Linuxserver/docker-plex version 1.41.0.8992-8463ad060-ls235. I downloaded the script via cli directly into the container: docker exec -it plex /bin sh apt-get update apt-get install git -y ##A few moments later....### git clone https://github.com/ChuckPa/PlexDBRepair.git cd "/config/Library/PlexDBRepair" Then launched the script via "./PlexDBRepair.sh" Able to select option #1 to stop PMS Then run / select any other option of my choice including #2 which runs smoothly just takes time because in my instance "com.plexapp.plugins.library.blobs.db" = 975MB & "com.plexapp.plugins.library.db" = 1.08GB in size. Once again, I thank you @ChuckPa and your team for all of your hard work behind the scenes. If you all want any further info or detail please let me know here or via PM. |
Well isn't this problematic 😄 For the life of me, I cannot figure out why these lines, which have worked for a long time now, suddenly fail.
I'm not testing for writeable.
|
I'm glad it helped. I've figured out how to do multiple-level 'undo' commands . It sounds like fun but feels like superfluous fluff. I use this in all my production and testing work at Plex (I use a lot of LXCs) |
I get it. Its been a task for sure but much appreciated. I have used the script on both Synology & Unraid which have both come as life savers thank to the help of yourself and your team. @ChuckPa |
On the current LinuxServer.io Plex Docker container, the service kill command is now
s6-svc -d /run/service/svc-plex
The path has changed and the current script will fail to stop otherwise.
The text was updated successfully, but these errors were encountered: