PRETTY_NAME="openSUSE Leap 15.3"

Hi,

we have a (single) server with OpenSuSE 15.3 running. There is no specific BESClient for OpenSUSE, only SUSE Linux in general.

Anyone else experiencing this? Any idea?

How could I investigate for the reason?

Thanks, Igor

Hello,

Is there any error message logged into the client logs ?

https://www.ibm.com/support/pages/common-file-locations

If you issue "service besclient start", is the client starting or you are getting any error message ?

Thank you.

PRETTY_NAME="openSUSE Leap 15.3"

Hi,

we have a (single) server with OpenSuSE 15.3 running. There is no specific BESClient for OpenSUSE, only SUSE Linux in general.

Anyone else experiencing this? Any idea?

How could I investigate for the reason?

Thanks, Igor

Hi Andrei, thanks for your reply.

Found some log files, not sure what to look at ... shall I upload the latest log file?

Yes, BESClient starts, but dies shortly after.

Thanks, Igor

Hello,

Is there any error message logged into the client logs ?

https://www.ibm.com/support/pages/common-file-locations

If you issue "service besclient start", is the client starting or you are getting any error message ?

Thank you.

PRETTY_NAME="openSUSE Leap 15.3"

Hi,

we have a (single) server with OpenSuSE 15.3 running. There is no specific BESClient for OpenSUSE, only SUSE Linux in general.

Anyone else experiencing this? Any idea?

How could I investigate for the reason?

Thanks, Igor

Hi Igor,

Check if the issue is this one documented here:

https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0078749

If this is not related, please open a case against ILMT product and upload the entire logs folder.

Thanks.

Hi Andrei, thanks for your reply.

Found some log files, not sure what to look at ... shall I upload the latest log file?

Yes, BESClient starts, but dies shortly after.

Thanks, Igor

Hello,

Is there any error message logged into the client logs ?

https://www.ibm.com/support/pages/common-file-locations

If you issue "service besclient start", is the client starting or you are getting any error message ?

Thank you.

PRETTY_NAME="openSUSE Leap 15.3"

Hi,

we have a (single) server with OpenSuSE 15.3 running. There is no specific BESClient for OpenSUSE, only SUSE Linux in general.

Anyone else experiencing this? Any idea?

How could I investigate for the reason?

Thanks, Igor

Hi Andrei,

I don't think this fits.

sodasrv:/var/lock/subsys # systemctl start besclient
sodasrv:/var/lock/subsys # ls
sodasrv:/var/lock/subsys # systemctl status besclient
● besclient.service - BESClient daemon
     Loaded: loaded (/usr/lib/systemd/system/besclient.service; enabled; vendor preset: disabled)
     Active: active (running) since Tue 2023-03-07 10:53:03 CET; 9s ago
    Process: 29113 ExecStart=/usr/local/bin/besclient start (code=exited, status=0/SUCCESS)
      Tasks: 8 (limit: 4915)
     CGroup: /system.slice/besclient.service
             ├─29115 /usr/local/bin/besclient start
             └─29116 /opt/BESClient/bin/BESClient -RPMHelper

Mar 07 10:53:03 sodasrv systemd[1]: Starting BESClient daemon...
Mar 07 10:53:03 sodasrv systemd[1]: Started BESClient daemon.
sodasrv:/var/lock/subsys # ps -ef | grep -i besc
root     29115     1  4 10:53 ?        00:00:00 /usr/local/bin/besclient start
nobody   29116 29115  5 10:53 ?        00:00:00 /opt/BESClient/bin/BESClient -RPMHelper
sodasrv:/var/lock/subsys # ls
sodasrv:/var/lock/subsys # ps -ef | grep -i besc
root     29115     1  3 10:53 ?        00:00:00 /usr/local/bin/besclient start
nobody   29116 29115  2 10:53 ?        00:00:00 /opt/BESClient/bin/BESClient -RPMHelper
(...)

sodasrv:/var/lock/subsys # systemctl status besclient
● besclient.service - BESClient daemon
     Loaded: loaded (/usr/lib/systemd/system/besclient.service; enabled; vendor preset: disabled)
     Active: active (running) since Tue 2023-03-07 10:53:03 CET; 1min 1s ago
    Process: 29113 ExecStart=/usr/local/bin/besclient start (code=exited, status=0/SUCCESS)
      Tasks: 7 (limit: 4915)
     CGroup: /system.slice/besclient.service
             └─29115 /usr/local/bin/besclient start

Mar 07 10:53:03 sodasrv systemd[1]: Starting BESClient daemon...
Mar 07 10:53:03 sodasrv systemd[1]: Started BESClient daemon.
sodasrv:/var/lock/subsys # ps -ef | grep -i besc
root     29115     1  2 10:53 ?        00:00:01 /usr/local/bin/besclient start
root     29720 19396  0 10:54 pts/0    00:00:00 grep --color=auto -i besc

