Sudden death, FreeNAS plexmediaserver-plexpass plugin

[Nuked_AnD]

I’ve been running PMS on Windows for a while now, and recently (over a week ago) I’ve migrated data to FreeNAS plugin which was working without any issues.

My initial thought was that plugin just died, so I’ve created a new jail and installed PMS from scratch and after that, I’ve copied across server data to a new jail. That came to the same result.

I’ve reviewed logs and tried to search on those errors but none of the solutions seems to bring it back to life.

Server Version#: 1.13.5.5291

Dec 01, 2018 23:02:47.849 [0x80e732f00] ERROR - Sync: failed to get status for sync list 20017315, sync item 22066048

Dec 01, 2018 23:02:50.689 [0x80ca17000] ERROR - Error issuing curl_easy_perform(handle): 7

Any help is greatly appriciated.

[mikec_pt]

So is PMS stopping/crashing? Or is it that you just can’t access the webapp?

Btw when you created the new jail di you set VIMAGE = on ?

[Nuked_AnD]

Thank for quick reply, the new jail I’ve created had it’s own IP address so I don’t believe that this is the cause of the issue however after I left my server running overnight, in the mail logs I can see that there is an activity it’s just a web interface is refusing the connection.

I’ve tried to remove the * System.bundle and * Framework.bundle but Plex doesn’t recreate them after the start so I’ve copied them back in from a newer version of PMS.

The stranges thing is that it’s all started after I’ve added a Grace Anatomy unofficial soundtrack of about ~1100 mp3. After that, it started going offline and after couple of restart of the plugin never return back online.

com.plexapp.system.log (38.1 KB)

[mikec_pt]

Can I kindly ask you to please edit the reply and upload the log rather then posting? (also I’m looking for the Plex Media Server.log (although others might help, this is usually the first place to start).

I also strongly recommend enabling VIMAGE (unsure if this means u need to re-create the Jail) as there will be some limitations without it.

[Nuked_AnD]

Thanks for the help with this.

I believe I’ve solved the mystery of the issue, which was caused by one of the below Preferences:

autoEmptyTrash=“1”
FriendlyName=“PlexServer”
sendCrashReports=“0”
ManualPortMappingMode=“1”
FSEventLibraryPartialScanEnabled=“1”
FSEventLibraryUpdatesEnabled=“1”
ScannerLowPriority=“1”
ScheduledLibraryUpdateInterval=“86400”
ScheduledLibraryUpdatesEnabled=“1”
EnableIPv6=“1”
TranscoderH264BackgroundPreset=“fast”
DlnaReportTimeline=“0”
ButlerStartHour=“1”
ButlerTaskRefreshLibraries=“0”
ButlerTaskRefreshPeriodicMetadata=“0”

I strongly believe that enabling IP6 what had done it but I don’t have currently a test Plex to experiment with to confirm it for sure.

So my solution was to replace Preferences.xml with a minimum setup setting and plex came back to live.

Once again thank you for all your help with this.

[mikec_pt]

Well I can confirm it was EnableIPv6 as I’ve actually just been testing with this recently.

I’ve only recently discover this but FreeBSD is actually violating an RFC here and doesn’t let you listen on v4/v6 using a single socket by default.

So if you look at the output of sockstat -l46 after enabling IPv6 you’ll find that it will only be listening on IPv6 an not v4 which is not the desired effect of this change.

A future PMS build should actually include a fix/workaround for this, but if you want to listen on both ipv6 and v4 on 32400, use this sysctl and that should do it:

sysctl net.inet6.ip6.v6only=0

This should allow the system to now listen also on v4 when a single socket is used to listen on both.

This systctl will no longer be needed once that PMS build with a fix is released though, so you might also just want to wait and for now don’t enable the preference.