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. Error When deleting a host (Michael T. Voity)
   2. REST interface stripping special characters (Patrick Landry)
   3. High CPU on Brocade Ethernet router when polled (Newton, Terry M)


----------------------------------------------------------------------

Message: 1
Date: Tue, 01 Oct 2013 15:55:40 -0400
From: "Michael T. Voity" <[email protected]>
Subject: [Netdot-users] Error When deleting a host
To: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"

Hello,

I am trying to delete a device that has been off my network for quite a 
while.   I get this error message when i go to manually delete it:

Ideas?


Transaction aborted: Can't delete 296: DBD::mysql::st execute failed: Cannot 
delete or update a parent row: a foreign key constraint fails 
(`netdot`.`fwtable_1353833103`, CONSTRAINT `fk_device_5` FOREIGN KEY (`device`) 
REFERENCES `device` (`id`)) [for Statement "DELETE
FROM   device
WHERE  id=?
" with ParamValues: 0='296'] at /usr/local/share/perl5/DBIx/ContextualFetch.pm 
line 52,  line 4.

Stack:
   [/usr/local/share/perl5/DBIx/ContextualFetch.pm:52]
   [/usr/local/share/perl5/DBIx/ContextualFetch.pm:32]
   [/usr/local/share/perl5/Class/DBI.pm:737]
   [/usr/local/netdot/lib/Netdot/Model.pm:876]
   [/usr/local/netdot/lib/Netdot/Model/Device.pm:2377]
   [/usr/local/netdot/htdocs/generic/delete.html:161]
   [/usr/local/netdot/htdocs/generic/delete.html:163]
   [/usr/local/netdot/htdocs/autohandler:110]
   [/usr/local/netdot/htdocs/management/dhandler:1]
   [/usr/local/netdot/htdocs/management/autohandler:83]
   [/usr/local/share/perl5/HTML/Mason/Request.pm:951]
   
[/usr/local/netdot/htdocs/masondata/obj/1292882063/management/autohandler.obj:21]
   [/usr/local/netdot/htdocs/autohandler:76]
  at /usr/local/netdot/htdocs/generic/delete.html line 161.

Stack:
   [/usr/local/share/perl5/Carp.pm:100]
   [/usr/local/share/perl5/Class/DBI.pm:169]
   [/usr/local/share/perl5/Class/DBI.pm:175]
   [/usr/local/share/perl5/Class/DBI.pm:739]
   [/usr/local/netdot/lib/Netdot/Model.pm:876]
   [/usr/local/netdot/lib/Netdot/Model/Device.pm:2377]
   [/usr/local/netdot/htdocs/generic/delete.html:161]
   [/usr/local/netdot/htdocs/generic/delete.html:163]
   [/usr/local/netdot/htdocs/autohandler:110]
   [/usr/local/netdot/htdocs/management/dhandler:1]
   [/usr/local/netdot/htdocs/management/autohandler:83]
   [/usr/local/share/perl5/HTML/Mason/Request.pm:951]
   
[/usr/local/netdot/htdocs/masondata/obj/1292882063/management/autohandler.obj:21]
   [/usr/local/netdot/htdocs/autohandler:76]





-- 
Michael T. Voity
Network Engineer
University of Vermont

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20131001/ac1f391e/attachment-0001.html
 

------------------------------

Message: 2
Date: Tue, 1 Oct 2013 16:43:44 -0500 (CDT)
From: Patrick Landry <[email protected]>
Subject: [Netdot-users] REST interface stripping special characters
To: "netdot-users " <[email protected]>
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="utf-8"

I am using the REST interface to manipulate DNS RR records. When I retrieve a 
record which has a multiline comment field (there are newlines in the field) 
the newline characters are being stripped from the string I get from the REST 
interface. Is there any way to get the actual data including the special 
(newline) characters using the REST interface? 

-- 

patrick 

Patrick Landry 
University of Louisiana at Lafayette 
Director, University Computer Support Services 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20131001/2cb0770d/attachment-0001.html
 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Landry, Patrick.vcf
Type: text/directory
Size: 11870 bytes
Desc: not available
Url : 
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20131001/2cb0770d/attachment-0001.bin
 

------------------------------

Message: 3
Date: Wed, 2 Oct 2013 17:41:51 +0000
From: "Newton, Terry M" <[email protected]>
Subject: [Netdot-users] High CPU on Brocade Ethernet router when
        polled
To: "[email protected]" <[email protected]>
Message-ID:
        <[email protected]>
Content-Type: text/plain; charset="us-ascii"

I am using Brocade Ethernet routers and whenever netdot polls the device, it 
runs up the cpu and causes adverse effects.  I have turned off the bulk snmp, 
but that did not make a differenct.  Any suggestions?  I really would like to 
use netdot to poll and collect information from these devices so any 
suggestions are appreciated.  Thanks.

----------------------------------------------------------------------
Confidentiality Notice: This e-mail message, including any attachments, is for 
the sole use of the intended recipient(s) and may contain confidential and 
privileged information. Any unauthorized review, use, disclosure or 
distribution is prohibited. If you are not the intended recipient, please 
contact the sender by reply e-mail and destroy all copies of the original 
message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20131002/e6f98912/attachment.html
 

------------------------------

_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users


End of Netdot-users Digest, Vol 59, Issue 1
*******************************************

Reply via email to