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

Not registering any node #37

Open
JahedulAnowar opened this issue Jul 10, 2020 · 4 comments
Open

Not registering any node #37

JahedulAnowar opened this issue Jul 10, 2020 · 4 comments
Labels

Comments

@JahedulAnowar
Copy link

I am not sure if registration is working properly or not as no nmos node seem to register the services and I get this output:

$ ./nmosregistration 

2020-07-10 12:25:27,018 : utils : DEBUG : Choosing interface from /etc/nmoscommon/config.json file: []
2020-07-10 12:25:27,018 : utils : DEBUG : Could not find ipp-utils, will try using default gateway interface
2020-07-10 12:25:27,019 : utils : DEBUG : Choosing interface using the default gateway: 192.168.2.1
WARNING:mdnsbridge:This class is deprecated. Please use the matching one in nmos-mdns-bridge instead.
Exception loading config: name 'f' is not defined
2020-07-10 12:25:27,204 : utils : DEBUG : Choosing interface from /etc/nmoscommon/config.json file: []
2020-07-10 12:25:27,204 : utils : DEBUG : Could not find ipp-utils, will try using default gateway interface
2020-07-10 12:25:27,204 : utils : DEBUG : Choosing interface using the default gateway: 192.168.2.1
2020-07-10 12:25:27,209 : utils : DEBUG : Choosing interface from /etc/nmoscommon/config.json file: []
2020-07-10 12:25:27,209 : utils : DEBUG : Could not find ipp-utils, will try using default gateway interface
2020-07-10 12:25:27,210 : utils : DEBUG : Choosing interface using the default gateway: 192.168.2.1
Could not open pid file, continuing
DEBUG:mdns-engine:Choosing interface from /etc/nmoscommon/config.json file: []
DEBUG:mdns-engine:Could not find ipp-utils, will try using default gateway interface
DEBUG:mdns-engine:Choosing interface using the default gateway: 192.168.2.1
Waiting for httpserver to start...
HttpServer running
Running on port: 8235
ERROR:cysystemd.daemon:Data could not be sent
DEBUG:garbage_collect:Not collecting - another collector has recently collected
DEBUG:garbage_collect:scheduled...
DEBUG:garbage_collect:Not collecting - another collector has recently collected
DEBUG:garbage_collect:scheduled...

Also on running the nmos-mdns-bridge output:

DEBUG:zeroconf mDNS:mDNS Service add: {'action': 'add', 'type': '_nmos-registration._tcp.local.', 'name': 'registration_192.168.2.1_http_dep._nmos-registration._tcp.local.', 'port': 80, 'hostname': 'registration_192.168.2.1_http_dep._nmos-registration._tcp.local', 'address': '192.168.2.1', 'txt': {b'pri': b'100', b'api_ver': b'v1.0,v1.1,v1.2,v1.3', b'api_proto': b'http', b'api_auth': False}}
DEBUG:zeroconf mDNS:mDNS Service add: {'action': 'add', 'type': '_nmos-register._tcp.local.', 'name': 'registration_192.168.2.1_http._nmos-register._tcp.local.', 'port': 80, 'hostname': 'registration_192.168.2.1_http._nmos-register._tcp.local', 'address': '192.168.2.1', 'txt': {b'pri': b'100', b'api_ver': b'v1.0,v1.1,v1.2,v1.3', b'api_proto': b'http', b'api_auth': False}}
@andrewbonney
Copy link
Contributor

This appears to be running correctly, but please note that it expects to be run with an Apache reverse proxy in front of it, otherwise the mDNS announcements do not match up with the port it runs on. The Apache configuration required is held in https://github.com/bbc/nmos-registration/blob/master/debian/ips-api-registration.conf and https://github.com/bbc/nmos-reverse-proxy/blob/master/etc/apache2/sites-available/ips-reverseproxy-common.conf

@JahedulAnowar
Copy link
Author

I got it to work by modifying line:87 to "current_priority = 100"

Thank you and sorry for the late reply.

@andrewbonney
Copy link
Contributor

Glad it's working. It should be possible to resolve this without having to adjust the code. By default the Registration API runs with a priority of '100' which is outside of the recommended range and is intended to prevent it disturbing a running system. If you want to put it into 'production' mode then this should be set between 0 and 99. You can do this using the configuration file as noted here: https://github.com/bbc/nmos-registration#configuration

@JahedulAnowar
Copy link
Author

I am not sure why it didn't work without adjusting the code.
Anyways, i intend to use Sony's implementation of nmos-registration, and so far i think it is working the way i want.

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

2 participants