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. Wifi Discovery or manual (Jacob Ghattas)
   2. Re: Arpwalk, Macsuck or Discover not successful on some
      devices (Charlie Butera)
   3. Re: Arpwalk, Macsuck or Discover not successful on some
      devices (Christian Ramseyer)
--- Begin Message ---
Greetings,

I have a netdisco instance installed and running..

One issue I currently have, is that the Wireless devices I use in my
network are (Extreme/Ex-Motorola/Zebra).
I don't know if it is related, but the Wireless reports is are showing "No
matching Records"
All of the Extreme devices and few other vendors, are showing as Vendor
Unknown.
I tried fixing the Extreme issue, but it seems I am doing something wrong,
or not totally understanding the system architecture for having it done.
Any help would be appreciated or redirection to a manual...

Btw, it's a great system!!! Thanks for all the contributors.

Jacob

--- End Message ---
--- Begin Message ---
Hey Christian,

Thanks for the help, I dropped down to a single poller and it seemed to fix
the issue until I upgraded some equipment which ended up then stuck
in queued status.

netdisco_service=# select * from admin where finished is NULL and device =
'192.168.1.10';
   job   |          entered           | started | finished |  device  |
port |  action  | subaction | status | username | userip | log | debug |
device_key
---------+----------------------------+---------+----------+----------+------+----------+-----------+--------+----------+--------+-----+-------+------------
 1371329 | 2019-10-02 01:50:32.449339 |         |          | 192.168.1.10 |
     | arpnip   |           | queued |          |        |     |       |
 1375580 | 2019-10-02 03:00:36.396481 |         |          | 192.168.1.10 |
     | discover |           | queued |          |        |     |       |

I added the following as a cronjob, which seems to have fixed both issues.
./bin/netdisco-do psql -e 'DELETE FROM admin WHERE finished IS NULL'

Is there not some expire job that runs automatically to clear stuck jobs?




*Charles Butera*

*Network Engineer*

[email protected] <[email protected]>

Squarespace

Squarespace.com


On Tue, Sep 24, 2019 at 9:53 AM Christian Ramseyer <[email protected]>
wrote:

>
>
> On 23.09.19 16:52, Charlie Butera wrote:
> > Christian,
> >
> > Definitely making progress! so for all jobs that are not working the
> > last job in the admin table shows the job being queued on a host.
> > One thing to note is that I had/have 2 netdisco hosts running both the
> > frontend and the backend service with a separate host running the
> database.
> > I have disabled one of the 2 frontend/backend netdisco hosts for the
> > time being to troubleshoot this issue but it seems the issue is somehow
> > related to my deployment setup.
>
> Cool, at least we're getting somewhere. Let us know if that makes the
> polling work normally again. You might have to delete the stuck entries
> from the admin queue:
>
> delete from admin where device = '<ip>'
>
> or you can also just nuke the whole queue to start over:
>
> delete from admin
>
>
> There might be some bugs with multiple pollers that nobody discovered
> yet. If you manage to reproduce stuck jobs we really appreciate if you
> drop us the details here or raise an issue at
> https://github.com/netdisco/netdisco/issues.
>
> Cheers
> Christian
>

--- End Message ---
--- Begin Message ---

On 03.10.19 16:43, Charlie Butera wrote:
       |
> 
> I added the following as a cronjob, which seems to have fixed both issues.
> ./bin/netdisco-do psql -e 'DELETE FROM admin WHERE finished IS NULL'
> 
> Is there not some expire job that runs automatically to clear stuck jobs?
> 
> 

Yes there is, but the default setting is quite long, 14 days:
https://github.com/netdisco/netdisco/wiki/Configuration#expire_jobs





--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to