Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

I have a dns error and I dont know how to fix it! #899

Closed
INFINIX98 opened this issue Nov 6, 2016 · 5 comments
Closed

I have a dns error and I dont know how to fix it! #899

INFINIX98 opened this issue Nov 6, 2016 · 5 comments
Labels

Comments

@INFINIX98
Copy link

I tried to installation it on ubuntu but i have this problème now ! rty@localhost:~$ sudo homebridge
*** WARNING *** The program 'nodejs' uses the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs
*** WARNING *** The program 'nodejs' called 'DNSServiceRegister()' which is not supported (or only supported partially) in the Apple Bonjour compatibility layer of Avahi.
*** WARNING *** Please fix your application to use the native API of Avahi!
*** WARNING *** For more information see http://0pointer.de/avahi-compat?s=libdns_sd&e=nodejs&f=DNSServiceRegister
[11/5/2016, 4:34:26 PM] Loaded plugin: homebridge-http
[11/5/2016, 4:34:27 PM] Registering accessory 'homebridge-http.Http'
[11/5/2016, 4:34:27 PM] ---
[11/5/2016, 4:34:27 PM] Loaded config.json with 1 accessories and 0 platforms.
[11/5/2016, 4:34:27 PM] ---
[11/5/2016, 4:34:27 PM] Loading 0 platforms...
[11/5/2016, 4:34:27 PM] Loading 1 accessories...
[11/5/2016, 4:34:27 PM] [Chambre] Initializing Http accessory...
Scan this code with your HomeKit App on your iOS device to pair with Homebridge:

┌────────────┐
│ 031-45-154 │
└────────────┘
/usr/lib/node_modules/homebridge/node_modules/mdns/lib/advertisement.js:56
dns_sd.DNSServiceRegister(self.serviceRef, flags, ifaceIdx, name,
^

Error: dns service error: unknown
at Error (native)
at new Advertisement (/usr/lib/node_modules/homebridge/node_modules/mdns/lib/advertisement.js:56:10)
at Object.create as createAdvertisement
at Advertiser.startAdvertising (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Advertiser.js:43:30)
at Bridge.Accessory._onListening (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:526:20)
at emitOne (events.js:96:13)
at HAPServer.emit (events.js:188:7)
at HAPServer._onListening (/usr/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/HAPServer.js:185:8)
at emitOne (events.js:96:13)
at EventedHTTPServer.emit (events.js:188:7)

@jonathanweinberg
Copy link

Check out #527 ?

@danijelst
Copy link

I had the same issue but didn't find anything how to solve it. At the end I figured out as I run homebridge inside of a docker with the commandline including --net=host that the Bonjour service port 5353 was already occupied by some other process. You can check if the port is already taken by some process with

netstat -anp | grep 5353

This will list something like:

`
[~] # netstat -anp | grep 5353

netstat: /proc/net/tcp6: No such file or directory
udp 533760 0 0.0.0.0:5353 0.0.0.0:* 13315/python
udp 533760 0 0.0.0.0:5353 0.0.0.0:* 13315/python
udp 533760 0 0.0.0.0:5353 0.0.0.0:* 13315/python
udp 533760 0 0.0.0.0:5353 0.0.0.0:* 13315/python
`

the 13315 is the pid which you then can check what the process is.

@Anuj79
Copy link

Anuj79 commented Mar 18, 2017

can you let me know how you figured out it was the port. i am getting the same error and i disabled the avahi demon running on the nas but i still get this error

[/share/Docker/homebridge] # netstat -plunt | grep 5353
netstat: /proc/net/tcp6: No such file or directory
netstat: /proc/net/udp6: No such file or directory

@Anuj79
Copy link

Anuj79 commented Mar 18, 2017

i had to log into the container to run the avahi manually by giving following command.. in case its helpful to anyone else

/etc/init.d/dbus start
avahi-daemon --debug --no-drop-root

@stale
Copy link

stale bot commented Oct 31, 2017

This issue has been automatically marked as stale because it has not had recent activity, and will be closed if no further activity occurs. If this issue was overlooked, forgotten, or should remain open for any other reason, please reply here to call attention to it and remove the stale status. Thank you for your contributions.

@stale stale bot added the stale label Oct 31, 2017
@stale stale bot closed this as completed Nov 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants