Send netdisco-users mailing list submissions to
[email protected]
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
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:
1. Re: Backend stopping, errors (Oliver Gorwits)
--- Begin Message ---
Hi Linwood
I wonder if Netdisco is failing to connect to the devices and blocking
them (using its device skip logic) for a week, until it will try again.
Restarting does cause Netdisco to try once more. This seems to describe
your behaviour well.
https://github.com/netdisco/netdisco/wiki/Job-Queue#skip-hints
At the moment you can't tell what devices are skipped in the web
interface job queue, but there is an Admin report "SNMP Connect
Failures". There is also a device_skip table in the database which
should be straightforward to inspect - looks for rows with the IP that
is not being discovered.
Are you able to take a look at those tables?
regards,
oliver.
On 2018-04-19 01:16, [email protected] wrote:
It stopped processing again, but pulling the detail did not give me
anything I can see as relevant. Below is what I got, and everything
just says idle.
The symptoms at the time were that a job would just go into the queue;
it never gave an error, it never completed. I could delete it (it
would be removed from the display), I would click discover on the
hosts' main page, it went back into the queue, but never processed. I
confirmed via snmpwalk connectivity.
In the log file at the time were the sorts of errors I the original
posting, i.e. the unitialized variables and MIB search error, nothing
more.
On restarting the daemon it returned to processing just fine, and
instantly (this is not a busy system at all, a discover all completes
almost everything in seconds, I think there are a couple devices that
take about 1-3 minutes because they are really slow with a lot of
ports). It looks more like the scheduler is not scheduling, than that
something is hung.
This is still 2.39.17; I saw the note that a new version is out, I
want to finish some other stuff and will likely be able to test it
tomorrow (re the LLDP changes, but who knows, might affect this).
Any ideas? Happy to collect datat when it hangs, but as before it's
unpredictable when it will.
Linwood
root@xxxxxx:~# ps -AF | grep netd
netdisco 1815 1 0 15187 16216 15 09:46 ? 00:00:06 netdisco-backend
netdisco 1817 1815 0 36174 45036 9 09:46 ? 00:00:02 nd2: master
netdisco 1881 1817 0 65761 75472 3 09:46 ? 00:00:00 nd2: #1 sched:
idle
netdisco 1882 1817 0 65286 75476 9 09:46 ? 00:00:42 nd2: #2 mgr: idle
postgres 2089 1813 0 413579 32876 10 09:46 ? 00:00:14 postgres:
netdisco netdisco ::1(39428) idle
postgres 9417 1813 0 413031 22808 3 09:50 ? 00:00:00 postgres:
netdisco netdisco ::1(41326) idle
root 26425 24610 0 3556 1028 13 17:45 pts/0 00:00:00 grep
--color=auto netd
postgres 170373 1813 0 413426 29680 7 16:41 ? 00:00:01 postgres:
netdisco netdisco ::1(49200) idle
postgres 170550 1813 0 413355 25392 0 16:41 ? 00:00:01 postgres:
netdisco netdisco ::1(49226) idle
postgres 170867 1813 0 413341 25932 14 16:41 ? 00:00:01 postgres:
netdisco netdisco ::1(49288) idle
postgres 170919 1813 0 413381 27892 7 16:41 ? 00:00:01 postgres:
netdisco netdisco ::1(49304) idle
postgres 171173 1813 0 413800 35060 7 16:42 ? 00:00:00 postgres:
netdisco netdisco ::1(49354) idle
postgres 171407 1813 0 413430 27584 10 16:42 ? 00:00:01 postgres:
netdisco netdisco ::1(49392) idle
postgres 171434 1813 0 413860 35192 7 16:42 ? 00:00:01 postgres:
netdisco netdisco ::1(49398) idle
postgres 171716 1813 0 413373 26920 7 16:42 ? 00:00:01 postgres:
netdisco netdisco ::1(49452) idle
postgres 174880 1813 0 413850 35452 1 16:44 ? 00:00:01 postgres:
netdisco netdisco ::1(50236) idle
postgres 175365 1813 0 413978 37428 7 16:44 ? 00:00:01 postgres:
netdisco netdisco ::1(50370) idle
netdisco 232854 1817 0 36604 45320 0 17:20 ? 00:00:00 nd2: #16 poll:
idle
netdisco 232856 1817 0 36605 45248 0 17:20 ? 00:00:00 nd2: #9 poll:
idle
netdisco 232857 1817 0 36605 45248 0 17:20 ? 00:00:00 nd2: #13 poll:
idle
netdisco 232858 1817 0 36605 45248 15 17:20 ? 00:00:00 nd2: #25 poll:
idle
netdisco 232874 1817 0 36603 45324 9 17:20 ? 00:00:00 nd2: #7 poll:
idle
netdisco 232876 1817 0 36603 45328 11 17:20 ? 00:00:00 nd2: #8 poll:
idle
netdisco 232880 1817 0 36603 45328 7 17:20 ? 00:00:00 nd2: #10 poll:
idle
netdisco 232881 1817 0 36603 45328 0 17:20 ? 00:00:00 nd2: #26 poll:
idle
netdisco 232884 1817 0 36603 45324 0 17:20 ? 00:00:00 nd2: #19 poll:
idle
netdisco 232888 1817 0 36603 45324 13 17:20 ? 00:00:00 nd2: #24 poll:
idle
netdisco 232889 1817 0 36603 45332 14 17:20 ? 00:00:00 nd2: #31 poll:
idle
netdisco 232890 1817 0 36603 45328 5 17:20 ? 00:00:00 nd2: #3 poll:
idle
netdisco 232891 1817 0 36603 45340 1 17:20 ? 00:00:00 nd2: #30 poll:
idle
netdisco 232892 1817 0 36603 45328 11 17:20 ? 00:00:00 nd2: #34 poll:
idle
netdisco 232893 1817 0 36603 45328 12 17:20 ? 00:00:00 nd2: #21 poll:
idle
netdisco 232894 1817 0 36603 45332 3 17:20 ? 00:00:00 nd2: #17 poll:
idle
netdisco 232921 1817 0 36603 45328 11 17:20 ? 00:00:00 nd2: #27 poll:
idle
netdisco 232922 1817 0 36603 45328 11 17:20 ? 00:00:00 nd2: #14 poll:
idle
netdisco 232923 1817 0 36603 45328 11 17:20 ? 00:00:00 nd2: #29 poll:
idle
netdisco 232924 1817 0 36603 45324 12 17:20 ? 00:00:00 nd2: #33 poll:
idle
netdisco 232925 1817 0 36603 45324 11 17:20 ? 00:00:00 nd2: #11 poll:
idle
netdisco 232926 1817 0 36603 45324 12 17:20 ? 00:00:00 nd2: #15 poll:
idle
netdisco 232927 1817 0 36603 45328 11 17:20 ? 00:00:00 nd2: #6 poll:
idle
netdisco 232928 1817 0 36603 45328 12 17:20 ? 00:00:00 nd2: #18 poll:
idle
netdisco 232929 1817 0 36603 45324 11 17:20 ? 00:00:00 nd2: #4 poll:
idle
netdisco 233095 1817 0 36603 45328 12 17:20 ? 00:00:00 nd2: #32 poll:
idle
netdisco 233119 1817 0 36603 45324 11 17:20 ? 00:00:00 nd2: #12 poll:
idle
netdisco 233418 1817 0 36605 45332 11 17:21 ? 00:00:00 nd2: #20 poll:
idle
netdisco 233430 1817 0 36605 45332 11 17:21 ? 00:00:00 nd2: #23 poll:
idle
netdisco 233431 1817 0 36605 45336 12 17:21 ? 00:00:00 nd2: #5 poll:
idle
netdisco 233593 1817 0 36605 45332 11 17:21 ? 00:00:00 nd2: #22 poll:
idle
netdisco 235091 1817 0 36605 45336 11 17:22 ? 00:00:00 nd2: #28 poll:
idle
-----Original Message-----
From: Oliver Gorwits [mailto:[email protected]]
Sent: Saturday, April 7, 2018 7:18 PM
To: [email protected]
Subject: Re: [Netdisco] Backend stopping, errors
Sorry Linwood, I forgot to mention... if you find the backend is
stalling again, please can you look at the process table for the
system and see what the nd2 entries are doing?
For example "ps aux".
There should be useful information in the process listing on the
manager, scheduler, and workers. In particular there should be a
"manager" or "mgr" process running which is handling the queues.
regards,
oliver.
On 2018-04-06 20:17, [email protected] wrote:
> Running 2.39.17, snmp 3.52, db 51, perl 5.22.1, on Ubuntu 16.04.6.
>
> A couple times now at unpredictable times I have had the backend
stop
> processing, though the service is running.
>
> I don't see starts and stops in the log so I'm struggling a bit to
> know what errors correspond to the actual issues, but I see
thousands
> of these:
>
> Use of uninitialized value $args{"mac"} in pattern match (m//) at
> /home/netdisco/perl5/lib/perl5/NetAddr/MAC.pm line 128,
<__ANONIO__>
> line 1.
>
> Use of uninitialized value $node in sprintf at
> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/Node.pm line 74,
> <__ANONIO__> line 1.
>
> M
>
> And also quite a few though less of these (below), which may be
> related to DLINK? And I have some DLINK's.
>
> Not sure if either of these relate to it stopping. It stops rarely,
> running days between, so leaving debug on the whole time is not an
> attractive option due to log size. Any simple way to tell what's
> happening absent something definitive in the log?
>
> By the way the symptom is that jobs just stay queued, and do not
> process, and do not receive errors. A service restart runs them all
> almost instantly.
>
> Linwood
>
> Cannot find module (AGENT-GENERAL-MIB): At line 1 in (none)
>
> MIB search path:
>
/home/netdisco/netdisco-mibs/3com:/home/netdisco/netdisco-mibs/adtran:/home/netdisco/netdisco-mibs/aerohive:/home/netdisco/netdisco-mibs/alcatel:/home/netdisco/netdisco-mibs/allied:/home/netdisco/netdisco-mibs/apc:/home/netdisco/netdisco-mibs/arista:/home/netdisco/netdisco-mibs/aruba:/home/netdisco/netdisco-mibs/asante:/home/netdisco/netdisco-mibs/avaya:/home/netdisco/netdisco-mibs/bluecoat:/home/netdisco/netdisco-mibs/bluesocket:/home/netdisco/netdisco-mibs/brother:/home/netdisco/netdisco-mibs/cabletron:/home/netdisco/netdisco-mibs/checkpoint:/home/netdisco/netdisco-mibs/cisco:/home/netdisco/netdisco-mibs/ciscosb:/home/netdisco/netdisco-mibs/citrix:/home/netdisco/netdisco-mibs/colubris:/home/netdisco/netdisco-mibs/cyclades:/home/netdisco/netdisco-mibs/d-link:/home/netdisco/netdisco-mibs/dell:/home/netdisco/netdisco-mibs/enterasys:/home/netdisco/netdisco-mibs/EXTRAS:/home/netdisco/netdisco-mibs/extreme:/home/netdisco/netdisco-mibs/extricom:/home/netdisco/netdisco-mibs/f5:/home/netdis
co/netdisco-mibs/force10:/home/netdisco/netdisco-mibs/fortinet:/home/netdisco/netdisco-mibs/foundry:/home/netdisco/netdisco-mibs/gigamon:/home/netdisco/netdisco-mibs/h3c:/home/netdisco/netdisco-mibs/hp:/home/netdisco/netdisco-mibs/huawei:/home/netdisco/netdisco-mibs/ibm:/home/netdisco/netdisco-mibs/juniper:/home/netdisco/netdisco-mibs/lancom:/home/netdisco/netdisco-mibs/lantronix:/home/netdisco/netdisco-mibs/liebert:/home/netdisco/netdisco-mibs/mediant:/home/netdisco/netdisco-mibs/meraki:/home/netdisco/netdisco-mibs/meru:/home/netdisco/netdisco-mibs/mikrotik:/home/netdisco/netdisco-mibs/moser-baer:/home/netdisco/netdisco-mibs/motorola:/home/netdisco/netdisco-mibs/net-snmp:/home/netdisco/netdisco-mibs/netapp:/home/netdisco/netdisco-mibs/netgear:/home/netdisco/netdisco-mibs/netscreen:/home/netdisco/netdisco-mibs/nexans:/home/netdisco/netdisco-mibs/nortel:/home/netdisco/netdisco-mibs/northerndesign:/home/netdisco/netdisco-mibs/opengear:/home/netdisco/netdisco-mibs/packetfront:/home/netd
isco/netdisco-mibs/paloalto:/home/netdisco/netdisco-mibs/pica8:/home/netdisco/netdisco-mibs/rad:/home/netdisco/netdisco-mibs/rfc:/home/netdisco/netdisco-mibs/riverbed:/home/netdisco/netdisco-mibs/ruckus:/home/netdisco/netdisco-mibs/schleifenbauer:/home/netdisco/netdisco-mibs/sentry:/home/netdisco/netdisco-mibs/sixnet:/home/netdisco/netdisco-mibs/sonicwall:/home/netdisco/netdisco-mibs/tplink:/home/netdisco/netdisco-mibs/trapeze:/home/netdisco/netdisco-mibs/vmware:/home/netdisco/netdisco-mibs/xirrus
>
>
>
>
----------------------------------------------------------------------
> -------- Check out the vibrant tech community on one of the world's
> most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
[1]
>
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/ [2]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot [1]
_______________________________________________
Netdisco mailing list
[email protected]
https://sourceforge.net/p/netdisco/mailman/netdisco-users/ [2]
Links:
------
[1] http://sdm.link/slashdot
[2] https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
