Running OS X 10.10.1 on Mac Mini Server (not using the actual server app, just mac mini server hardware)
Latest PlexConnect, Latest PMS
Every time my server reboots, I have to manually restart the PlexConnect service using the sudo restart.bash command.
I have installed PC as a launchdaemon, and this all used to work fine. I think Yosemite broke it....
On the ATV, unless I restart the daemon, nothing gets discovered except for Home Sharing. The home screen does not populate with the "internet connected" icons (for lack of a better term)
I have attached the PlexConnect.log, but that only shows from when I restarted the daemon. Where can I get a log going back further?
I played around with the bash plist for iOS devices maybe this would work for you also if the prior test bash I provided doesn't work (Note this relies on google) Hopefull @baa won't kill me for this ;)
- 78 points to the error.
Difference to wahlman's file: "sleep 1"
I haven't seen this behavior unless one used a hacintosh...
Do you think that it may be because :
A) Yosemite has broken it?
B ) I have PC stored on my second HDD and not the OS drive?
I played around with the bash plist for iOS devices maybe this would work for you also if the prior test bash I provided doesn't work (Note this relies on google) Hopefull @baa won't kill me for this ;)
You need a internet connection to use PlexConnect. I knew one user that borrowed his neighbors internet, started up PlexConnect then disconnected the internet and PlexConnect still worked since all the apps had loaded on their aTV. You need to load the storeFront (apps) at minimum on your aTV.
You can try to add a lager "sleep" amount of time into the plist maybe you will have success then. Since its server I'm not sure if that is the issue or something else. You can search for a thread on OS X server that may help you.
But it’s not running the actual server software. I’m just going overseas for a few weeks. I’ll try move PC back into the OS HDD and see if it makes a diff
I don't see how that would fix it. I did find another possible option here. I would mess with the delay (sleep) function by 10 or 20 seconds. I think its a timing error but without testing more time its hard to say for sure.