Failure after starting bes client

Usage and Config Platform
1

[root@AP-bfiserver1 tmp]# uname -a
Linux AP-bfiserver1 3.10.0-327.10.1.el7.x86_64 #1 SMP Sat Jan 23 04:54:55 EST 2016 x86_64 x86_64 x86_64 GNU/Linux

Bes client : http://support.bigfix.com/bes/release/9.1/patch4/
[root@AP-bfiserver1 ~]# cd /tmp
[root@AP-bfiserver1 tmp]# ls
BESAgent-9.1.1134.0-rhe5.x86_64.rpm db2greg.trc.dump.15189 db2prereqcheck.24793 systemd-private-etlyth
besclient.config

[root@AP-bfiserver1 tmp]# rpm -ihv BESAgent-9.1.1134.0-rhe5.x86_64.rpm
Preparing… ################################# [100%]
Updating / installing…
1:BESAgent-9.1.1134.0-rhe5 ################################# [100%]

[root@AP-bfiserver1 tmp]# /etc/init.d/besclient start
Starting besclient (via systemctl): Job for besclient.service failed because the control process exited with error code. See “systemctl status besclient.service” and “journalctl -xe” for details.
[FAILED]

[root@AP-bfiserver1 tmp]# cd /etc/opt/BesClient/
[root@AP-bfiserver1 BesClient]# ls -la
total 72
drwxr-xr-x 2 root root 4096 Mar 4 07:22 .
drwxr-xr-x. 4 root root 4096 Mar 4 07:20 …
-rw-r–r-- 1 root root 59614 Mar 4 07:22 ActionSite.afxm

I think is something related with the OS.

Someone can help me?

Thanks!

2

Have you tried running these on the shell of your RHEL 5 server?

3

Try renaming Actionsite.afxm to actionsite.afxm.

Copy your actionsite masthead to the Linux BigFix Client computer (the masthead contains configuration, license, and security information). The action site masthead (actionsite.afxm) can be found in your BigFix Installation folders (by default they are placed under C:\BigFix Installers). If the masthead is not named “actionsite.afxm”, rename it to “actionsite.afxm” and place it on the computer at the following location: /etc/opt/BESClient/actionsite.afxm.

https://support.bigfix.com/bes/install/besclients-nonwindows.html#rhel

-jgo

1 Like
4

Oh oh…

After the rename… restart the besclient.

Let me know.
-Jgo

1 Like
5

Hi jgo
I have rename the file and still failed

[root@AP-bfiserver1 BesClient]# /etc/init.d/besclient restart
Restarting besclient (via systemctl): Job for besclient.service failed because the control process exited with error code. See “systemctl status besclient.service” and “journalctl -xe” for details.
[FAILED]
[root@AP-bfiserver1 BesClient]# ls -la
total 72
drwxr-xr-x 2 root root 4096 Mar 4 08:41 .
drwxr-xr-x. 4 root root 4096 Mar 4 07:20 …
-rw-r–r-- 1 root root 59614 Mar 4 07:22 actionsite.afxm

6

something is not right in here. something is wrong.
For immediate support, I would open a PMR asap through the IBM support process.

A few questions after you do that.
how did you get the file to the red hat box?
does it have the same size as the afxm on your server?
What is the error code when you systemctl or look through journlctl?

-Jgo

7

I ftp the file and the iem operator send me the link to download the package
The actionsite.afxm file is correct, was sent to me by the iem operator.

I do not have much experienced with systemctl this is what is showing the command about besservice

● besclient.service loaded failed failed SYSV: Starts and stops the IBM Endpoint Manager Client daemon

Thanks for your help!

8

Instructions for installing BigFix client on RedHat machine:

http://www-01.ibm.com/support/knowledgecenter/SS63NW_9.2.0/com.ibm.tivoli.tem.doc_9.2/Platform/Adm/c_red_hat_installation_instructi.html

Copy your actionsite masthead to the client computer (the masthead contains configuration, license, and security information). The action site masthead (actionsite.afxm) can be found in your BES Installation folders (by default they are placed under C:\Program Files (x86)\BigFix Enterprise\BES Installers\Client on Windows and /var/opt/BESInstallers/Client/ on Linux). If the masthead is not named actionsite.afxm, rename it to actionsite.afxm and place it on the computer at the following location: /etc/opt/BESClient/actionsite.afxm.

Note: The directory /etc/opt/BESClient/ is not automatically created by the installer. If it does not exist, create it manually.

I noticed in your post:

[root@AP-bfiserver1 tmp]# cd /etc/opt/BesClient/
[root@AP-bfiserver1 BesClient]# ls -la
total 72
drwxr-xr-x 2 root root 4096 Mar 4 07:22 .
drwxr-xr-x. 4 root root 4096 Mar 4 07:20 ..
-rw-r--r-- 1 root root 59614 Mar 4 07:22 ActionSite.afxm

It appears the /etc/opt/BESClient/ directory is spelled /etc/opt/BesClient/ (the e and the s in BesClient are not capitalized. Could this be the problem?)

Try recreating/renaming the directory to be /etc/opt/BESClient/

and the masthead to actionsite.afxm instead of ActionSite.afxm

2 Likes
9

Good Eye! @BigFixNinja

1 Like