Send Netdot-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-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 Netdot-users digest..."
Today's Topics:
1. Re: Error updating device. (Jos? A. Dom?nguez)
2. Re: Error updating device. (Carlos Vicente)
3. Re: Error updating device. (Begley, John)
----------------------------------------------------------------------
Message: 1
Date: Mon, 18 Mar 2013 15:03:36 -0700
From: "Jos? A. Dom?nguez" <[email protected]>
Subject: Re: [Netdot-users] Error updating device.
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
On 3/15/13 10:56 AM, Begley, John wrote:
> A Cisco 7606 showed up as SNMP down, but I knew was available. I flipped
> the snmp-down flag, and updated. Got past the first page where owner/etc.
> is assigned, and then I get this. Tried it on another 7606 running the
> same code and got the same response.
>
>
>
> Where would I start looking to correct this?
>
John, what version of netdot are you running? It looks to me like an issue
with an IP address that is being used on your 7606. If I had to guess,
there might be some sort of inconsistency.
For more details I would suggest that you do an updatedevices.pl -d for the
specific device that you are trying to discover.
Jos?.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
Url :
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20130318/a1c03dd6/attachment-0001.bin
------------------------------
Message: 2
Date: Tue, 19 Mar 2013 11:42:54 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] Error updating device.
To: "Begley, John" <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
John,
In mysql, list your netdot tables and see if you have any rotated ARP or
FWT tables in there. You can identify them because they have a timestamp
at the end of their name (e.g. arpcacheentry_NNN) where NNN is a unix
epoch integer.
If you do, I would try dropping them to see if that fixes your problem.
cv
On 3/15/13 1:56 PM, Begley, John wrote:
>
> A Cisco 7606 showed up as SNMP down, but I knew was available. I
> flipped the snmp-down flag, and updated. Got past the first page
> where owner/etc. is assigned, and then I get this. Tried it on
> another 7606 running the same code and got the same response.
>
>
>
> Where would I start looking to correct this?
>
>
>
> JB
>
> *updatedevice.html* produced the following error:
>
>
>
> Transaction aborted: Error while updating Ipblock: Can't update
> 6195829: DBD::mysql::st execute failed: Cannot add or update a child
> row: a foreign key constraint fails (`netdot`.`ipblock`, CONSTRAINT
> `fk_status_2` FOREIGN KEY (`status`) REFERENCES `ipblockstatus`
> (`id`)) [for Statement "UPDATE ipblock
>
> SET status = ?
>
> WHERE id=?
>
> " with ParamValues: 0='Static', 1='6195829'] at
> /usr/share/perl5/DBIx/ContextualFetch.pm line 52, line 5763.
>
>
>
> Stack:
>
> [/usr/share/perl5/DBIx/ContextualFetch.pm:52]
>
> [/usr/share/perl5/DBIx/ContextualFetch.pm:32]
>
> [/usr/share/perl5/Class/DBI.pm:781]
>
> [/usr/local/netdot/lib/Netdot/Model.pm:837]
>
> [/usr/local/netdot/lib/Netdot/Model/Ipblock.pm:2835]
>
> [/usr/local/netdot/lib/Netdot/Model/Ipblock.pm:2808]
>
> [/usr/local/netdot/lib/Netdot/Model/Ipblock.pm:766]
>
> [/usr/local/netdot/lib/Netdot/Model/Ipblock.pm:1694]
>
> [/usr/local/netdot/lib/Netdot/Model/Interface.pm:686]
>
> [/usr/local/netdot/lib/Netdot/Model/Interface.pm:604]
>
> [/usr/local/netdot/lib/Netdot/Model/Device.pm:5893]
>
> [/usr/local/netdot/lib/Netdot/Model/Device.pm:2968]
>
> [/usr/local/netdot/lib/Netdot/Model/Device.pm:2747]
>
> [/usr/local/netdot/lib/Netdot/Model.pm:746]
>
> [/usr/local/netdot/lib/Netdot/Model/Device.pm:2745]
>
> [/usr/local/netdot/lib/Netdot/Model/Device.pm:1559]
>
> [/usr/local/netdot/htdocs/management/updatedevice.html:248]
>
> [/usr/local/netdot/htdocs/management/autohandler:81]
>
> [/usr/share/perl5/HTML/Mason/Request.pm:936]
>
>
> [/usr/local/netdot/htdocs/masondata/obj/991023240/management/autohandler.obj:21]
>
> [/usr/local/netdot/htdocs/autohandler:76]
>
> at /usr/local/netdot/lib/Netdot/Model/Interface.pm line 686
>
>
>
> Stack:
>
> [/usr/share/perl5/Carp.pm:44]
>
> [/usr/share/perl5/Class/DBI.pm:169]
>
> [/usr/share/perl5/Class/DBI.pm:175]
>
> [/usr/share/perl5/Class/DBI.pm:783]
>
> [/usr/local/netdot/lib/Netdot/Model.pm:837]
>
> [/usr/local/netdot/lib/Netdot/Model/Ipblock.pm:2835]
>
> [/usr/local/netdot/lib/Netdot/Model/Ipblock.pm:2808]
>
> [/usr/local/netdot/lib/Netdot/Model/Ipblock.pm:766]
>
> [/usr/local/netdot/lib/Netdot/Model/Ipblock.pm:1694]
>
> [/usr/local/netdot/lib/Netdot/Model/Interface.pm:686]
>
> [/usr/local/netdot/lib/Netdot/Model/Interface.pm:604]
>
> [/usr/local/netdot/lib/Netdot/Model/Device.pm:5893]
>
> [/usr/local/netdot/lib/Netdot/Model/Device.pm:2968]
>
> [/usr/local/netdot/lib/Netdot/Model/Device.pm:2747]
>
> [/usr/local/netdot/lib/Netdot/Model.pm:746]
>
> [/usr/local/netdot/lib/Netdot/Model/Device.pm:2745]
>
> [/usr/local/netdot/lib/Netdot/Model/Device.pm:1559]
>
> [/usr/local/netdot/htdocs/management/updatedevice.html:248]
>
> [/usr/local/netdot/htdocs/management/autohandler:81]
>
> [/usr/share/perl5/HTML/Mason/Request.pm:936]
>
>
> [/usr/local/netdot/htdocs/masondata/obj/991023240/management/autohandler.obj:21]
>
> [/usr/local/netdot/htdocs/autohandler:76]
>
>
>
>
> ------------------------------------------------------------------------
> This E-mail and any of its attachments may contain Time Warner Cable
> proprietary information, which is privileged, confidential, or subject
> to copyright belonging to Time Warner Cable. This E-mail is intended
> solely for the use of the individual or entity to which it is
> addressed. If you are not the intended recipient of this E-mail, you
> are hereby notified that any dissemination, distribution, copying, or
> action taken in relation to the contents of and attachments to this
> E-mail is strictly prohibited and may be unlawful. If you have
> received this E-mail in error, please notify the sender immediately
> and permanently delete the original and any copy of this E-mail and
> any printout.
>
>
> _______________________________________________
> Netdot-users mailing list
> [email protected]
> https://osl.uoregon.edu/mailman/listinfo/netdot-users
------------------------------
Message: 3
Date: Tue, 19 Mar 2013 12:37:53 -0400
From: "Begley, John" <[email protected]>
Subject: Re: [Netdot-users] Error updating device.
To: "Jos? A. Dom?nguez" <[email protected]>,
"[email protected]" <[email protected]>
Message-ID:
<767a949080bda948bd6da9c5e2918748097cd03...@prvpexvs10.corp.twcable.com>
Content-Type: text/plain; charset="iso-8859-1"
Thanks guys. Definitely some addressing rules broken there which, when
removed, corrected the issue. All parties involved have been heavily flogged.
JB
> -----Original Message-----
> From: [email protected] [mailto:netdot-users-
> [email protected]] On Behalf Of "Jos? A. Dom?nguez"
> Sent: Monday, March 18, 2013 6:04 PM
> To: [email protected]
> Subject: Re: [Netdot-users] Error updating device.
>
> On 3/15/13 10:56 AM, Begley, John wrote:
> > A Cisco 7606 showed up as SNMP down, but I knew was available. I
> > flipped the snmp-down flag, and updated. Got past the first page where
> owner/etc.
> > is assigned, and then I get this. Tried it on another 7606 running
> > the same code and got the same response.
> >
> >
> >
> > Where would I start looking to correct this?
> >
>
> John, what version of netdot are you running? It looks to me like an issue
> with an IP address that is being used on your 7606. If I had to guess, there
> might be some sort of inconsistency.
>
> For more details I would suggest that you do an updatedevices.pl -d for the
> specific device that you are trying to discover.
>
> Jos?.
>
This E-mail and any of its attachments may contain Time Warner Cable
proprietary information, which is privileged, confidential, or subject to
copyright belonging to Time Warner Cable. This E-mail is intended solely for
the use of the individual or entity to which it is addressed. If you are not
the intended recipient of this E-mail, you are hereby notified that any
dissemination, distribution, copying, or action taken in relation to the
contents of and attachments to this E-mail is strictly prohibited and may be
unlawful. If you have received this E-mail in error, please notify the sender
immediately and permanently delete the original and any copy of this E-mail and
any printout.
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 52, Issue 8
*******************************************
