Over the last couple of days I have had an issue with shutting down Plexconnect where the port is not cleared and when I restart Plexconnect gives the port being used error. I thought it was because of some incompatibility between recent versions and the Applescript I was using where the shutdown process wasn't working.
After testing a bit, however, with and without the applescript (just using the sudo terminal process) and just using the latest build with no modifications, I have discovered there is a rogue python process that seems to be starting and crashing constantly. I discovered this by going into Activity Monitor (I am on OSX 10.6.8) and what i see is the regular steady python processes and then one that keeps appearing and disappearing, which i assume is one trying start and then failing.
Again this began a day or 2 ago so it is not a result of yesterdays big changes alone. Also, it doesn't interfere with the operation of Plexconnect except when I have to quit it for some reason. In that case I have to restart the computer to restart Plexconnect successfully. I am also unable to kill the rogue process in Activity Monitor because it is never stable enough to select as it keeps starting and stopping, starting and stopping etc.
No. Looking further, this might have something to do with PMS. In console is see this:
6/30/13 6:43:52 AM[0x0-0x30030].com.plexapp.plexmediaserver[437] File "/Users/***/Library/Application Support/Plex Media Server/Plug-ins/Framework.bundle/Contents/Resources/Versions/1/Python/PMS/YAML.py", line 6, in
So, I managed to get this to stop happening by going back to using the terminal to initiate Plexconnect. I was using the AppleScript and I think it wasn’t shutting things down properly for some reason. The usr/bin/env python wasn’t working with the script either so going old school is probably best.
Still don’t know why PMS can’t find “Yaml” and if it is important or not.
