Linux Agent

Agents not showing in Dashboard/Connection errors in logs:

  1. Confirm you are starting the agent with root or sudo
  2. Confirm you have downloaded the correct agent for your OS Architecture 32 or 64 bit. Use the “uname -mrsn” command to get detailed Platform/OS information.
  3. Our agents only support Glib 2.5 and above.
  4. What are the permissions on the smagent Folder.

Use the “smagent # ls -lR” command to verify:

drwxr-xr-x 2 user user 4096 Dec 19 2012 bin
drwxr-xr-x 2 user user 4096 Feb 5 2010 doc
drwxr-xr-x 2 user user 4096 Sep 26 07:27 etc
drwxr-xr-x 2 root root 4096 Aug 28 00:00 logs
-rwxr-xr-x 1 root root 9574 Jun 14 2013 smagent.sh
drwxr-x— 4 root root 4096 Aug 20 12:06 plugins

./bin:

total 820

-rwxrwxrwx 1 user user 735470 Jun 27 2013 smagent
-rwxr-xr-x 1 user user 90691 Feb 14 2013 updater

./doc:

total 8

-rw-r–r– 1 user user 2049 Oct 27 2009 LICENSE
-rw-r–r– 1 user user 3131 Jun 24 2013 README

./etc:

total 4

-rw-r–r– 1 root root 289 Aug 20 10:50 smagent.conf

./logs:

total 28600

-rw-r–r– 1 root root 2395028 Aug 28 15:28 smagent.log
-rw-r–r– 1 root root 5 Aug 20 11:39 smagent.pid

 

Enable Linux Agent detailed logging

  1. Locate this file in the smagent folder …/etc/smagent.conf
  2. Add LOGLEVEL 10 on a new line then save
  3. Restart the agent
  4. Wait for 10 min…
  5. Go to …/smagent/logs

 

SSL connection initialization failed

Problem is that our agent is expecting the shared SSL library name as “libssl.so”.

So, in this case it would be sufficient to create a symbolic link for the original shared SSL library to point it to libssl.so.

That should be enough.

Please try this:

1.) Locate your shared SSL library (locate libssl.so)

2.) Change the directory to that folder where your libssl.so is located at

3.) Create symbolic link for the shared SSL library like: ln -s libssl.so.1.0.1e libssl.so (ln -s <ORIGINAL FILE> <NEW NAME>)

4.) Restart the agent