Monitoring, Management & Location Tracking

URL: /nf/scheduling error - remove scheduled rogue scans from the database

In AMP 4.0, AMP stopped supporting rogue scans on old Symbol APs. Because of this change, customers who have scheduled rogue scans get errors when they go to the scheduling page. This document describes how to access the AMP database to delete the scheduled scans.

1. SSH to the AMP or access the AMP terminal directly.
2. Type 'db' to access the database.

3. Issue the following command at the prompt to see the scheduled events:

airwave=> select * from schedule;

id | window_id | type | target_id | recurrent | username 
-----+-----------+------+-----------+-----------+----------
284 | 134 | 4 | 5464 | 1 | root
281 | 134 | 2 | 5464 | 1 | root
282 | 134 | 2 | 5464 | 1 | root
283 | 134 | 2 | 5464 | 1 | root
(4 rows)


Any entries of type 4 need to be deleted (I added the bad entry to our database for demonstration purposes; visiting the System -> Scheduling page on our AMP produces the same error you were seeing).

4. Delete the offending records:

airwave=> delete from schedule where type=4;

DELETE 1

5. Confirm the delete with the previous command:

airwave=> select * from schedule;

id | window_id | type | target_id | recurrent | username 
-----+-----------+------+-----------+-----------+----------
281 | 134 | 2 | 5464 | 1 | root
282 | 134 | 2 | 5464 | 1 | root
283 | 134 | 2 | 5464 | 1 | root
(3 rows)

6. Quit the database

airwave=> \q
In AMP 4.0, AMP stopped supporting rogue scans on old Symbol APs. Because of this change, customers who have scheduled rogue scans get errors when they go to the scheduling page. This document describes how to access the AMP database to delete the scheduled scans.

1. SSH to the AMP or access the AMP terminal directly.
2. Type 'db' to access the database.

3. Issue the following command at the prompt to see the scheduled events:

airwave=> select * from schedule;

id | window_id | type | target_id | recurrent | username 
-----+-----------+------+-----------+-----------+----------
284 | 134 | 4 | 5464 | 1 | root
281 | 134 | 2 | 5464 | 1 | root
282 | 134 | 2 | 5464 | 1 | root
283 | 134 | 2 | 5464 | 1 | root
(4 rows)


Any entries of type 4 need to be deleted (I added the bad entry to our database for demonstration purposes; visiting the System -> Scheduling page on our AMP produces the same error you were seeing).

4. Delete the offending records:

airwave=> delete from schedule where type=4;

DELETE 1

5. Confirm the delete with the previous command:

airwave=> select * from schedule;

id | window_id | type | target_id | recurrent | username 
-----+-----------+------+-----------+-----------+----------
281 | 134 | 2 | 5464 | 1 | root
282 | 134 | 2 | 5464 | 1 | root
283 | 134 | 2 | 5464 | 1 | root
(3 rows)

6. Quit the database

airwave=> \q

Version history
Revision #:
1 of 1
Last update:
‎06-09-2014 09:12 AM
Updated by:
 
Labels (2)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.