Problems shutting down DNSserver again. It’s a given it stops working over X amount of time. Sometimes X is 10 minutes, sometimes it’s a few hours…never guaranteed. There was one update that seemed to allow this problem to exit (I even posted all was well)…but in newer updates these issues have reappeared. And once the DNSserver stops responding, it refuses to shut down correctly, as well as close port 53 [Errno 48]. Which means my Mac is being shut down several times a day so I can run PlexConnect.
Only using Ethernet connection on my Mac Mini; Mac OS X 10.7.5. Apple TV 3; 5.2.1 software. DNSserver on Apple TV set to 192.168.2.15…same as local IP of PMS. PlexConnect and PMS running on same Mac. Media stored on external drive. Newest build available, updated today.
I have had similar problems over the last few days. The failure of Plexconnect to shut down the Webserver properly has been the most obvious issue and also leads to the occupied port issue for me. I think it is the Webserver, not the DNSServer that isn't shutting down. Restarting usually fixes this issue.
I have also had the problem where Plexconnect starts up and works for a while and then becomes unresponsive. I initially thought this may be a local network issue but reading your post the problem is similar to what you describe where Plexconnect works for a while but then the ATV cannot find trailers and nothing appears in the terminal indicating that there is anything wrong (or anything even happening). This did not happen for me until about 2 days ago. I update Plexconnect every morning.
Plexconnect and PMS are on an iMac running Snow Leopard and my ATV 3 is connected via wireless and the OS is up to date.
Yup, looking forward to gettin this resolved 
You may be onto something with that WebServer idea… Terminal always hangs after it says “WebServer: Shutting Down,” and thus PlexConnect never fully shuts down.
By the way, rather than having to reboot the computer, I find I can clear the blocked port by killing all Python processes in Activity Monitor (on a mac). Saves a bit of hassle.
I've been discussing with Baa and we are struggling to see how to troubleshoot it if the terminal is showing everything as working. If you can reproduce the problem please:
- let us know if it isn't shutting down or freezing
- let us know if the terminal window output changes if using the normal atv apps and what the output is e.g. if passing on dns requests
- use "sudo lsof -i -P" in a terminal window and send the output to pastebin to see if we can see what ports are being held by what
also are you using any apps like skype? it can apparently have a nasty habit of grabbing port 80
Today's build has been shutting down properly. I'll send this info when and if it messes up again.
I do have an off topic question though. I ran "sudo lsof -i -P" and saw that my computer tries to connect to yazsoft.com a lot from various commands such as:
No idea but i see Yazsoft have warning in their forum about malware ridden pirate images of their software, apparently it caused system instability (i am not assuming that you used a pirate software).
Do you have another drive you could swap out with a fresh install of OSX/Windows to see if there is some kind of conflict with other software?
I too have had this problem. I am happy to find others who have observed this. I just downloaded the most recent release (today) and hope it will help. For the record, I had tried going into activity monitor and quitting Python, but I still had to restart to "clear" the port so I could start PlexConnect again. Another thing that sucks, is when it fails, the network is down for the apple TV entirely. I can't even use netflix. Airplay mirroring works though. For the record, I have an apple TV 3 with the latests firmware (5.2ish), and a fully functioning hackintosh running OS X 10.8.3, Plex Media Server 0.9.7.22.511. Looking forward to more stability out of a great solution! Keep up the good work, it is much appreciated.
Question...
once PlexConnect has failed, is there any evidence in the terminal output that the WebServer already died? I wonder, if there is any uncatched exception happening along the way.
Question...
once PlexConnect has failed, is there any evidence in the terminal output that the WebServer already died? I wonder, if there is any uncatched exception happening along the way.
No evidence on my end...everything stops working but no output appears in terminal...it's just showing the output prior to PlexConnect failing.
Please follow the info I gave and post the output, the more info we have the better.
from http://forums.plexapp.com/index.php/topic/57831-plex-atv-think-different/?p=400115:
>> it just stops everything after it says "***forward request."
Life is good... I have a theory: It is the DNSServer!
This is how I see it: aTV sets up a DNS request, which gets forwarded - just as it says. Unfortunately we don't get an answer back... getting stuck in line 159: DNS_forward.sendto(data, (Settings.getIP_DNSmaster(), 53))
I think this is the only http communication, where I didn't put in any timeout handling.
By the way - once it got stuck, have you ever tried to kill python/PlexConnect with "CTRL-Z"? This should result in a KeyboardInterrupt shutting down the system - similar to the ENTER key.
EDIT: new commit, adding timeout. Please try again!
Hi Baa. That works. It shuts down cleanly now.
Thanks
Great... How about pressing "Mark Solved"? :-D
I am not the original poster. Not sure I can mark it solved (at least I do not see how).
Count the buttons to the lower right:
MultiQuote - Quote - Mark Solved
you should select the "good" message first... :-D
Great... How about pressing "Mark Solved"? :-D
Done ;)
Sweet! Just updated, and so far so good 
Great... How about pressing "Mark Solved"? :-D Done ;)
Thx for hitting that f00b4r, it still doesn't appear for me. I would have selected it if I could...I swear!
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
