Not able to login to Airwave GUI

Aruba Employee
Problem:

Not able to login to the Airwave web interface. User/password not accepted



Diagnostics:

 

We would be seeing the below error message in the httpd error log, when we try to login to the server.

DBD::Pg::st execute failed: ERROR:  database is not accepting commands to avoid wraparound data loss in database "airwave"
HINT:  Stop the postmaster and use a standalone backend to vacuum that database.
You might also need to commit or roll back old prepared transactions. at /usr/local/airwave/lib/perl/Mercury/DB/Q/st.pm line 20.
[Fri May 06 15:00:03 2016] [error] [client 127.0.0.1] DBD::Pg::st execute failed: ERROR:  database is not accepting commands to avoid wraparound data loss in database "airwave"\nHINT:  Stop the postmaster and use a standalone backend to vacuum that database.\nYou might also need to commit or roll back old prepared transactions. at /usr/local/airwave/lib/perl/Mercury/DB/Q/st.pm line 20.\n\t(in cleanup) DBD::Pg::st execute failed: ERROR:  database is not accepting commands to avoid wraparound data loss in database "airwave"\nHINT:  Stop the postmaster and use a standalone backend to vacuum that database.\nYou might also need to commit or roll back old prepared transactions. at /usr/local/airwave/lib/perl/Mercury/DB/Q/st.pm line 20.\n, referer: https://airwave.ca.com/site_list

If for some reason autovacuum fails to clear old XIDs from a table, the system will begin to emit warning messages like this when the database's oldest XIDs reach ten million transactions from the wraparound point

 

WARNING:  database "airwave" must be vacuumed within 177009986 transactions
HINT:  To avoid a database shutdown, execute a database-wide VACUUM in "airwave".

 

A manual VACUUM should fix the problem, as suggested by the hint; but note that the VACUUM must be performed by a superuser, else it will fail to process system catalogs and thus not be able to advance the database's datfrozenxid.) If these warnings are ignored, the system will shut down and refuse to start any new transactions once there are fewer than 1 million transactions left until wraparound:

ERROR:  database is not accepting commands to avoid wraparound data loss in database "airwave"
HINT:  Stop the postmaster and use a standalone backend to VACUUM in "airwave".


Solution

 

When we fall to this scenario, we have to enter the single-user backend for airwave. Below are the steps we need to follow to fix this issue,

# amp_disable

# service postgresql stop

Now enter the single-user backend for "airwave"

# su postgres -c "postgres --single -D /var/lib/pgsql/9.2/data airwave"

PostgreSQL stand-alone backend 9.2.4

Do a full vacuum analyze

backend> vacuum Full analyze;

Do ctl+D to exit the backend shell

#service postgresql start

# amp_enable -now

 

Once analyze is done it will come back
 

Version history
Revision #:
2 of 2
Last update:
‎05-07-2016 03:05 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
cancel
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.