Ok Alex, I just changed the rma.ini to the local host address and now it is listening and I am able to connect through RMA Manager. That is great.
I have a couple of questions for you though :
1. First question is in Windows, I usually install the RMA agent as a service and close the application. For UNIX, when I started I am seeing something like
[rma][11:02:36] 10.33.68.68 TCP connection accepted
[rma][11:02:36] 10.33.68.68 <-- Correct HM request received
[rma][11:02:36] 10.33.68.68 --> request processed (200)
If I close the session window, will RMA agent be stopped or will it continue listening.
1. I wanted to find disk free space for the Unix system and since there is no disk in Unix, I had read in Host Monitor website that we have to use UNC test. I did something like this - UNC test for /ora.dump/backup and selected "Alert when free space (for caller) less than 50 GB", the test gives me an alert with a reply of 11 GB. I checked the file system using df -k and it is showing me for /ora.dump/backup available space as 46327196. Please let me know what the problem is.
Thanks.
problem running RMA for Linux after configuration
That's because you have started agent in interactive mode using -i option. Start RMA without this option or use -d option = daemon mode.1. First question is in Windows, I usually install the RMA agent as a service and close the application. For UNIX, when I started I am seeing something like
[rma][11:02:36] 10.33.68.68 TCP connection accepted
[rma][11:02:36] 10.33.68.68 <-- Correct HM request received
[rma][11:02:36] 10.33.68.68 --> request processed (200)
If you want to check total free space, use "Alert when: the TOTAL free space is less than a specified value" option instead of "free space (for caller)".selected "Alert when free space (for caller) less than 50 GB", the test gives me an alert with a reply of 11 GB. I checked the file system using df -k and it is showing me for /ora.dump/backup available space as 46327196.
Regards
Alex