APs config status is stuck in Verifying (nextval max exceeded)

By Shyam_Moolayilkalarikkal posted Jun 27, 2014 08:00 PM

  

Issue: APs config status is stuck in Verifying (nextval max exceeded)

 

I have a large number of APs that have a configuration status of "Verifying" and they have been stuck that way for a long time. In the config_verifier log (/var/log/config_verifier) I'm seeing errors that look something like this...

Fri Jul 17 04:04:13 2009: try failed! ERROR: nextval: reached maximum value of sequence "device_config_id_seq" (2147483647): insert
into device_config (ap_id, name, value, timestamp) values (?, ?, ?, null)

(see below for more detail)

What's going on?

The counter used by AMP for device configuration audits has been exceeded. You can check the value with this command:

# dbc 'select * from device_config_id_seq'

You can reset the counter by running the following commands:

# disable_amp
# dbc 'delete from device_config;'
# dbc 'alter SEQUENCE device_config_id_seq RESTART 1;'
# enable_amp

Wait for a moment then check the AMP web GUI. As AMP begins to audit the devices their configuration status will change from Verifying to one of the other states.


-----------------------------------------------------------------------
More detailed error message from config_verifier log:

Fri Jul 17 04:04:13 2009: try failed! ERROR: nextval: reached maximum value of sequence "device_config_id_seq" (2147483647): insert
into device_config (ap_id, name, value, timestamp) values (?, ?, ?, null) (1004 bsnAPIfSniffChannel.2 0) at /usr/local/airwave/lib/
perl/Mercury/DB/Q.pm line 191
Mercury::DB::Q::execute('Mercury::DB::Q', 'insert into device_config (ap_id, name, value, timestamp) val...', 1004, 'bsnAPIf
SniffChannel.2', 0) called at /usr/local/airwave/lib/perl/Mercury/DeviceConfig.pm line 64
Mercury::DeviceConfig::insert('Mercury::DeviceConfig', 1004, 'bsnAPIfSniffChannel.2', 0) called at /usr/local/airwave/lib/pe
rl/Mercury/DeviceConfig.pm line 52

0 comments
3 views