I have read thru many topics here and I have followed the instructions on installing on the client on Ubuntu but I am stumped. I’m a very noob to Linux as I’ve been using windows for half a century and being forced to lean Linux cause windows is getting expensive license wise.
I am installing on Linux Ubuntu 20.04 (5.8.0-55-generic) and using ver 9.5. I know it is not supported on this but I have gotten it to work, I will explain in a bit.
I have a test box set up with Ubuntu 20.04 and have followed the steps in the document https://support.bigfix.com/bes/install/besclients-nonwindows.html#ubuntu and have successfully set up BigFix on this device and it is reporting to the server.
I am attempting to set this up in a corporate UAT environment and I follow the same steps as on my test box and it does not install the client properly.
On my test box I go to /var/opt/BESClient and I see the __BESData folder etc… so I can go into the logs and see that it is running. I open System Monitor and select all processes and I see BESClient there.
In the UAT environment I see none of this.
I have turned on and off the firewall, added the server address to the hosts file etc…but as I said i do not even see the process working on the UAT environment.
Any help or push in any direction would be great.
Ubuntu 20.04 endpoint in UAT environment with BigFix v9.5 agent installed.
Do the BigFix client logs on the endpoint show any successful network communications with your BigFix UAT server (as appears in your masthead file?)
Reading your post a second time, can you confirm that the __BESData folder exists on your UAT endpoint?
How about the package itself, does dpkg show it as installed?
dpkg-query -l
Nope. It’s like the deamon is not even starting/running. It shows:
$ sudo /etc/init.d/besclient start
Starting besclient (via systemctl): besclient.service.
The __BESData folder should be under the /var/opt/BESClient folder I believe, but it is not present, the whole folder is empty.
The only thing the query shows is besagent, same as my test box.
Please validate:
ls /etc/opt/BESClient/
Should show actionsite.afxm
ls /var/opt/BESClient
Should show some files and the __BESData folder
dpkg-query -l|grep besagent
Should show an installed package
top
Should show BESClient somewhere in the list.
You can also check for today’s client log with a sudo (since the __Data folder is permissioned against your access)
sudo tail -f /var/opt/BESClient/__BESData/__Global/Logs/20210630.log
4 Likes
OkAy so I forgot that Linux was a case sensitive OS…
In /ect/opt/BESClient I had ActionSite.amfx…so renamed it to actionsite and it is working now!
@brolly33 Thanks for the tips they will come in useful in the future to look for things running.
Also for any noob I found this useful: (not sure how I came upon it but…)
systemctl status besclient.service
I was seeing this:
besclient.service - LSB: Starts BigFix Agent
Loaded: loaded (/etc/init.d/besclient; generated)
Drop-In: /usr/lib/systemd/system/besclient.service.d
└─restart.conf
Active: inactive (dead) since Wed 2021-06-30 11:24:44 CDT; 1h 34min ago
Docs: man:systemd-sysv-generator(8)
Process: 384903 ExecStart=/etc/init.d/besclient start (code=exited, status=0/SUCCESS)
Process: 384911 ExecStop=/etc/init.d/besclient stop (code=exited, status=0/SUCCESS)
Jun 30 11:24:44 TMDEV04 systemd[1]: Starting LSB: Starts BigFix Agent…
Jun 30 11:24:44 TMDEV04 besclient[384910]: /etc/init.d/besclient: line 57: failure: command not found
Jun 30 11:24:44 TMDEV04 systemd[1]: besclient.service: Succeeded.
Jun 30 11:24:44 TMDEV04 systemd[1]: Started LSB: Starts BigFix Agent.
So seeing the 3rd to last line I see there is a failure, I opened besclient in a text editor and saw it was looking for actionsite.afmx, then remember Linux being case sensitive and there you go.
2 Likes
