Thanks a lot, Oktawian, for you reply and advice. Instructions very useful to know.
Yes, client registered ok.
Stop/start did not help, stop/delete folder/start did resync, but the "Update BESClient" fixlet still got "not reported".
I then installed another SLES15 with the BESclient, this time another version.
While the first BESClient install was BESAgent-11.0.0.175-sle12.x86_64.rpm , this time I used BESAgent-11.0.1.104-sle12.x86_64.rpm. With this version, everything went smoothly. I then went on the first machine and updated rpm -Fvh with the higher version ... then BESAgent got updated from BigFix immediately and also the ILMT Client Scanner install went through quickly and successfully.
Maybe the 11.0.0.175 has a flaw. I wanted to use a lower version intentionally to check correct BigFix action. With 11.0.1.104 all went well and got updated to 11.0.2.125
Thanks again for your help.
Kind regards, Igor
------------------------------
Igor P. Merkù
------------------------------
Original Message:
Sent: Mon July 15, 2024 06:34 AM
From: Oktawian Powązka
Subject: BESClient : after install start ok, but systemctl enable fails
Hello,
If BESClient is registered (visible on BES Console) it definitely means that the service is working (guess that this 'malformated ...' stuff can be treated as warnings).
Pls. look into the following to confirm how the BESClient is processing :
/var/opt/BESClient/__BESData/__Global/Logs/20240715.log
(Considering that all registration steps been conducted today)
Pay close attention to following line:
RegisterOnce: Attempting secure registered....
If BESClient succeeded with registration a following log line should show up :
Registered with url 'https://<besserver>:52311/...
In the BES Console, right-click on that agent and pick up 'Send Refresh' from a pop-up menu.
Bigfix agent log file should reply with a following entry:
ForceRefresh command received.
That will allow to confirm Bigfix Server<->Bigfix agent connection flow.
at last, there is a useful trick to force the full BigFix Agent<->BigFix Server synchronization :
stop the BigFix Agent,
Delete the '../__BESData' folder,
start the BigFix Agent,
That way BigFix Agent should receive all due actions...
------------------------------
Thank you,
Oktawian
Oktawian Powązka, L3 Support
IBM License Metric Tool
Original Message:
Sent: Mon July 15, 2024 04:08 AM
From: Igor P. Merkù
Subject: BESClient : after install start ok, but systemctl enable fails
Hi,
is this the correct place to ask or should I open a support ticket with HCL?
Just installed the BESClient on SuSE 15 SP4 (first time on SLES15, other SLES12 or Ubuntu are ok).
When trying to enable the automatic start of BESClient at system boot I get an error:
root# systemctl enable besclient.serviceSynchronizing state of besclient.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.Executing: /usr/lib/systemd/systemd-sysv-install enable besclienterror: malformated LSB header in besclient: missing LSB end marker, aborting.
BESClient is running, though:
● besclient.service - BESClient daemon Loaded: loaded (/usr/lib/systemd/system/besclient.service; enabled; vendor preset: disabled) Active: active (running) since Mon 2024-07-15 09:22:06 CEST; 5s ago Process: 25824 ExecStart=/usr/local/bin/besclient start (code=exited, status=0/SUCCESS) Tasks: 7 CGroup: /system.slice/besclient.service ├─ 25838 /opt/BESClient/bin/BESClient └─ 25839 /opt/BESClient/bin/BESClient -RPMHelperJul 15 09:22:06 sumasrv systemd[1]: Starting BESClient daemon...Jul 15 09:22:06 sumasrv besclient[25830]: Starting BigFix: BESClientJul 15 09:22:06 sumasrv besclient[25824]: ..doneJul 15 09:22:06 sumasrv systemd[1]: Started BESClient daemon.
Seeing the client register to BigFix server I tried to install ILMT Scanner, but result is "Not reported".
Where do I go from here?
Thanks, Igor
PS: I have basic knowledge and rare use of ILMT/BigFix ... not sure where to look...
------------------------------
Igor P. Merkù
------------------------------