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: renamed access-point (Kristof Van Doorsselaere)
   2. Re: Constant "Error while inserting ArpCache' messages in
      syslog (Roberto Greiner)


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

Message: 1
Date: Mon, 28 Apr 2014 08:51:55 +0000
From: Kristof Van Doorsselaere <[email protected]>
Subject: Re: [Netdot-users] renamed access-point
To: Kristof Van Doorsselaere <[email protected]>,
        Netdot-users    <[email protected]>
Message-ID: <cf83e058.214f3%[email protected]>
Content-Type: text/plain; charset="iso-8859-1"

Dear Usergroup,

I noticed another issue, while updating info for our cisco WLC devicec.


DEBUG - Device::discover: Device ap-xxxxx-x does not yet exist

DEBUG - Device::assign_name: x.x.x.x does not resolve

INFO - Inserted new RR: x.x.x.x.x.hogent.be

DEBUG - ap-xxxx-x.sys.hogent.be type is: Access Point

INFO - Inserting new Device: xx-xxx-xx

DEBUG - Device::_netdot_rebless: ap-xx-xxxx.hogent.be: sysObjectID not available

DEBUG - ap-gvesa-8.sys.hogent.be: Using existing XXXXXXXX as base bridge address

DEBUG - inserting asset with asset args: serial_number: XXXXXXX , product_id: 
53 , reserved_for: , physaddr: 214551994

DEBUG - updating device with product id: 53

ERROR: Transaction aborted: Transaction aborted: Can't call method "update" on 
an undefined value at /usr/local/netdot/lib/Netdot/Model/Device.pm line 3051.


