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: VLANs 1002-1005 (Panagiotis Papaspyropoulos)
2. Re: Netdisco stopped working all of a sudden - DBI
connect('dbname=netdisco', 'netdisco', ...) failed: FATAL:
database is not accepting commands to avoid wraparound data
(Joseph Bernard)
3. Re: Netdisco stopped working all of a sudden - DBI
connect('dbname=netdisco', 'netdisco', ...) failed: FATAL:
database is not accepting commands to avoid wraparound data
(Robert Kerr)
4. Node not appearing in search (Jonathan Woodard)
5. Possible to set BulkRepeaters? (Rune Thorsplass)
6. Re: Node not appearing in search (Jonathan Woodard)
--- Begin Message ---
Hey Oliver,
I know these VLANs exist in the switches by default, I just don't remember
seeing them in the VLAN inventory in versions 0.26 and 0.27. I thought
Netdisco was ignoring them already and it was somehow changed in the
current version. Maybe they were in page 2 and I never saw them. Thanks for
the reply :) .
> From: Oliver Gorwits <oli...@cpan.org>
> To: <netdisco-users@lists.sourceforge.net>
> Cc:
> Date: Mon, 28 Jul 2014 10:18:57 +0100
> Subject: Re: [Netdisco] VLANs 1002-1005
> Hi Panos,
>
> On 2014-07-28 08:30, Panagiotis Papaspyropoulos wrote:
>>
>> After upgrading ND2 to v2.0.28, VLANs 1002-1005 appear in my VLAN
>> inventory, although there are no ports assigned on them. Is this a new
>> feature or a bug in my installation? Is there any way to ignore them?
>> The switches are all Catalyst 2950 and 2960.
>
>
> These VLANs exist on many Cisco platforms, here's a page which explains
why:
>
>
http://etherealmind.com/cisco-ios-vlan-1002-reserved-1005-purpose-function/
>
> Netdisco doesn't Macsuck from these VLANs but they will be included in
the VLAN inventory. We could have a configuration item to filter them out
(ignore_vlans just like ignore_interfaces) - does anyone have an opinion on
that?
>
> I'll also try to take a look at what Netdisco 1 did, as presumably it
skips them somehow.
>
> regards,
> oliver.
>
--- End Message ---
--- Begin Message ---
Have you checked to make sure your hard drive isn’t full?
Thanks,
Joseph B.
On Jul 28, 2014, at 11:22 AM, RYAN Justin <j.r...@phoenixmedical.co.uk> wrote:
> Hi I've had a netdisco instance running for a few years now (pre 2011)
> Version 1.0
> Built on centos 5 has been rock solid.
> However a few days ago I tried logging into web interface to get a error 500
> internal server error
>
> Internal Server Error
>
> The server encountered an internal error or misconfiguration and was unable
> to complete your request.
>
> Please contact the server administrator, root@localhost and inform them of
> the time the error occurred, and anything you might have done that may have
> caused the error.
>
> More information about this error may be available in the server error log.
> Apache/2.2.3 (CentOS) Server at 10.200.7.206 Port 80
>
> When I try and do a manual discovery /usr/sbin/netdisco -r IP
>
> I get the following error
>
> n e t d i s c o
> --------------------------------------------------
> Network discovery starting from root *.*(.*(.* at Mon Jul 28 11:26:36 2014
> DBI connect('dbname=netdisco','netdisco',...) failed: FATAL: database is not
> accepting commands to avoid wraparound data
> loss in database "postgres"
> HINT: Stop the postmaster and use a standalone backend to vacuum database
> "postgres".
> at /usr/lib/perl5/vendor_perl/5.8.8/netdisco.pm line 1432
> Can't connect to DB. FATAL: database is not accepting commands to avoid
> wraparound data loss in database "postgres"
> HINT: Stop the postmaster and use a standalone backend to vacuum database
> "postgres".
>
>
> Postgress is running btw
>
> Can someone help me fix it. I would like to retain the data for historical
> reasons.
>
>
>
>
>
>
> PRIVACY & CONFIDENTIALITY
>
> This e-mail is private and confidential. If you have, or suspect you have
> received this message in error please notify the sender as soon as possible
> and remove from your system. You may not copy, distribute or take any action
> in reliance on it. Thank you for your co-operation.
>
> Please note that whilst best efforts are made, neither the company nor the
> sender accepts any responsibility for viruses and it is your responsibility
> to scan the email and attachments (if any).
>
> This e-mail has been automatically scanned for viruses by Proofpoint (Inc.)
> Enterprise Protection for Email Security services.
>
> PHOENIX Healthcare Distribution Ltd. Reg. in England No. 129370
> PHOENIX Medical Supplies Ltd. Reg. in England No. 3603234
> Rivington Road, Whitehouse Ind. Est., Runcorn, Cheshire, WA7 3DJ
> VAT No. 741706443
>
> ------------------------------------------------------------------------------
> Infragistics Professional
> Build stunning WinForms apps today!
> Reboot your WinForms applications with our WinForms controls.
> Build a bridge from your legacy apps to the future.
> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
> _______________________________________________
> Netdisco mailing list
> netdisco-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
On 28/07/14 16:22, RYAN Justin wrote:
> I get the following error
> n e t d i s c o --------------------------------------------------
> Network discovery starting from root *.*(.*(.* at Mon Jul 28
> 11:26:36 2014 DBI connect('dbname=netdisco','netdisco',...) failed:
> FATAL: database
is not accepting commands to avoid wraparound data loss in database
"postgres"
> HINT: Stop the postmaster and use a standalone backend to vacuum
database "postgres".
> at /usr/lib/perl5/vendor_perl/5.8.8/netdisco.pm line 1432 Can't
> connect to DB. FATAL: database is not accepting commands to
avoid wraparound data loss in database "postgres"
> HINT: Stop the postmaster and use a standalone backend to vacuum
database "postgres".
This is an issue with postgres - I'm guessing you're running a really
old version or don't have auto-vacuum enable in the config for some
reason. Try this procedure:
http://chrishood.typepad.com/blog/2009/05/postgresql-fatal-database-is-not-accepting-commands-to-avoid-wraparound.html
--
Robert Kerr
--- End Message ---
--- Begin Message ---
I did a test install of netdisco v2 recently and I love it. I am a VOIP admin
and I use it to run down IP phones that have been plugged in. When I did a new
install on its permanent home, I am now not able to search nodes as the
previous install. Previously I was able to put in a phone's IP in a node
search and be able to track down the switch port.
Forgive me as I'm new to this and not sure totally how netdisco handles things.
but I'm looking for suggestions.
Also, it feels like I'm having to put more into discover than the previous
install. I remember doing maybe 3 at most but I'm having to compare and
manually put them in from initial install.
The install is less than 24hrs old but very close. Is it something I just
should give it more time?
--- End Message ---
--- Begin Message ---
Hi
I have problem with bulkwalk because of our MTU size in the WAN and I need to
set the MaxRepeaters for Bulkwalk to less than 10. Default in SNMP::Info are
20.
How to change this?
RuneT
--- End Message ---
--- Begin Message ---
Just wanted to post my fix. Thanks to those in IRC chat for the help. The
problem was that I was not able to SNMP my gateway. Once I added it and redid
an ARPNIP on everything then IP search worked.
From: Jonathan Woodard [mailto:jwood...@astate.edu]
Sent: Tuesday, July 29, 2014 9:34 AM
To: netdisco-users@lists.sourceforge.net
Subject: [Netdisco] Node not appearing in search
I did a test install of netdisco v2 recently and I love it. I am a VOIP admin
and I use it to run down IP phones that have been plugged in. When I did a new
install on its permanent home, I am now not able to search nodes as the
previous install. Previously I was able to put in a phone's IP in a node
search and be able to track down the switch port.
Forgive me as I'm new to this and not sure totally how netdisco handles things.
but I'm looking for suggestions.
Also, it feels like I'm having to put more into discover than the previous
install. I remember doing maybe 3 at most but I'm having to compare and
manually put them in from initial install.
The install is less than 24hrs old but very close. Is it something I just
should give it more time?
--- End Message ---
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls.
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Netdisco mailing list - Digest Mode
netdisco-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/netdisco-users
