13.0 upgrade and now I have to reboot daily to get my box back ...

[johnism]

So my 12 was running good except I had to create a cron job to restart my Plex jail every day because four months ago Plex would become unresponsive.
I did try Upgraded Plex plugin and still no luck only a jail restart or reboot would fix the issue ..
I saw 13 was available and thought maybe a base OS upgrade may fix the issue. .. After the upgrade during the midday TrueNAS portal and Plex become unresponsive , but my shares still work.
So far the only fix is a reboot.
What sucks is for over a year I ran Plex and TrueNAS 12 no issues ..rock solid .
Attached is the error screen I see when I have to reboot.
I may have to set a cron job to reboot daily to make sure my box is up . I am assuming shutdown-r would accomplish that?
Thanks for any help or direction ,
John

 

[djkt1980]

So my 12 was running good except I had to create a cron job to restart my Plex jail every day because four months ago Plex would become unresponsive.
I did try Upgraded Plex plugin and still no luck only a jail restart or reboot would fix the issue ..
I saw 13 was available and thought maybe a base OS upgrade may fix the issue. .. After the upgrade during the midday TrueNAS portal and Plex become unresponsive , but my shares still work.
So far the only fix is a reboot.
What sucks is for over a year I ran Plex and TrueNAS 12 no issues ..rock solid .
Attached is the error screen I see when I have to reboot.
I may have to set a cron job to reboot daily to make sure my box is up . I am assuming shutdown-r would accomplish that?
Thanks for any help or direction ,
John
View attachment 59396

@johnism ... Absolute same issue for me, however, slight deviation in that my box still works on all fronts, just PLEX is the issue. If I restart the Jail/Plugin now, 24 hours later I'm unable to connect through the IP address, home devices with apps installed, or outside of my network. ( I do have PlexPass Lifetime). No issues when it was running TrueNAS 12 with the older Plex version. I have even loaded an older snapshot of PLEX and that didn't solve it.
I see that no one else has replied to you on the thread, but did you ever receive any direct messages? Or did you get it resolved on your own..? I'm curious to try any new options/ideas.

 

[Whattteva]

How much RAM does the system have?

 

[djkt1980]

@Whattteva ... Unfortunately, I'm now at the day job and NAS is at home.
I'll update my signature with specs soon, but to answer your questions, I believe my system has 4 sticks .. 16gb total.

 

[sretalla]

Jails should be considered disposable, so the answer here would be either:

Separate out your plex config/DB to storage on the host and build a new 13.1-RELEASE jail and put plex in it

or

If you already have your data separated, just build a new jail and switch to using that.

Ultimately, changing to a manually created jail from the plugin would be key here as the plugin tends to not get updated enough.

There are threads around on how to do that. I can answer questions if needed.

 

[djkt1980]

@sretalla .. Thanks for the instructions. I created the manual jail but was unable to figure coding out before turning in for the night.
After logging in this morning, I noticed this at the bottom.
Not sure when or where I created the configuration reload either....

 

[sretalla]

Well, it is Friday the 13th, but that's very odd... I wouldn't expect a config reload to be happening automatically at all, so finding the source of that action and making it stop is a good selection for priority 1.

 

[djkt1980]

Well, it is Friday the 13th, but that's very odd... I wouldn't expect a config reload to be happening automatically at all, so finding the source of that action and making it stop is a good selection for priority 1.

You called it! HA. I'm reviewing the forums now to determine the cause for the "exited on Signal 11" and for the "Configuration reload request..."
.. Again, thank you for your help. Have a great weekend!

 

[Alecmascot]

Well, it is Friday the 13th, but that's very odd... I wouldn't expect a config reload to be happening automatically at all, so finding the source of that action and making it stop is a good selection for priority 1.

All my FreeNAS/TrueNAS servers over the years have reloaded the config at mignight !

 

[sretalla]

All my FreeNAS/TrueNAS servers over the years have reloaded the config at mignight !

Apparently so do mine... I had never noticed that.

It doesn't impact my jails though, so evidently something else must be going on there.

 

[Whattteva]

Apparently so do mine... I had never noticed that.

It doesn't impact my jails though, so evidently something else must be going on there.

Wow, I had never noticed that. I, too have that after looking at my logs. No adverse effects from it though, so I'd say it's probably harmless.

Interestingly, I checked my vanilla FreeBSD server installation and it doesn't have that midnight configuration reload, so that's something else to thinkj about.