Monitoring, Management & Location Tracking

PAPI process in Airwave continuously bootstraps
Problem:

In the recent Airwave upgrades we are randomly noticing that the PAPI process never be stable and bootstraps PAPI process continuously.

 

This behavior impacts the following feature:

> Clients count and usage graph doesn't update.

> App RF data will not get updated.



Diagnostics:

The PAPI process starts to fail when Airwave couldn't resolve the server's hostname hence it log the following error message in service watcher log and tries to bootstrap the papi process.

 



Solution

We can resolve this issue by adding a manual entry in /etc/hosts file as shown below.

Syntax to add DNS entry into Airwave:

echo -e "amp eth0 IP"'\t'"FQDN"'\t'"hostname" >> /etc/hosts

Current /etc/hosts:

[root@current_amp mercury]# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

Hostname/FQDN of Airwave:

[root@current_amp mercury]# hostname
current_amp.nslab.com

 

Adding host entry into /etc/hosts:
[root@current_amp mercury]# echo -e "10.29.161.57"'\t'"current_amp.nslab.com"'\t'"current_amp" >> /etc/hosts

 

Updated entry:
[root@current_amp mercury]# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
10.29.161.57    current_amp.nslab.com   current_amp
[root@current_amp mercury]#
 

Restart the services:

[root@current_amp mercury]# rd

Once the service is restarted the PAPI service will be stable and graphs will be updated.

Version history
Revision #:
2 of 2
Last update:
‎12-28-2016 06:53 AM
Updated by:
 
Labels (1)
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.