Reinstalled Mavericks OS, now getting "DNSServer not alive. Shutting Down"

Third Party Apps & Tools
1

I reformatted a Macbook Pro that was running plexconnect flawlessly, and after re-installing everything I am getting the following error when initializing plexconnect:

11:43:44 PlexConnect: ***
11:43:44 PlexConnect: PlexConnect
11:43:44 PlexConnect: Press CTRL-C to shut down.
11:43:44 PlexConnect: ***
11:43:44 PlexConnect: started: 11:43:44
11:43:44 PlexConnect: Version: 0.3.1+
11:43:44 PlexConnect: Python: 2.7.5 (default, Aug 25 2013, 00:04:04) 
[GCC 4.2.1 Compatible Apple LLVM 5.0 (clang-500.0.68)]
11:43:44 PlexConnect: Host OS: darwin
11:43:44 PlexConnect: IP_self: 10.0.1.6
11:43:44 DNSServer: started: 11:43:44
11:43:44 DNSServer: Failed to create socket on UDP port 53: [Errno 13] Permission denied
11:43:44 PlexConnect: DNSServer not alive. Shutting down.
11:43:44 PlexConnect: Shutting down.
11:43:44 PlexConnect: shutdown

After doing some research, I have tried the following:

 

1. Ensured internet sharing was disabled in Mavericks. 

2. Opened port forwarding for port 53 and assigned to macbook pro. (Im not 100% on this, so below is a screen shot from Airport Utility)

 

wKsAzfZ.png

 

Still getting the "shutting down" message. Any ideas on the fix? 

 

Thank you.

2

Close port forwarding before anything!!! You do not want a non-hardened DNS server exposed to the outside world.

Reboot your machine and try again, if still getting the error open a terminal window and enter the following (without the quotes) in the terminal "sudo lsof -i -P" and look to see in the output what is using port 53.

3

Close port forwarding before anything!!! You do not want a non-hardened DNS server exposed to the outside world.

Reboot your machine and try again, if still getting the error open a terminal window and enter the following (without the quotes) in the terminal "sudo lsof -i -P" and look to see in the output what is using port 53.

Thank you for the quick response!

I turned off port forwarding immediately after testing it.

I rebooted, and checked in terminal using the command you said. The only thing in the entire list that even has a 53 is this:

mDNSRespo  38 _mdnsresponder    8u  IPv4 [REDACTED]      0t0    UDP *:5353

Any ideas?

4

Try running PlexConnect again as the port looks to have been freed up. Make sure you shut down PlexConnect using CTRL+C or it will not shut down properly and port 53 issues may occur (you don’t need to do this if using the daemon to auto start it).

5

Try running PlexConnect again as the port looks to have been freed up. Make sure you shut down PlexConnect using CTRL+C or it will not shut down properly and port 53 issues may occur (you don't need to do this if using the daemon to auto start it).

That doesn't seem to be working. There is nothing on port 53, even after rebooting.

Is there anyway to change the port it is trying to open?

6

Yeah... you can change that port in Settings.cfg. But then it wouldn't answer to aTV's requests coming in on #53 (DNS). So it doesn't help that much.

But you are sure, you are doing the "sudo" thing/having admin rights? Doesn't look like it...

7

You say there is nothing but there must be if you are getting that error.

Are you still getting the exact same error? Post the whole output of the PlexConnect terminal window and of the command i gave you.

8

Yeah... you can change that port in Settings.cfg. But then it wouldn't answer to aTV's requests coming in on #53 (DNS). So it doesn't help that much.

But you are sure, you are doing the "sudo" thing/having admin rights? Doesn't look like it...

This was it. Wow, its always something silly.

NO :

/applications/PlexConnect-master/PlexConnect/py

YES:

sudo /applications/PlexConnect-master/PlexConnect/py

Thank you both for your help. If I hadn't been reviewing the latest 

sudo lsof -i -P

 output, I wouldn't have noticed that PlexConnect was being run as my logged in user and not root.

This community really is awesome. Thanks.

9

>>PlexConnect/py

-> PlexConnect.py

10

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.