Monitoring, Management & Location Tracking

Unable to run Airwave Specific Commands (Alias)
Problem:

In custom AMP installation on RHEL, the AMP alias commands may or may not work. If they don't work then you could resolve the issue using the procedure in this article.

Some of the commands are below: 

root, amp_version, wd, amp_enable, amp_disable, start_amp_upgrade, etc.



Diagnostics:

If you find that all the services are up and everything works with the AMP except the Alias commands.

1. Try to source .bashrc:

# [root@localhost svn]# source /root/.bashrc
-bash: /root/.bashrc: No such file or directory

2. If you see the warning as above, check in the directory /root/ if .bashrc file is present:

# ls -la /root/

3. If the file is not present there, then you need to check the /root/amp-install.log file. 

To check that open the file using the command less:

# less amp-install.log

then search for "bash" using by typing '/' (/bash) and press Enter.

You won't find below lines in the log, they would be missing: 

/bin/cp -f lib/conf/bashrc /root/.bashrc
/bin/cp -f lib/conf/bash_logout /root/.bash_logout
/bin/cp -f lib/conf/bash_profile /root/.bash_profile
/bin/cp -f lib/conf/bash_completion_svn /etc/bash_completion_svn
 

 

 



Solution

To resolve the issue, you need to run the commands manually to copy the lib: 

cp -f /root/svn/mercury/lib/conf/bashrc /root/.bashrc
cp -f /root/svn/mercury/lib/conf/bash_logout /root/.bash_logout
cp -f /root/svn/mercury/lib/conf/bash_profile /root/.bash_profile
cp -f /root/svn/mercury/lib/conf/bash_completion_svn /root/bash_completion_svn

 

Now execute : source /root/.bashrc 

Once done, you should be able to execute the amp specific commands. 

Version History
Revision #:
2 of 2
Last update:
4 weeks ago
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.