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: thanks for your help! ([email protected])
2. Re: thanks for your help! (Oliver Gorwits)
3. errors in netdisco-daemon.log (Joseph Bernard)
4. Re: errors in netdisco-daemon.log (Oliver Gorwits)
5. Re: errors in netdisco-daemon.log (Joseph Bernard)
6. Re: ND2 strange node behaviour (Oliver Gorwits)
--- Begin Message ---
That's exactly what I mean -- we use a different port internally, and I wonder
if there's a file I can edit to change 5432 to 5XXX
-----Original Message-----
From: Oliver Gorwits [mailto:[email protected]]
Sent: Friday, April 11, 2014 2:32 AM
To: [email protected]
Subject: Re: [Netdisco] thanks for your help!
Hi Peter,
That's good news, thanks for letting us know (and thanks for persevering).
On 2014-04-10 22:39, [email protected] wrote:
> I got the application up and running; now I just need my network
> admins to populate it with data. Tell me - Can I change the port that
> netapp connects to postgres?
Just to clarify, do you mean an alternative to the default Pg port 5432 ?
regards,
oliver.
>
> Peter H Burris
>
> Network Services Division
>
> International Trade Commission
--- End Message ---
--- Begin Message ---
On 2014-04-17 23:05, [email protected] wrote:
That's exactly what I mean -- we use a different port internally, and
I wonder if there's a file I can edit to change 5432 to 5XXX
Yes, but you need to use the "host" config option, which I recall you
had trouble with, before?
Anyway, this will work:
database:
name: 'netdisco'
host: 'localhost;port=5432'
user: 'changeme'
pass: 'changeme'
When using the "host" option, MD5 auth should be enabled in the
database config:
https://metacpan.org/pod/App::Netdisco::Manual::Deployment#Enable-MD5-authentication-to-PostgreSQL
regards,
oliver.
-----Original Message-----
From: Oliver Gorwits [mailto:[email protected]]
Sent: Friday, April 11, 2014 2:32 AM
To: [email protected]
Subject: Re: [Netdisco] thanks for your help!
Hi Peter,
That's good news, thanks for letting us know (and thanks for
persevering).
On 2014-04-10 22:39, [email protected] wrote:
I got the application up and running; now I just need my network
admins to populate it with data. Tell me - Can I change the port
that
netapp connects to postgres?
Just to clarify, do you mean an alternative to the default Pg port
5432 ?
regards,
oliver.
Peter H Burris
Network Services Division
International Trade Commission
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
I've been getting errors in the netdisco-daemon.log as follows. I started
looking for errors when I noticed the Job Queue stopped progressing and found
that all the netdisco-daemon-fg processes had stopped running. It seems to be
happening less since upgrading to 2.026000 and SNMP::Info 3.13. Are the errors
correctable or normal?
Thanks,
Joseph B.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited abnormally
and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat
your command.
WARNING: terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back the
current transaction and exit, because another server process exited abnormally
and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and repeat
your command.
DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI
connect('dbname=netdisco','netdisco',...) failed: FATAL: the database system
is in recovery mode at /home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm
line 1483. at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Daemon/Worker/Manager.pm line 56
error closing job: DBIx::Class::Storage::DBI::catch {...} (): DBI Connection
failed: DBI connect('dbname=netdisco','netdisco',...) failed: FATAL: the
database system is in recovery mode at
/home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1483. at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Daemon/Worker/Common.pm line 73
error running job: DBIx::Class::Storage::DBI::catch {...} (): DBI Connection
failed: DBI connect('dbname=netdisco','netdisco',...) failed: FATAL: the
database system is in recovery mode at
/home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1483. at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/PortMAC.pm line 48
error closing job: DBIx::Class::Storage::DBI::catch {...} (): DBI Connection
failed: DBI connect('dbname=netdisco','netdisco',...) failed: FATAL: the
database system is in recovery mode at
/home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1483. at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Daemon/Worker/Common.pm line 73
--- End Message ---
--- Begin Message ---
Hi Joseph,
On 2014-04-18 13:47, Joseph Bernard wrote:
I've been getting errors in the netdisco-daemon.log as follows. I
started looking for errors when I noticed the Job Queue stopped
progressing and found that all the netdisco-daemon-fg processes had
stopped running. It seems to be happening less since upgrading to
2.026000 and SNMP::Info 3.13. Are the errors correctable or normal?
I'm not sure that these issues are coming from the Netdisco app
(although the app is picking up on them).
It seems like your PostgreSQL installation has some problems - perhaps
bad hardware or file corruption, or a buggy version. Can you upgrade to
a different PostgreSQL version, or try running the database on another
server?
regards,
oliver.
WARNING: terminating connection because of crash of another server
process
DETAIL: The postmaster has commanded this server process to roll
back the current transaction and exit, because another server process
exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database
and repeat your command.
WARNING: terminating connection because of crash of another server
process
DETAIL: The postmaster has commanded this server process to roll
back the current transaction and exit, because another server process
exited abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database
and repeat your command.
DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI
connect('dbname=netdisco','netdisco',...) failed: FATAL: the
database
system is in recovery mode at
/home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1483.
at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Daemon/Worker/Manager.pm
line 56
error closing job: DBIx::Class::Storage::DBI::catch {...} (): DBI
Connection failed: DBI connect('dbname=netdisco','netdisco',...)
failed: FATAL: the database system is in recovery mode at
/home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1483.
at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Daemon/Worker/Common.pm
line 73
error running job: DBIx::Class::Storage::DBI::catch {...} (): DBI
Connection failed: DBI connect('dbname=netdisco','netdisco',...)
failed: FATAL: the database system is in recovery mode at
/home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1483.
at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Util/PortMAC.pm line 48
error closing job: DBIx::Class::Storage::DBI::catch {...} (): DBI
Connection failed: DBI connect('dbname=netdisco','netdisco',...)
failed: FATAL: the database system is in recovery mode at
/home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1483.
at
/home/netdisco/perl5/lib/perl5/App/Netdisco/Daemon/Worker/Common.pm
line 73
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
I'm running PostrgreSQL 9.3.3 from their yum repository, but it looks like they
issued a 9.3.4 update. I'll try that and see how it goes.
Thanks,
Joseph B.
On Apr 18, 2014, at 11:50 AM, Oliver Gorwits <[email protected]> wrote:
> Hi Joseph,
>
> On 2014-04-18 13:47, Joseph Bernard wrote:
>> I've been getting errors in the netdisco-daemon.log as follows. I
>> started looking for errors when I noticed the Job Queue stopped
>> progressing and found that all the netdisco-daemon-fg processes had
>> stopped running. It seems to be happening less since upgrading to
>> 2.026000 and SNMP::Info 3.13. Are the errors correctable or normal?
>
> I'm not sure that these issues are coming from the Netdisco app
> (although the app is picking up on them).
>
> It seems like your PostgreSQL installation has some problems - perhaps
> bad hardware or file corruption, or a buggy version. Can you upgrade to
> a different PostgreSQL version, or try running the database on another
> server?
>
> regards,
> oliver.
>
>
>
>
>
>> WARNING: terminating connection because of crash of another server
>> process
>> DETAIL: The postmaster has commanded this server process to roll
>> back the current transaction and exit, because another server process
>> exited abnormally and possibly corrupted shared memory.
>> HINT: In a moment you should be able to reconnect to the database
>> and repeat your command.
>> WARNING: terminating connection because of crash of another server
>> process
>> DETAIL: The postmaster has commanded this server process to roll
>> back the current transaction and exit, because another server process
>> exited abnormally and possibly corrupted shared memory.
>> HINT: In a moment you should be able to reconnect to the database
>> and repeat your command.
>> DBIx::Class::Storage::DBI::catch {...} (): DBI Connection failed: DBI
>> connect('dbname=netdisco','netdisco',...) failed: FATAL: the
>> database
>> system is in recovery mode at
>> /home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1483.
>> at
>> /home/netdisco/perl5/lib/perl5/App/Netdisco/Daemon/Worker/Manager.pm
>> line 56
>> error closing job: DBIx::Class::Storage::DBI::catch {...} (): DBI
>> Connection failed: DBI connect('dbname=netdisco','netdisco',...)
>> failed: FATAL: the database system is in recovery mode at
>> /home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1483.
>> at
>> /home/netdisco/perl5/lib/perl5/App/Netdisco/Daemon/Worker/Common.pm
>> line 73
>>
>> error running job: DBIx::Class::Storage::DBI::catch {...} (): DBI
>> Connection failed: DBI connect('dbname=netdisco','netdisco',...)
>> failed: FATAL: the database system is in recovery mode at
>> /home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1483.
>> at
>> /home/netdisco/perl5/lib/perl5/App/Netdisco/Util/PortMAC.pm line 48
>>
>> error closing job: DBIx::Class::Storage::DBI::catch {...} (): DBI
>> Connection failed: DBI connect('dbname=netdisco','netdisco',...)
>> failed: FATAL: the database system is in recovery mode at
>> /home/netdisco/perl5/lib/perl5/DBIx/Class/Storage/DBI.pm line 1483.
>> at
>> /home/netdisco/perl5/lib/perl5/App/Netdisco/Daemon/Worker/Common.pm
>> line 73
>>
>> ------------------------------------------------------------------------------
>> Learn Graph Databases - Download FREE O'Reilly Book
>> "Graph Databases" is the definitive new guide to graph databases and
>> their
>> applications. Written by three acclaimed leaders in the field,
>> this first edition is now available. Download your free book today!
>> http://p.sf.net/sfu/NeoTech
>> _______________________________________________
>> Netdisco mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/netdisco-users
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> _______________________________________________
> Netdisco mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
--- Begin Message ---
Hi Nikolas,
I've been looking into this... my thought is that it's a bug in the
frond-end web interface, and the data in the database is correct. That
is: the data is being displayed incorrectly.
At the moment I can't reproduce it, though. I may follow up off-list to
get some data from your database for testing.
regards,
oliver.
On 2014-04-14 12:45, Nikolaos Milas wrote:
On 21/3/2014 2:13 μμ, Nikolaos Milas wrote:
In the meantime, I confirmed the same issue on practically all our
switches (35 Cisco switches of various types) monitored by ND2. (ND1
works fine.)
Hello,
I have upgraded to SNMP::Info 3.13 and App-Netdisco-2.026000. I can
see
a much better display of the reported devices.
Thank you for this!
I am listing below some more devices (probably special ones?) which
are
not displayed by default (same problem as before: interface Up/Up but
no
device showing up unless "Archived Data" option is checked).
When more than one ports are in the image below, the affected devices
are framed in red (as shown when the "Archived Data" option is
checked).
See:
http://iweb.noa.gr/files/nd2/nd2-4a.png
and:
http://iweb.noa.gr/files/nd2/nd2-4b.png
The latter is an HP ILO network interface.
And some more:
http://iweb.noa.gr/files/nd2/nd2-5a.png
http://iweb.noa.gr/files/nd2/nd2-5b.png
http://iweb.noa.gr/files/nd2/nd2-5c.png
http://iweb.noa.gr/files/nd2/nd2-5d.png
http://iweb.noa.gr/files/nd2/nd2-5e.png
http://iweb.noa.gr/files/nd2/nd2-5f.png
Thanks in advance.
All the best,
Nick
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
--- End Message ---
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users
