#Docker container PlexMetaManager stopped unexpectedly

1 messages · Page 1 of 1 (latest)

acoustic stag
#

Hello everyone. PMM and (kinda) Docker noob here so please be patient with me. I know enough to get myself into trouble but I went down the rabbit hole yesterday... 🤷‍♂️ . I'm running PLEX on a Synology NAS and it's been working perfectly for a long time. I installed PMM on my NAS via Docker yesterday and after some substantial troubleshooting got it to run (without any errors as far as I know). The problem I'm having is that as soon as it's finished its 'run' the Docker container just stops running and I get a "Docker container PlexMetaManager stopped unexpectedly". I can't figure it out for the life of me. Any assistance would be greatly appreciated.

rain saffronBOT
#

Please complete #938455615741775902 and someone from the community or one of our <@&938443185347244033> members will respond when they're available.

Including the meta.log from the beginning is a huge help use !logs for more information.

shy prism
#

How are you running it? docker run? compose? something else?

acoustic stag
#

I installed it through Docker via my Synology NAS. Downloaded the latest image from there.

shy prism
#

OK, I can't see your screen so you're going to have to provide more details.

What's the configuration look like?

There's a runtime flag or an ENV var that will make it behave like this; it will run immediately when you start the container then exit.

#

PMM_RUN

acoustic stag
#

That's probably it. I added that.

shy prism
#

If that's true the container will behave like this.

acoustic stag
#

I need to force run it. It's the only way I could get it to do it.

shy prism
#

If you remove PMM_RUN and start the container, it will wait until 5AM, then do its thing, then wait until the next 5AM, rinse, repeat.

acoustic stag
#

Thanks but...

#

How do I get it to run manually?

shy prism
#
  1. Create a second container with PMM_RUN set. Start that one when you want to do an immediate run.
#
  1. exec into the container and run the python script manually.
#
  1. Use docker run
#

[those are alternatives, not steps]

#

If you want it to RUN RIGHT NOW when the container starts and then when it finishes wait until tomorrow at 5AM, you can't do that [easily] with a single container.

#

For the most part these two modes: "run right now" vs. "wait until the scheduled time" are mutually exclusive.

acoustic stag
#

I tried 2 (I think) through the the Docker Terminal with the --run command but it didn't work. Are you able to provide some specifics details on 1 or 2 as I'm not really clear on either?

shy prism
#

for 1, you have one container already, leave that one alone. When you want to run PMM right this second, start that container; PMM will run and the container will quit when it's finished.

Create a second container just like the one you have with all the same parameters and config details EXCEPT leave PMM_RUN out. When you start that container it will run in the background and wake up every day at 5AM.

#

for 3, you'd run something like:

docker run --rm -ti -v /opt/pmm/config:/config meisnate12/plex-meta-manager:nightly -c /config/test-config.yml --run

on your NAS [of course, change those config details as appropriate]

Wait that was 3

acoustic stag
#

Ahhhh... Duplicate containers with the one parameter being removed, yes?

shy prism
#

For #2, you'd open a shell into the container however Synology does that and run python plex_meta_manager.py --run

acoustic stag
#

Thank you very much sir!

shy prism
#

You could create however many duplicate containers with different settings to do various things [just overlays, only collections, etc]. Start/stop as desired.

acoustic stag
#

Right, right! One day at a time! LOL

#

Thanks so much! I appreciate your time and assistance.