I have a large amount of devices that have had their device name changed to a GUID, this is no good.
@jwol1 could you please run the command adamone-issue and send the output file to support@adamnet.works along with a link to this forum thread.
I am getting 50x Error. Loads for a few minutes than times out.
Are you able to run it from an SSH console prompt?
I’m seeing this too …
Version
4.14.0-1 | 14.0-CURRENT
@atw Is there any progress on a fix for this issue? It’s makng a complete mess of device lists. I hope it’s a priority for adam:ONE.
I’m seeing it on 4.14.1-1 | 15.0-CURRENT
You can delete devices but it repopulates again, so doesn’t seem any workaround administrators can make.
1 Like
@atw Any update please? Still seeing the issue.
@BrightSpark it seems that the mDNS function in anmuscle is not working correctly so what I would suggest is adding disable-sd to your anmuscle.conf configuration file, restart anmuscle and see if that resolves it for you.
Thanks @atw . Have followed your advice. No change visible in the device list, but have manually deleted GUID type entries to clean up the list somewhat. Just have to hope they don’t re-occur I guess. What do we lose by “disable-sd” (sorry not familiar with the command). Does lack of mDNS mean new device discovery is problematic? Is a fix to whatever underlying issue is causing this being worked on? I presume I’ll need to remove “disable-sd” at that point to restore mDNS? Any more background/general clues on this would be appreciated. I’m sure other users would also appreciate clarity. Thanks!
Yes it won’t automatically clear existing naming issues, but it should prevent that from happening again.
For some clarification, the “disable-sd” should disable the use of mDNS for naming and device discovery.
It still uses ARP, Netbios, and DHCP leases.
But I can’t speak to whether mDNS will be fixed. It might have to be removed altogether.