ZCM High Server Utilization

  • 7001380
  • 17-Sep-2008
  • 17-Sep-2013

Environment

Novell ZENworks 10 Configuration Management with Support Pack 1 - 10.1

Situation

This issue has 4 effects :

1. High server utilization
2. High memory usage
3. Loading ZCC pages is slow or sometimes will not load, thread deadlocks
4. Users unable to login.

Resolution

This is fixed in version 10.1.1 - see KB 7001406 "ZENworks 10 Configuration Management 10.1.1 - patch information and list of fixes" which can be found at https://www.novell.com/support


Make sure to follow the steps below to configure the rootlogger of log4j with a new configuration file.
 
Windows:
1. Create a log4j.properties file at:
{ZENWORKS_HOME}\share\tomcat\common\classes\
        and
{ZENWORKS_HOME}\conf\loader-logging\


2.  Run {ZENWORKS_HOME}\bin\zenloaderw.exe.
3.  Click on the Java tab.
4.  Add “;{ZENWORKS_HOME}\conf\loader-logging” to the end of the text in the “Java Classpath” edit field (making sure to replace ZENWORKS_HOME with your real ZENWORKS_HOME directory, e.g. C:\Program Files\Novell\ZENworks)
5.  Click OK.
6.  Restart the “Novell ZENworks server” service (this will also restart the “Novell ZENworks loader” service and the “Novell ZENworks Agent Service” service.

Linux:

1. Create a log4j.properties file at:
/opt/novell/zenworks/share/tomcat/common/classes/
        and
/etc/opt/novell/zenworks/loader-logging/


(If you have to create either of those directories make sure you change their ownership to the zenworks user and zenworks group, e.g. “chown zenworks:zenworks loader-logging”)

2. Open /opt/novell/zenworks/bin/zenloader in a text editor.
3. Add the following“:/etc/opt/novell/zenworks/loader-logging/” to the end of the line “CP=$(echo $CP | sed ‘s@ @:@g’)” (should be line 3) to look like:
        CP=$(echo $CP | sed ‘s@@:@g’):/etc/opt/novell/zenworks/loader-logging/
4. Save the file and exit.
5. Restart the novell-zenserver and novell-zenloader daemons (“/etc/init.d/novell-zenserver restart”, “/etc/init.d/novell-zenloader restart”).

Feedback service temporarily unavailable. For content questions or problems, please contact Support.