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: Duplicate asset error message (Jos? A. Dom?nguez)


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

Message: 1
Date: Wed, 30 Jan 2013 13:40:39 -0800
From: "Jos? A. Dom?nguez"       <[email protected]>
Subject: Re: [Netdot-users] Duplicate asset error message
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"

On 1/30/13 11:13 AM, Schroeder, AJ (GE Healthcare, consultant) wrote:
> 
> ERROR- Error while updating Asset: Can't update 662: DBD::mysql::st execute
> failed: Duplicate entry '12971' for key 2 [for Statement "UPDATE asset
> SET    physaddr = ? WHERE  id=? " with ParamValues: 0='12971', 1='662'] at
> /usr/lib/perl5/site_perl/5.8.8/DBIx/ContextualFetch.pm line 52.  at
> /usr/local/netdot/bin/updatedevices.pl line 201 
> 

Hi AJ, yeah, we have run into similar issues. It looks like you have two
devices/assets that have the same key information. Do you know what that
particular assets are? You should be able to direct sql query for some of
the details. You can attempt to run updatedevices.pl with debugging turned
on (-d) and that should point you in the right direction. Basically you
have a new device that seems to want to use the same asset information as
an existing device. You can also attempt some direct sql queries on the
asset and device tables for the referenced ids.

In the end you want to determine which two devices are colliding and see
whether it is an issue with the way that netdot is handling the assets or a
misconfiguration on the devices or lingering old data in netdot.

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/20130130/e7adf16b/attachment-0001.bin
 

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

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


End of Netdot-users Digest, Vol 50, Issue 10
********************************************

Reply via email to