sodasrv:/var/lock/subsys # ls

sodasrv:/var/lock/subsys #

OK, then, I'll go and open a case.

Thanks, Igor

Hi Igor,

Check if the issue is this one documented here:

https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0078749

If this is not related, please open a case against ILMT product and upload the entire logs folder.

Thanks.

Hi Andrei, thanks for your reply.

Found some log files, not sure what to look at ... shall I upload the latest log file?

Yes, BESClient starts, but dies shortly after.

Thanks, Igor

Hello,

Is there any error message logged into the client logs ?

https://www.ibm.com/support/pages/common-file-locations

If you issue "service besclient start", is the client starting or you are getting any error message ?

Thank you.

PRETTY_NAME="openSUSE Leap 15.3"

Hi,

we have a (single) server with OpenSuSE 15.3 running. There is no specific BESClient for OpenSUSE, only SUSE Linux in general.

Anyone else experiencing this? Any idea?

How could I investigate for the reason?

Thanks, Igor

Hi Igor,

It seems that openSUSE OS is not supported for the BESClient installation, yet.

Thank you.

Hi Andrei,

I don't think this fits.

sodasrv:/var/lock/subsys # systemctl start besclient
sodasrv:/var/lock/subsys # ls
sodasrv:/var/lock/subsys # systemctl status besclient
● besclient.service - BESClient daemon
     Loaded: loaded (/usr/lib/systemd/system/besclient.service; enabled; vendor preset: disabled)
     Active: active (running) since Tue 2023-03-07 10:53:03 CET; 9s ago
    Process: 29113 ExecStart=/usr/local/bin/besclient start (code=exited, status=0/SUCCESS)
      Tasks: 8 (limit: 4915)
     CGroup: /system.slice/besclient.service
             ├─29115 /usr/local/bin/besclient start
             └─29116 /opt/BESClient/bin/BESClient -RPMHelper

Mar 07 10:53:03 sodasrv systemd[1]: Starting BESClient daemon...
Mar 07 10:53:03 sodasrv systemd[1]: Started BESClient daemon.
sodasrv:/var/lock/subsys # ps -ef | grep -i besc
root     29115     1  4 10:53 ?        00:00:00 /usr/local/bin/besclient start
nobody   29116 29115  5 10:53 ?        00:00:00 /opt/BESClient/bin/BESClient -RPMHelper
sodasrv:/var/lock/subsys # ls
sodasrv:/var/lock/subsys # ps -ef | grep -i besc
root     29115     1  3 10:53 ?        00:00:00 /usr/local/bin/besclient start
nobody   29116 29115  2 10:53 ?        00:00:00 /opt/BESClient/bin/BESClient -RPMHelper
(...)

sodasrv:/var/lock/subsys # systemctl status besclient
● besclient.service - BESClient daemon
     Loaded: loaded (/usr/lib/systemd/system/besclient.service; enabled; vendor preset: disabled)
     Active: active (running) since Tue 2023-03-07 10:53:03 CET; 1min 1s ago
    Process: 29113 ExecStart=/usr/local/bin/besclient start (code=exited, status=0/SUCCESS)
      Tasks: 7 (limit: 4915)
     CGroup: /system.slice/besclient.service
             └─29115 /usr/local/bin/besclient start

Mar 07 10:53:03 sodasrv systemd[1]: Starting BESClient daemon...
Mar 07 10:53:03 sodasrv systemd[1]: Started BESClient daemon.
sodasrv:/var/lock/subsys # ps -ef | grep -i besc
root     29115     1  2 10:53 ?        00:00:01 /usr/local/bin/besclient start
root     29720 19396  0 10:54 pts/0    00:00:00 grep --color=auto -i besc

sodasrv:/var/lock/subsys # ls

sodasrv:/var/lock/subsys #

OK, then, I'll go and open a case.

Thanks, Igor

Hi Igor,

Check if the issue is this one documented here:

https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0078749

If this is not related, please open a case against ILMT product and upload the entire logs folder.

Thanks.

Hi Andrei, thanks for your reply.

Found some log files, not sure what to look at ... shall I upload the latest log file?

Yes, BESClient starts, but dies shortly after.

Thanks, Igor

Hello,

Is there any error message logged into the client logs ?

https://www.ibm.com/support/pages/common-file-locations

If you issue "service besclient start", is the client starting or you are getting any error message ?

Thank you.

PRETTY_NAME="openSUSE Leap 15.3"

Hi,

we have a (single) server with OpenSuSE 15.3 running. There is no specific BESClient for OpenSUSE, only SUSE Linux in general.

Anyone else experiencing this? Any idea?

How could I investigate for the reason?

Thanks, Igor