PMS crashing immediately in macOS Mojave

[MacSupport]

UHC29: flags=0<> mtu 0
XHC0: flags=0<> mtu 0
UHC93: flags=0<> mtu 0
EHC250: flags=0<> mtu 0
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP>
	inet 127.0.0.1 netmask 0xff000000 
	inet6 ::1 prefixlen 128 
	inet6 ••••::1%lo0 prefixlen 64 scopeid 0x5 
	inet 127.94.0.2 netmask 0xff000000 
	inet 127.94.0.1 netmask 0xff000000 
	nd6 options=201<PERFORMNUD,DAD>
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
EHC253: flags=0<> mtu 0
UHC90: flags=0<> mtu 0
UHC26: flags=0<> mtu 0
UHC58: flags=0<> mtu 0
UHC61: flags=0<> mtu 0
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=b<RXCSUM,TXCSUM,VLAN_HWTAGGING>
	ether ••:••:••:••:••:•• 
	inet 10.0.••.130 netmask 0xffffff00 broadcast 10.0.••.255
	inet6 ••••::•••:••••:••••:••••en0 prefixlen 64 secured scopeid 0xd 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (1000baseT <full-duplex>)
	status: active
en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=b<RXCSUM,TXCSUM,VLAN_HWTAGGING>
	ether ••:••:••:••:••:•• 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (<unknown type>)
	status: inactive
en2: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
	ether ••:••:••:••:••:•• 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect (<unknown type>)
	status: inactive
fw0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 4078
	lladdr ••:••:••:••:••:••:••:•• 
	nd6 options=201<PERFORMNUD,DAD>
	media: autoselect <full-duplex>
	status: inactive
p2p0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2304
	ether ••:••:••:••:••:•• 
	media: autoselect
	status: inactive
utun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 2000
	inet6 ••••::••••:••••:••••:••••%utun0 prefixlen 64 scopeid 0x12 
	nd6 options=201<PERFORMNUD,DAD>

[sa2000]

@MacSupport

lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 options=1203<RXCSUM,TXCSUM,TXSTATUS,SW_TIMESTAMP> inet 127.0.0.1 netmask 0xff000000 inet6 ::1 prefixlen 128 inet6 ••••::1%lo0 prefixlen 64 scopeid 0x5 inet 127.94.0.2 netmask 0xff000000 inet 127.94.0.1 netmask 0xff000000

Could be the 127.94.0.1 and 127.94.0.2 addresses

[sa2000]

Linking to other forum topic where there is example of how to remove the additional ip addrsses

PMS will no longer start after 3.77.2 upgrade -- Mac

Thanks you!! Turns out I had two additional inet addresses on the loopback. I removed them using ifconfig interface -alias address. So, for me I typed ifconfig lo0 -alias <ip address>. Performed the update again and now Plex 1.14 starts up just fine. I still have two inet6 IPs on the loopback, so it appears those don’t matter. EDIT: It appears the (Transcoder) Resolved a rare deadlock (#9332) is working great. I would notice starting a TV show on IOS would not work. I would often have to resta…

[mschepers]

This is indeed a workaround that works easiest at the moment on MacOS 10.14.x Mojave. Downgrade to 1.13.9.5456. Thanks Aaron!

[piethout]

yeah i was having this same problem. Plex immediately crashing on launch. Only fix for me was to downgrade and dont forget to turn off automatic updates. It updated itself back to 10.14 and I had to redownload 1.13.9.5456 from the link in one of the comments above. Thanks for the link to 1.13.9.5456

[vlopddap]

Hi! I still give a sidelong look to this thread but my PMS is still on a 10.13.xx MacMini and still working flawlessly. However Apple are still prompting me several time a week to upgrade to Mojave and I am wondering if PMS is finally stable on Mojave, but apparently still not… right?

[darcilicious]

First, not everyone has issues running the latest PMS (v1.14) on Mojave (I do not, for example).
Second, it seems like those that do are able to work around it by keeping PMS at version 1.13 which you say you’re using. I’m not sure why you think you’ll have a problem at this point.

[sa2000]

@vlopddap

Hi! I still give a sidelong look to this thread but my PMS is still on a 10.13.xx MacMini and still working flawlessly. However Apple are still prompting me several time a week to upgrade to Mojave and I am wondering if PMS is finally stable on Mojave, but apparently still not… right?

There is a specific issue to do with having aliases for network interfaces including loopback which leads to a crash on launch. This will be fixed in 1.14.1 which is in QA at the moment before going out to beta initially

I posted a link earlier to a forum post from a user that shows how aliases can be removed to avoid the crash, ifconfig -a would show if there are multiple ip addresses for loopback or other ipv4 interface

see PMS crashing immediately in macOS Mojave - #45 by sa2000

[vlopddap]

@darcilicious

First, not everyone has issues running the latest PMS (v1.14) on Mojave (I do not, for example).
Second, it seems like those that do are able to work around it by keeping PMS at version 1.13 which you say you’re using. I’m not sure why you think you’ll have a problem at this point.

No, I am using latest version of PMS 1.14.0.5470, however I didn’t updated my MacMini to Mojave yet… it’s still on the latest release of High Sierra and I just want to wait until all possible issues are fixed (those in relation to Mojave). I already updated my other Macs to Mojave since a while (my 2x MacBook Pro, another MacMini and my iMac 27in). This specific MacMini is only used for PMS so I don’t want to break anything if it’s not necessary…

[darcilicious]

@vlopddap

but my PMS is still on a 10.13.xx MacMini and still working flawlessly.

@vlopddap

I am using latest version of PMS 1.14.0.5470,

Aha, I missed a digit, didn’t I?

Did you see the other response to your query from sa2000?

[vlopddap]

@darcilicious

@vlopddap

but my PMS is still on a 10.13.xx MacMini and still working flawlessly.

@vlopddap

I am using latest version of PMS 1.14.0.5470,

Aha, I missed a digit, didn’t I?

Did you see the other response to your query from sa2000?

yup, 10.13.xx stands for MacOS High Sierra where I don’t remember exact sub-release and too lazy to check

I am sorry if you misunderstood my concern, I don’t want to nitpick on PMS, it’s just because I have a fully working server right now on High-Sierra and I don’t want to mess anything if not needed. Is a saying that if something isn’t broken, don’t try to fix it… however I would like to gain other new feature from Mojave on my MacMini Server, so I don’t want to avoid upgrading if it wont cause issues to PMS.

[sa2000]

Plex Media Server 1.14.1.5487 has just been released as Beta. It has fix for the 1.14.0 issue leading to a crash on launch on MACs when network IP Address aliases are used.

See Release Notice

Plex Media Server

Plex Media Server 1.14.1.5487 is now available to Plex Pass users in the Beta update channel NEW: (Web) Updated to 3.77.4 FIXES: (DLNA) DLNA clients would not report timeline states for Now Playing (#9347) (DVR) Don’t return an error message when shutting down a live TV session in a normal way (#9277) (DVR) Recordings could be missed when the ‘HD only’ setting was selected (#9226) (DVR) Properly parse episode number from dd_progid field in XMLTV data (#9419) (DVR) Wait longer to detect dur…

• The server could crash when using network interface aliases on macOS (‪#9344‬; rdar://46083980)