JSVC process causes high utilization when changing inventory settings for SLES primary server.

  • 7005883
  • 30-Apr-2012
  • 14-Jul-2014

Environment

Novell ZENworks 11 Configuration Management Support Pack 2 - ZCM 11 SP2 Inventory
Novell ZENworks 11 Configuration Management Support Pack 1 - ZCM 11 SP1 Inventory
SUSE Linux Enterprise Server 10 Service Pack 3
SUSE Linux Enterprise Server 11 Service Pack 1

Situation

A SLES based primary server will go into a high utilization state when the default settings for inventory schedule are changed in ZCC > Configuration > Inventory > Inventory Schedule, to Fixed Interval. The server will stay in the higher utilization state and not recover.

Resolution

For cause 1 (see below):
This is fixed in version 11.2.2 - see KB 7010757 "ZENworks Configuration Management 11.2.2 - update information and list of fixes" which can be found at https://support.microfocus.com/kb/doc.php?id=7010757

For cause 2: (see below):
This is fixed in version 11.2.4 - see KB 7012027 "ZENworks Configuration Management 11.2.4 - update information and list of fixes" which can be found at https://support.microfocus.com/kb/doc.php?id=7012027&path=37&number=f.2

Workaround:
  1. In ZCC > Devices > Servers > YourServerName > Settings Tab > Inventory > Inventory Schedule, select Override settings, then change the schedule to Monthly and click on the Apply button.
  2. On the server stop the ZCM services using the 'novell-zenworks-configure -c Start' command. Note, this command will bring up a menu that allows the selection of the services to be started or stopped, and also allows a selection to start or stop them. (See screen-shot below)



    In the above screen shot the option to stop services was selected by entering '12' and then pressing the 'Enter' key.

  3. Watch for the JSVC process to stop. If the JSVC process unloads and utilization drops back to normal then start the ZCM services using the 'novell-zenworks-configure -c Start' command. If the utilization stays high or the JSVC process does not stop, then reboot the server.

Cause

The cause of this issue was determined to be the following:

1- The past due setting is not honored by the inventory manager.

2- The TESS module is triggering an event that does not seem to stop as it should.