SGLX serviceguardmanager

[yilmazaydin]

Hello. 

On the cluster nodes, the space in the /opt directory is rapidly filling up. We analyzed and realized that there are a lot of rest-logs* files in the /opt/hp/cmcluster/serviceguardmanager/rest/logs/ directory.

The contents of all the files are about the same:

2026/02/28 15:36:10,339 [RefreshDaemon] ERROR - [org.apache.log4j::writeLog] 2026-02-28 15:36:10.339 137 [com.hp.utils.CommandUtils] [method :: formNetworkData] [line :: -1] RestException [ex=java.lang.NullPointerException, id=999, additionalMsg=null]
2026/02/28 15:36:10,339 [RefreshDaemon] ERROR - [org.apache.log4j::writeLog] 2026-02-28 15:36:10.339 137 [com.hp.handlers.RefreshDaemon] [method :: run] [line :: -1] RestException [ex=java.lang.NullPointerException, id=999, additionalMsg=null]
2026/02/28 15:36:10,339 [RefreshDaemon] ERROR - [org.apache.log4j::writeLog] 2026-02-28 15:36:10.339 137 [java.lang.Thread] [method :: run] [line :: 825] RestException [ex=java.lang.NullPointerException, id=999, additionalMsg=null]
2026/02/28 15:36:10,487 [RefreshDaemon] ERROR - [org.apache.log4j::writeLog] 2026-02-28 15:36:10.487 137 [com.hp.utils.CommandUtils] [method :: formNetworkData] [line :: -1] RestException [ex=java.lang.NullPointerException, id=999, additionalMsg=null]

I tried to find the cause of the error and could only understand one thing - an error in receiving network data.

How can I fix this error or disable this service?

Regards, YA.

[shiva_jr]

Hi @yilmazaydin , 
   Yes, there may be issue with network. I havn't went through this issue. But I believe the following steps may help you -
a. Run cmviewcl -v to view the cluster and verify
b. Run nwmgr command and verify each network interface and its status
   Ex. nwmgr -q -A id=lan0 
c. Check the network basics such as name resolution for peers, DNS and NTPs are working.
    Ex. nslookup <dnsIP address> or nslookup <peer hostname>
d. Verify the version and network configuration mis-matches on cluster nodes.

Regards,
Shiva_jr

[yilmazaydin]

@shiva_jr Thank you for respond.

In our case we don`t use the serviceguard manager. Can you help me to disable this feature?

Regards, YA.

[shiva_jr]

Hi @yilmazaydin , 

    As per my understanding, we can't disable the rest logs, but you can do the following to reduce the volume of generating logs-
a. Update the SGLX to A.15.30 or later, it fixes the old bugs on logs.
b. Ensure jetty-sgmgr service to be running state.
c. You can change the rootlogger option from ERROR to someother in log4j file, but the ERROR logs will not be recorded. I have no idea about how to do it.

Regards,
Shiva_jr

[support_s]

Hello,

Let us know if you were able to resolve the issue.

If you are satisfied with the answers then kindly click the "Accept As Solution" button for the most helpful response so that it is beneficial to all community members.

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".