#Docker restart unless stopped

1 messages · Page 1 of 1 (latest)

kind plank
#

So im running windows docker and have it setup all ok but when running the

docker run -d
--restart=unless-stopped
-v “C:/Users/Home/plex-meta-manager/config:/config:rw”
meisnate12/plex-meta-manager

It starts up correctly and says it will start at 5am but then it never stops. It keeps going round and round and round in a cycle of the config file and doesnt come up again with starts at 5am.

Any ideas what I might need to change in the code or perhaps I have something wrong. Thanks.

zinc daggerBOT
#

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.

analog mulch
#

please provide the full meta.log

analog mulch
#

also, the restart=unless-stopped has nothing to do with PMM's behaviour itself... it refers to the container itself, meaning if PMM stops running or dies, the container would restart... but if PMM is being shutdown "normally" then the container would stop and stay stopped

#

if your PMM keeps going through a loop and complaining about something, then the issue is with the PMM configuration itself, hence we need to see what it exactly says and does.

honest valley
#
docker run -d \
  --restart=unless-stopped \
  -v “C:/Users/Home/plex-meta-manager/config:/config:rw” \
  meisnate12/plex-meta-manager --run

?

#

by default, PMM runs at 5AM. You have to use the -r or --run flag to tell it "hey, run right now!"

kind plank
kind plank
kind plank
#

Hi. This is the log. Interestingly it says it finished however when you click the container on windows docker it still is going and keeps going... Perhaps it actually has finished but the container is behind or something?

kind plank
#

ok. I've been messing around with things and for some reason I cant get it to display anything in docker when using the below... If i use -r it works as a container. When I run the below its a blank container without the plex-meta-manager will run at 05:00 etc..

docker run -d --restart=unless-stopped -v “C:/Users/Home/plex-meta-manager/config:/config:rw” meisnate12/plex-meta-manager

flint cliff
#

That's normal.

#

That bit of logging [the countdown] doesn't show up in some docker logging contexts.

kind plank
#

oh ok! Thats good to know

#

Im going to run both tv and movie containers and wait to see whats happened tomorrow then. I did try with --time setting 2 minutes later than current to see if it activated or showed anything and nothing came up. Will leave it and see if anything shows tomorrow morning. Thanks!

fluid edge
#

if you set to run at a specific time, it will run at that tim. The container will continue to run, and PMM will start again when it reaches the specified time.

kind plank
#

Yeah. I’m wondering if it won’t run tonight then as it didn’t run when doing a test with setting it for —time 01:00 the container was just blank when clicked on.

fluid edge
#

With a time, it will not run right away.

flint cliff
#

Look at the log file, not the docker console.

kind plank
#

Thats all good to know! Think I was looking in the wrong place as this morning its still running and going along. Only issue I have is it crashes plex sometimes. I thought it was because of running both movies and tv on one config on a large ish database so separated them out. But still its crashing plex. I run a programme to auto restart plex but sometimes even that doesnt work. Any ideas that may help?

kind plank
#

If it helps my Config for the plex-meta-manager which is for my movies

flint cliff
#

Do you have a log of this happening?

fluid edge
#

Why not put tv and movies in the same config?

kind plank
kind plank
#

@flint cliff This is the latest log for plex. I noticed last night none of the overlays updated.. think it crashed the same again so decided to run it with --overlay -r so I could see it happen. This was the output from running that. I have 64bit plex running updated to latest along with running AlwaysUp (Because it crashes so often I need it to be restarted)

analog mulch
#

honestly, if everything seems to crash so often on that system, it might be a good idea to find out why everything crashes and fix that underlying cause instead of just restarting everything over and over

honest valley
#

Some people set it to 180, some to 300.

But if you are already sunig AlwaysUp because of how often Plex crashes, I dread to think what's gonna happen when you're also hitting the Plex API with PMM requests 😄

kind plank
#

So I managed to get it to run the overlays without any timeouts after upping it to 360. But last night I had a different error with the ratings that hasnt happened before.. Im wondering if Im trying to run too much at once. Perhaps when its cached, it may run better...

honest valley
#

"PMS is currently running startup maintenance tasks"

#

Looks like Plex either a) restarted or b) was running scheduled tasks when PMM was trying to do something

kind plank
#

Hmm yeah I see that now. I have changed scheduled tasks to 00:00 ending at 05:00 when pmm starts. But perhaps this is when it crashes and is being restarted.

I ran it again using -r this morning and have this error..
Seems like loads of errors/timeouts everywhere with things
requests.exceptions.ConnectTimeout: HTTPSConnectionPool(redacted): Max retries exceeded with url: /title/tt9850370/parentalguide (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f9d206778e0>, 'Connection to www.imdb.com timed out. (connect timeout=180)'