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. AUTO : Jos? Cordeiro est ? l'ext?rieur du bureau (retour
2014-08-25) ([email protected])
2. VLANs 1002-1005 (Panagiotis Papaspyropoulos)
3. Re: VLANs 1002-1005 (Oliver Gorwits)
4. Issue After Update (William Jones)
5. Re: Upgrade from version App::Netdisco 2.028000 to 2.028012
(Oliver Gorwits)
6. Re: Issue After Update (Oliver Gorwits)
7. Netdisco stopped working all of a sudden - DBI
connect('dbname=netdisco', 'netdisco', ...) failed: FATAL:
database is not accepting commands to avoid wraparound data
(RYAN Justin)
--- Begin Message ---
Je suis absent(e) du bureau jusqu'au 2014-08-25
Bonjour
Je suis présentement à l'extérieur du bureau. Pour toutes informations
urgentes, svp contacter M. Leclerc au 26162 ou M. Daigle au 28882.
Concernant des interventions réseau, M. Gorodko au 25154.
Merci
Remarque : ceci est une réponse automatique à votre message
"netdisco-users Digest, Vol 97, Issue 8" envoyé le 2014-07-26 08:21:13.
C'est la seule notification que vous recevrez pendant l'absence de cette
personne.
--- End Message ---
--- Begin Message ---
Hello,
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.
Panos
--- End Message ---
--- Begin Message ---
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 ---
Hi all,
I recently installed the latest version of Netdisco (2.028012) and I'm
seeing some strange behavior. I ran a full discovery and for the most
part, everything seemed to work. But then I noticed that there were some
discover jobs (only 9 out of a large amount) in the queue that were not
completing and were just alternating between "running on ..." and "queued"
over and over again and they just wouldn't complete. I left them for a
very long time with no change.
The daemon was still running at that time. I then restarted the daemon and
expected the jobs to kick off, which they attempted to, but then the daemon
crashed and I saw the following in the log:
[2183] 2014-07-24 02:07:01 warn App::Netdisco 2.028012 backend
DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::SQLite::st
execute failed: UNIQUE constraint failed: admin.job [for Statement "INSERT
INTO admin ( action, debug, device, entered, finished, job, log, port,
started, status, subaction, type, userip, username) VALUES ( ?, ?, ?, ?, ?,
?, ?, ?, ?, ?, ?, ?, ?, ? )"] at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Daemon/LocalQueue.pm line 17
## netdisco-daemon-fg: caught signal '__DIE__', exiting
As you can see, this killed the daemon and the jobs were still left in
"running on" state in the web app.
I've tried restarting the daemon a few times, but I still see the same
behavior. It starts up, tries running the jobs and then gets that error
and the daemon stops running.
I did see the same error message posted recently by someone else in the
list who had just updated, but I believe it was stated that it can be
safely ignored. Seeing this behavior, I'm not sure that's the case.
Here's my system info in case it is needed:
App::Netdisco: 2.028012
DB Schema: v38
Dancer: 1.3126
Bootstrap: 2.3.1
PostgreSQL: PostgreSQL 9.3.4 on x86_64-redhat-linux-gnu, compiled by gcc
(GCC) 4.8.2 20131212 (Red Hat 4.8.2-7), 64-bit. DBI 1.63, DBD::Pg 2.19.3
SNMP::Info: 3.18
Perl: 5.018002
52 devices with 1,144 interfaces using 259 IPs
107 layer 2 links between devices
1,435 nodes in 2,702 entries
1,665 IPs in 1,665 entries
If additional info is needed, please let me know.
Any help would be greatly appreciated. Thanks!
--- End Message ---
--- Begin Message ---
Hi Geert,
The version is printed by the web and poller daemons to the log when
they start, and is also available in the Web interface under "system
information" on the homepage.
Are you sure you restarted the daemons? Did you do all these steps as
the "netdisco" user?
regards,
oliver.
On 2014-07-26 12:57, geert wrote:
Hi
I want to upgrade from 2.028000 to 2.028012 by executing the
following, but the version stays on 2.028000
# upgrade Netdisco
~/bin/localenv cpanm --notest App::Netdisco
# apply database schema updates
~/bin/netdisco-deploy
# restart web service
~/bin/netdisco-web restart
# restart job daemon (if you use it)
~/bin/netdisco-daemon restart
Regards
Geert
--- End Message ---
--- Begin Message ---
Hi,
Thanks for the bug report - we'll look into it.
A workaround for you to get out of this situation is to start the web
frontend but not the poller backend. In the web interface, go to Admin
-> Job Queue and click the bin icon to empty the queue. Then you can
start the backend. It will then proceed as normal with the next
scheduled jobs.
regards,
oliver.
On 2014-07-24 03:57, William Jones wrote:
Hi all,
I recently installed the latest version of Netdisco (2.028012) and
I'm
seeing some strange behavior. I ran a full discovery and for the
most part, everything seemed to work. But then I noticed that there
were some discover jobs (only 9 out of a large amount) in the queue
that were not completing and were just alternating between "running
on
..." and "queued" over and over again and they just wouldn't
complete.
I left them for a very long time with no change.
The daemon was still running at that time. I then restarted the
daemon and expected the jobs to kick off, which they attempted to,
but
then the daemon crashed and I saw the following in the log:
[2183] 2014-07-24 02:07:01 warn App::Netdisco 2.028012 backend
DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception:
DBD::SQLite::st execute failed: UNIQUE constraint failed: admin.job
[for Statement "INSERT INTO admin ( action, debug, device, entered,
finished, job, log, port, started, status, subaction, type, userip,
username) VALUES ( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ? )"] at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Daemon/LocalQueue.pm line
17
## netdisco-daemon-fg: caught signal '__DIE__', exiting
As you can see, this killed the daemon and the jobs were still left
in
"running on" state in the web app.
I've tried restarting the daemon a few times, but I still see the
same
behavior. It starts up, tries running the jobs and then gets that
error and the daemon stops running.
I did see the same error message posted recently by someone else in
the list who had just updated, but I believe it was stated that it
can
be safely ignored. Seeing this behavior, I'm not sure that's the
case.
Here's my system info in case it is needed:
App::Netdisco: 2.028012
DB Schema: v38
Dancer: 1.3126
Bootstrap: 2.3.1
PostgreSQL: PostgreSQL 9.3.4 on x86_64-redhat-linux-gnu, compiled by
gcc (GCC) 4.8.2 20131212 (Red Hat 4.8.2-7), 64-bit. DBI 1.63, DBD::Pg
2.19.3
SNMP::Info: 3.18
Perl: 5.018002
52 devices with 1,144 interfaces using 259 IPs
107 layer 2 links between devices
1,435 nodes in 2,702 entries
1,665 IPs in 1,665 entries
If additional info is needed, please let me know.
Any help would be greatly appreciated. Thanks!
--- End Message ---
--- Begin Message ---
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
--- 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
