I’m trying to figure out the best time for Windows and Plex to auto-update themselves so they don’t take any Plex streams down when someone’s likely to be connected to the server.
How do you specify the time frame when PMS updates itself? Does this happen within the Scheduled Tasks start and stop times?
I believe so, but I did not find any confirmation in the support docs.
https://support.plex.tv/articles/202197488-scheduled-server-maintenance/
I don’t normally run pms on windows, so don’t have much experience when it auto updates.
I guess this is the answer:
My problem is there’s no mention of version updates being a “task”.
Should we assume that it is a task, albeit one that isn’t actually mentioned anywhere under Scheduled Tasks?!
IMO there should at least be an additional entry that says “Install version updates” and then have its checkbox checked but grayed out, to indicate to the user that they can’t disable it from happening within the maintenance window.
Windows aside (that update takes - forever) it’s likely Plex can update itself - and never bother a stream. It happens all the time at my house. If I have friends on and watching when I need to reboot the Server, I just reboot the server. The streams run off the Buffer in their devices until the server comes back up.
Of course, my streams have a WHOLE LOT more in the buffer at any given time than others and your mileage will absolutely vary.
Is there any reason you can’t go to a manual update from Plex - so you need to push the button at an opportune time instead of rolling the dice and letting Plex push it for you?
That’s cool. I was thinking about buffers and figured it might work but wasn’t sure the clients would reconnect quickly enough afterwards.
Awesome! I guess I don’t have anything to worry about in that case.
Laziness.
Basically I’d like to set it and forget it. I trust updates not to break anything so don’t mind if they happen automatically but just wanted to ensure they happened when no one would be using it (so late at night basically).
Don’t be lazy - and here’s why:
I like to look at the update notes - and give others the hour or two ‘safety net testing’ that would reveal the thermo-nuclear device that could be packaged up in that Plex Update… it’s happened before and I have no illusions it won’t happen again…lol
It’s just an update - yes, we’re all likely waiting for that fix - but we’ve probably been waiting this long, a little more won’t hurt…
Are bad updates eventually fixed by subsequent good ones, or do people have to roll back and screw around with PMS to fix it? I don’t mind waiting for it to automatically fix itself lol.
Yea, Plex won’t let a bomb survive long… at least there’s that.
I’d rather wait a little, than back up a version (or two) when I’ve leaped too soon.
I ran auto-update manually on June 16th and it said I was already up to date but a new version was released on the 14th, a couple of days before -so I already kind of had the feeling that letting PMS update itself would lag behind manual updates a bit! I guess that’s why updates that break it wasn’t something I was that nervous about.
Also, I don’t have the beta channel enabled, so I’m not getting the bleeding edge updates either.
THAT is a good idea.
What I would do - is change the update routine to Manual - you can have Plex send the update if you like, but make sure it’s YOU that triggers it.
You can test it yourself that way:
Start a Stream on a device - then update the server.
You may find your stream continues on without interruption.
Mine do - locally and remote.
… and yes - I always reboot the server after an update.
That never affects a stream negatively at my house either.
Note:
If streams are in progress - I update the server - then when that calms down and the streams get more buffer - I reboot the box. Painless.
Interesting. Do you mean to use manual updates as a temporary setting, just to see if PMS updates interrupts streams, or as a setting to keep enabled permanently?
Mine is permanent.
I don’t let Plex do a lot of things without supervision.
Updates are at the top of the list ('cause I have had to back up from my Version backups - and I’d really like to avoid any future forays into that sequence of events).
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