In Device.pm I added on line 3047: if ( $devtmp{snmp_target}) , which "fixed"  
this issue, not sure if it's a good fix or just a work arround, can anyone 
comment on this?


    ##############################################################

    # Things to do only when creating the device

    if ( $argv{device_is_new} ){


        $devtmp{snmp_version} = $info->{snmp_version} if exists 
$info->{snmp_version};


        if ( $asset && $asset->product_id  ){

            my $val = $self->_assign_device_monitored($asset->product_id);

            $devtmp{monitored}    = $val;

            $devtmp{snmp_polling} = $val;

            if ( $devtmp{snmp_target}) {

                $logger->debug("updating device with product id: 
%s",$asset->product_id );

                $devtmp{snmp_target}->update({monitored => $val});

            }

        }


        if ( my $g = $self->_assign_monitor_config_group($info) ){

            $devtmp{monitor_config}       = 1;

            $devtmp{monitor_config_group} = $g;

        }

    }

Kristof Van Doorsselaere
Dear Netdot Usergroup,

One of our wireless accesspoints was renamed, but for some reason this device 
was not automatically updated in netdot, is the expected behavior?

remark the accesspoint is discovered via the cisco WLC device

In the debug log I saw:


DEBUG - Device::discover: Device ap-kask-25 does not yet exist

DEBUG - Device::assign_name: A Device with IP x.x.x.x already exists: 
ap-cons-2.xxx.xx

DEBUG - ap-cons-2.hogent.be type is: Access Point

INFO - Inserting new Device: ap-kask-25

DEBUG - Device::insert: Device 20629 already exists in DB as ap-cons-2.xxx.xx

Kristof Van Doorsselaere

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

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

Message: 2
Date: Mon, 28 Apr 2014 10:17:45 -0300
From: Roberto Greiner <[email protected]>
Subject: Re: [Netdot-users] Constant "Error while inserting ArpCache'
        messages in syslog
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252

The MySQL restart did not solve the problem. I'm still getting the same
"Could not insert ArpCache" syslog messages. Does somebody know what
could be the problem?

Thanks,

Roberto

On 25/04/2014 15:15, Roberto Greiner wrote:
> No other instance was running. But running the process manually, it took
> a long time to finish (almost 2 minutes), and ended with the following
> error:
> ERROR - DBD::mysql::st execute failed: Lock wait timeout exceeded; try
> restarting transaction [for Statement "INSERT INTO ipblock
>                                        
> (address,prefix,version,status,first_seen,last_seen)
>                                         VALUES (?, ?, ?, ?, ?, ?)
>                                         ON DUPLICATE KEY UPDATE
> last_seen=VALUES(last_seen);" with ParamValues:
> 0='53174322907827205988022887441789636709', 1=128, 2=6,
> 3=IpblockStatus=HASH(0x5e280e0), 4='2014/04/25 15:06:33', 5='2014/04/25
> 15:06:33'] at /usr/share/perl5/DBIx/ContextualFetch.pm line 52.
>
> This looks like there is some deadlock in MySQL, so I forced a restart
> in MySQL, which crashed a query (where none should be running).  I ran
> the same command again, and this time it finished quickly and without
> errors. The problem seems to have been cleared. Will see for the next
> hours if new messages are generated.
>
> Thanks,
>
> Roberto
>
> On 25/04/2014 12:20, Carlos Vicente wrote:
>> Hi Roberto,
>>
>> I have never seen this one. Are you sure that there isn?t another 
>> updatedevices process running at the same time?
>>
>> cv
>>
>> On Apr 25, 2014, at 11:16 AM, Roberto Greiner <[email protected]> wrote:
>>
>>> Hi,
>>>
>>> I'm running netdot 1.0.6 (upgraded two days ago from 1.0.5RC1, my
>>> initial version). I'm getting frequent syslog messages like the
>>> following one:
>>>
>>> Apr 25 10:00:13 leonis netdot: WARN - Device 3com8.ipiranga.unesp.br:
>>> Could not insert ArpCache at 2014/04/25 10:00:03: Error while inserting
>>> ArpCache: Can't insert new ArpCache: DBD::mysql::st execute failed:
>>> Duplicate entry '7-2014-04-25 10:00:03' for key 'arpcache1' [for
>>> Statement "INSERT INTO arpcache (tstamp, device)#012VALUES (?, ?)#012"
>>> with ParamValues: 0='2014/04/25 10:00:03', 1='7'] at
>>> /usr/share/perl5/DBIx/ContextualFetch.pm line 52.#012 at
>>> /usr/local/netdot/bin/updatedevices.pl line 213#012
>>>
>>> They occur at full hours, except at midnight, midday and 5:00PM,
>>> coinciding with the following cronjob:
>>>
>>> # Retrieve forwarding tables and ARP caches
>>> 0 1-11,13-16,18-23 * * * root $PREFIX/bin/updatedevices.pl -DFA
>>>
>>> When a device, like 3Com8 in the example above, generates those messages
>>> and I disable SNMP management in Netdot, I don't get any more messages
>>> indicating errors for this device. Problem is that I have already
>>> disabled many of the devices, and new ones appeared. I started getting
>>> those errors for all my DLink switches, now I'm getting them for my 3Com
>>> switches. I couldn't find any reference in the web to this error. Could
>>> someone help me?
>>>
>>> Thanks,
>>>
>>> Roberto
>>>
>>> PS: Netdot running in a Debian 7-64bits VM, with everything, except
>>> Netdot itself, installed from the APT repositories.
>>>
>>> -- 
>>>  -----------------------------------------------------
>>>                Marcos Roberto Greiner
>>>
>>>   Os otimistas acham que estamos no melhor dos mundos
>>>    Os pessimistas tem medo de que isto seja verdade
>>>                                  James Branch Cabell
>>>  -----------------------------------------------------
>>>
>>> _______________________________________________
>>> Netdot-users mailing list
>>> [email protected]
>>> https://osl.uoregon.edu/mailman/listinfo/netdot-users
>


-- 
  -----------------------------------------------------
                Marcos Roberto Greiner

   Os otimistas acham que estamos no melhor dos mundos
    Os pessimistas tem medo de que isto seja verdade
                                  James Branch Cabell
  -----------------------------------------------------



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

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


End of Netdot-users Digest, Vol 65, Issue 13
********************************************

Reply via email to