You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello guys,
I've set up via the easy nmos suite, but neither the Hardware Blackmagic Decklink IP nor the virtnode appears in the registry.
It seems to have a problem with mDNS.
nmos-virtnode | Starting mDNSResponder service
nmos-virtnode | Starting Apple Darwin Multicast DNS / DNS Service Discovery daemon: mdnsd.
nmos-testing | * Removing stale PID file /var/run/dbus/pid.
nmos-testing | * Starting system message bus dbus
nmos-testing | ...done.
nmos-testing | * Starting Avahi mDNS/DNS-SD Daemon avahi-daemon
nmos-testing | Process 21 died: No such process; trying to remove PID file. (/run/avahi-daemon//pid)
nmos-testing | ...done.
nmos-virtnode | 2025-03-27 21:22:27.416: more info: 124985058211584: After DNSServiceBrowse, DNSServiceProcessResult timed out or was cancelled
nmos-virtnode | 2025-03-27 21:22:27.416: more info: 124985016248064: After DNSServiceBrowse, DNSServiceProcessResult timed out or was cancelled
nmos-virtnode | 2025-03-27 21:22:27.416: warning: 124984781252352: Did not discover a suitable System API via DNS-SD
The text was updated successfully, but these errors were encountered:
Hello guys,
I've set up via the easy nmos suite, but neither the Hardware Blackmagic Decklink IP nor the virtnode appears in the registry.
It seems to have a problem with mDNS.
nmos-virtnode | Starting mDNSResponder service
nmos-virtnode | Starting Apple Darwin Multicast DNS / DNS Service Discovery daemon: mdnsd.
nmos-testing | * Removing stale PID file /var/run/dbus/pid.
nmos-testing | * Starting system message bus dbus
nmos-testing | ...done.
nmos-testing | * Starting Avahi mDNS/DNS-SD Daemon avahi-daemon
nmos-testing | Process 21 died: No such process; trying to remove PID file. (/run/avahi-daemon//pid)
nmos-testing | ...done.
...
nmos-registry | 2025-03-27 21:22:26.351: error: 123186052519680: DNSServiceRegisterRecord reported error: -65540
nmos-registry | 2025-03-27 21:22:26.351: error: 123185911531264: DNSServiceRegister reported error: -65540 while registering advertisement for: nmos-cpp_query_192-168-151-3:80._nmos-query._tcp..
nmos-registry | 2025-03-27 21:22:26.351: error: 123185903138560: DNSServiceRegister reported error: -65540 while registering advertisement for: nmos-cpp_registration_192-168-151-3:80._nmos-registration._tcp..
nmos-registry | 2025-03-27 21:22:26.351: error: 123185894745856: DNSServiceRegister reported error: -65540 while registering advertisement for: nmos-cpp_registration_192-168-151-3:80._nmos-register._tcp..
nmos-registry | 2025-03-27 21:22:26.351: error: 123185886353152: DNSServiceRegister reported error: -65540 while registering advertisement for: nmos-cpp_node_192-168-151-3:80._nmos-node._tcp..
nmos-registry | 2025-03-27 21:22:26.352: error: 123185877960448: DNSServiceRegister reported error: -65540 while registering advertisement for: nmos-cpp_system_192-168-151-3:80._nmos-system._tcp..
...
nmos-virtnode | 2025-03-27 21:22:27.416: more info: 124985058211584: After DNSServiceBrowse, DNSServiceProcessResult timed out or was cancelled
nmos-virtnode | 2025-03-27 21:22:27.416: more info: 124985016248064: After DNSServiceBrowse, DNSServiceProcessResult timed out or was cancelled
nmos-virtnode | 2025-03-27 21:22:27.416: warning: 124984781252352: Did not discover a suitable System API via DNS-SD
The text was updated successfully, but these errors were encountered: