Send netdisco-users mailing list submissions to
netdisco-users@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
netdisco-users-requ...@lists.sourceforge.net
You can reach the person managing the list at
netdisco-users-ow...@lists.sourceforge.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. Re: New install failed to find a number of devices.
Recommendations for determining failure points and cleaning up
database? (Oliver Gorwits)
2. How does netdisco-web resolve its hostname? (Stuart Kendrick)
--- Begin Message ---
Hi again David
Seems I forgot that store_modules setting does exist:
https://github.com/netdisco/netdisco/wiki/Configuration#store_modules
However it is global so removes the functionality from all device discover.
Would be nice to be an ACL so I'll leave the ticket open.
Maybe this helps you complete the reinstallation though. Chassis/module
info should not be needed for any other Netdisco function (unless you rely
on the relevant reports of course).
regards
Oliver.
On Tue, 14 Nov 2023 at 22:07, Oliver Gorwits <oli...@cpan.org> wrote:
> Hi David
>
> The different errors you describe all relate to the "Device Modules" tab
> entries, that is, the hardware components reported by the device. Invalid
> parent means the report is somehow inconsistent with itself, and the
> uninitialized error, while a bug in Netdisco, also points to some weird
> data back from the device.
>
> Unfortunately we don't have a feature in Netdisco to disable Entity
> gathering (which would just skip this stuff and allow the rest to
> continue). I've made a ticket for it:
> https://github.com/netdisco/netdisco/issues/1126
>
> The other option is to share with me the output of an snmpwalk if the
> device will allow it, and I can see if I can reproduce the issue(s) and fix
> them: https://github.com/netdisco/netdisco/wiki/Snapshot#share-a-snapshot
>
> Oh, I guess the other hack you could do locally is copy "worker_plugins"
> config from the default and remove the "Discover::Entities" item to disable
> it. https://github.com/netdisco/netdisco/blob/master/share/config.yml
>
> I also opened a ticket for the uninitialized value bug
> https://github.com/netdisco/netdisco/issues/1127
>
> Kind regards
> Oliver.
>
> On Tue, 14 Nov 2023 at 04:06, David Bertagni <dberta...@brynmawr.edu>
> wrote:
>
>> Hi,
>>
>> Apologies if this is noted elsewhere and I missed it...
>>
>> I have an old instance, v2.39.19, on an old Ubuntu distribution that I'm
>> replacing with a new from scratch instance, v2.68.1. I decided to not
>> migrate anything but the basic configuration and allowed the new instance
>> to find devices with a single seed to my core Juniper stack. It found
>> _most_ of them, but I had to manually discover a dozen or so and I'm
>> wondering how best to clean up the manual discovery as they all came up
>> with "invalid parent" errors and a few reported this error:
>> "Use of uninitialized value in sprintf at
>> /home/netdisco/perl5/lib/perl5/App/Netdisco/Worker/Plugin/Discover/Entities.pm
>> line 109."
>>
>> I'm primarily a Juniper shop with some legacy HP and newer Aruba-CX type
>> switches. I'm getting ready to deploy Extreme's universal switch line, as
>> product becomes available.
>>
>> I'm not sure exactly why discovery failed as it was pretty random from my
>> end. The switches are all configured identically and some were found while
>> others skipped even on the same network.
>>
>> Happy to provide logs and other output as I'd like to get this instance
>> up clean before retiring out the old.
>>
>> Thanks,
>> David Bertagni
>> Bryn Mawr College
>>
>>
>> _______________________________________________
>> Netdisco mailing list
>> netdisco-users@lists.sourceforge.net
>> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>>
>>
--- End Message ---
--- Begin Message ---
BRIEF
* How does netdisco-web resolve its hostname?
BACKGROUND
* I am currently running NetDisco under CentOS 7.9
* I have a built a new box running Rocky 9.2 and am installing NetDisco
DETAIL
On the new box ('new-server'), when I load the Web front-end:
[netdisco@new-server ~]$ ~/bin/netdisco-web start
Netdisco Web [Started]
config watcher: watching /home/netdisco/environments for updates.
[netdisco@new-server ~]$
I see the following in /home/netdisco/logs/netdisco-web.log
Resolved [*]:5000 to [::]:5000, IPv6
Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::]
IPv6
Binding to TCP port 5000 on host :: with IPv6
2023/11/14-10:47:44 Can't connect to TCP port 5000 on :: [Invalid argument] at
line 66 in file /home/netdisco/perl5/lib/perl5/Net/Server/Proto/TCP.pm
2023/11/14-10:47:44 Received QUIT. Running a graceful shutdown
2023/11/14-10:47:44 Worker processes cleaned up
2023/11/14-10:47:44 Server closing!
And nothing is listening on TCP 5000
[root@new-server ~]# lsof -nP -i:5000
[root@new-server ~]#
So, examining those logs messages ... seems to me that the Web front-end is
having trouble resolving its hostname ...
If I specify host, the Web front-end loads fine:
[netdisco@new-server ~]$ bin/netdisco-web start --host 127.0.0.1
Netdisco Web [Started]
config watcher: watching /home/netdisco/environments for updates.
[netdisco@new-server ~]$ bin/netdisco-web stop
config watcher: sending TERM to the web server (pid:411033)...
Netdisco Web [Stopped]
[netdisco@new-server ~]$ bin/netdisco-web start --host new-server
config watcher: watching /home/netdisco/environments for updates.
Netdisco Web [Started]
[netdisco@new-server ~]$
And I see comforting feedback in the log:
Binding to TCP port 5000 on host 127.0.0.1 with IPv4
[411034] 2023-11-14 22:52:00 warn App::Netdisco 2.069000 web
[411035] 2023-11-14 22:52:00 warn App::Netdisco 2.069000 web
[411038] 2023-11-14 22:52:00 warn App::Netdisco 2.069000 web
[411037] 2023-11-14 22:52:00 warn App::Netdisco 2.069000 web
[411036] 2023-11-14 22:52:00 warn App::Netdisco 2.069000 web
2023/11/15-09:39:01 Server closing!
2023/11/15-09:39:14 Starman::Server (type Net::Server::PreFork) starting!
pid(445758)
Resolved [ganesh]:5000 to [10.1.2.3]:5000, IPv4
Binding to TCP port 5000 on host 10.1.2.3with IPv4
[445760] 2023-11-15 17:39:14 warn App::Netdisco 2.069000 web
[445759] 2023-11-15 17:39:14 warn App::Netdisco 2.069000 web
[445761] 2023-11-15 17:39:14 warn App::Netdisco 2.069000 web
[445762] 2023-11-15 17:39:14 warn App::Netdisco 2.069000 web
[445763] 2023-11-15 17:39:14 warn App::Netdisco 2.069000 web
And I can point a browser at the appropriate hostname and get in fine:
[cid:image001.png@01DA17A9.AC98D520]
How does netdisco-web figure out what IP address to bind to?
--sk
Stuart Kendrick
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
