Type Public
Category Configuration
Subject iAgent will not show up in iManager after install in CentOS
Rating 0% rating out of 0 vote(s).
Navigation Previous - Next - iTivity Remote Support Software - DoubleVision TTY Terminal Remote Control

iAgent will not show up in iManager after install in CentOS

This is a quick troubleshooting guide to help those who have problems with the iAgent NOT
showing up on the iManager list. This guide assumes the iAgent was installed on a Unix/Linux
system. For Windows the troubleshooting principles are the same.

1- Review that you entered the correct DNS name for your iServer in the
iAgent configuration file.

- Look at the file : /etc/iTivity/iAgent.conf
- in this file look for the entry that looks as follows :


2- Make sure that is spelled correctly.
If not correct it, save the file. and stop and restart the iAgent by
issuing the commands:

cd /usr/lib/iTivity/iAgent

2- Now if the DNS entry IS CORRECT, then it could be that the host computer
where the iAgent is installed is NOT configured correctly for DNS, or has
NO DNS, or there is some issue with DNS.

To check for this, from the command line enter the command :


you should get an output similar to the one below, and in this case
it was able to resolve my iServer's DNS name to the correct IP address.

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> iserver.us.tridia.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44614
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;iserver.us.tridia.com. IN A

iserver.us.tridia.com. 3600 IN A

;; Query time: 86 msec
;; WHEN: Wed Aug 30 09:45:53 2017
;; MSG SIZE rcvd: 55

- if the DNS is NOT working, you can always ENTER the IP address of your iServer
and by-pass repairing your customers DNS issues. Just edit the file iAgent.conf
( see above ) and instead of the DNS name use the IP address of your iserver.
This would be a temporary solution unless you have a static IP for you iserver
in which case you probably don't have to worry out this.

3- IF the problem is NOT either of the ABOVE, then it could be that the iAgent
is being blocked by the FIREWALL at the host computer
OR AT THE COMPANY's firewall.

To test to see if you are able to 'get out' run the following command :

traceroute -p 23800

4- Lastly if all else is working make sure you don't have 2 copies of the iAgent running.
To be sure, stop and then restart the iAgent as follows :

cd /usr/lib/iTivity/iAgent; ./stop_iagent; ./start_iagent

This is a general troubleshooting guide taken from a real tech support case.
Did this answer your question? Be heard!
5 4 3 2 1   
Yes! Getting warm Keep looking Not Really No!