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: Issues with netdisco and postgresql (Oliver Gorwits)
--- Begin Message ---
>
> All you can really do is distribute collection, spread out timed jobs
Yes, it's worth looking into the features we have... you can run multiple
backends (restricted to certain device IPs if you wish, or not), you can
spread out the polling by having different arpwalk/etc commands limited to
certain device IPs, and of course simply alter the number of pollers on the
backend.
Similar to Mike I would be interested to hear examples of how people have
used these features (I do know that distributed backends has been helpful
to those running global networks, to have the SNMP happen locally and DB
data sent over the WAN back home) -- and any tips for DB scaling as that
becomes the central bottleneck for it all.
Thanks,
On Sat, 6 Nov 2021 at 07:11, Michael Butash <mich...@butash.net> wrote:
> Do you have a lot of fex or stack switch ports? With ciscos I always
> notice vss/stack/fex's are terribly slow in returning snmp data and put
> huge delays into them having to remote query cluster devices with enough
> they'll back monitoring up. I've seen this in bigger environments when
> polling a lot of pseudo-devices like those, particularly remotely a few
> states away over vpn. I find these often good reasons not to use
> vss/stack/fex's, and seen enough tools conversely also impact (ie crash)
> the devices adversely from over-polling. Hell, last asr1000 I pointed
> netdisco at began causing 100% cpu, never underestimate vendor
> bugs/stupidity.
>
> All you can really do is distribute collection, spread out timed jobs, or
> squeeze performance out of the app/db themselves debugging the box. Check
> iotop and db tools for performance bottlenecks too.
>
> I'd be curious what a scale out model of netdisco would look like for
> large/huge environments if distributed layers of collection, database,
> graphic ui's, etc, but never needed to.
>
> -mb
>
>
> On Fri, Nov 5, 2021 at 9:01 PM Muris <alcat...@gmail.com> wrote:
>
>> Hi Trent, thanks for that.
>>
>>
>>
>> What I found out was, because the environment is so big, the arpnips and
>> macsucks are overlapping, I have them on a hourly basis..so I don’t think
>> they finishing on time... so I have separated them out by 2 – 3 hours now..
>> and it seems to be working a lot better. When arpnips/macsucks are running
>> seems to use 90-100% cpu.. and then web requests can timeout looking up
>> things.
>>
>>
>>
>> Will checkout the vacuum things too.
>>
>>
>>
>> Muris
>>
>>
>>
>> *From: *Trent Curtis <trent.cur...@gmail.com>
>> *Date: *Thursday, 4 November 2021 at 22:07
>> *To: *Dominik Müller <mue...@t-online.de>
>> *Cc: *<netdisco-users@lists.sourceforge.net>
>> *Subject: *Re: [Netdisco] Issues with netdisco and postgresql
>>
>>
>>
>> I would suggest stopping services, restarting postgres, and performing a
>> full database vacuum, and potentially clearing the admin table.
>>
>>
>>
>> 1. Sudo as netdisco and Stop Netdisco-backend and Netdisco-web:
>>
>> ~/bin/netdisco-backend stop
>>
>> ~/bin/netdisco-web stop
>>
>>
>>
>> 2. Restart postgres service per your distro instructions.
>>
>>
>>
>> 3. Sudo as postgres user and execute:
>>
>> psql netdisco
>>
>> set statement_timeout=0;
>>
>> vacuum full;
>>
>>
>>
>> The vacuum will take a while depending on the table sizes. I'd suggest
>> also making the pgtune tweaks if you have not already. It would also good
>> to take a look at your postgres logs to see if the vacuum is actually
>> running. Another tip would be to clear the admin table all together to
>> clear any schedule backlogs, this could be one of the culprits of the
>> slowness.
>>
>>
>>
>> To clear the admin queue, sudo as netdisco and execute:
>>
>> ~/bin/netdisco-do psql -e "DELETE FROM admin;"
>>
>>
>>
>> Also please share your schedule config from the deployment.yml file.
>> Ultimately you want to avoid any job overlaps to prevent scheduling
>> backlogs.
>>
>>
>>
>> Hope this helps.
>>
>>
>>
>> - Trent
>>
>>
>>
>> On Thu, Nov 4, 2021, 1:21 AM Dominik Müller <mue...@t-online.de> wrote:
>>
>> Hi,
>>
>>
>>
>> sounds like there is a constant writing on your db.
>>
>> How often do you discover your Network?
>>
>>
>>
>> BR
>>
>>
>>
>> Dominik
>>
>>
>>
>> Am 04.11.2021 um 04:47 schrieb Kurt Buff <kurt.b...@gmail.com>:
>>
>>
>>
>> A pure guess - is the vacuum running?
>>
>> https://www.postgresql.org/docs/9.1/sql-vacuum.html
>>
>>
>>
>> Kurt
>>
>>
>>
>> On Wed, Nov 3, 2021 at 7:55 AM Muris <alcat...@gmail.com> wrote:
>>
>> Hi All,
>>
>>
>>
>> I have a bit of a problem where netdisco database seems to have stopped
>> working and lookups from web interface I have tried to restart postgresql
>> and netdisco-web and netdisco-backend helps a bit but then starts happening
>> again
>>
>>
>>
>> The database is very slow to access looking at items through the web
>> interface, and looking up a device comes up with “Search failed! Please
>> contact your site administrator (server error).”
>>
>>
>>
>> Netdisco-backend and netdisco-log don’t show any errors, so I think its
>> something postgresql related that’s not going right…
>>
>>
>>
>> I then stop netdisco-web and netdisco-backend and theres this “postgres :
>> checkpointer” that constantly hangs around and takes cpu
>>
>>
>>
>> What can I do to fix it or see whats going on with postgres?
>>
>>
>>
>> Thanks
>>
>> Muris
>>
>> _______________________________________________
>> Netdisco mailing list
>> netdisco-users@lists.sourceforge.net
>> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>>
>> _______________________________________________
>> Netdisco mailing list
>> netdisco-users@lists.sourceforge.net
>> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>>
>> _______________________________________________
>> Netdisco mailing list
>> netdisco-users@lists.sourceforge.net
>> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>>
>> _______________________________________________
>> Netdisco mailing list
>> netdisco-users@lists.sourceforge.net
>> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
>
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://sourceforge.net/p/netdisco/mailman/netdisco-users/
--- End Message ---
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
