How to enable debug logging for ZENworks 10, 11 & 2017 Configuration Management

  • 3418069
  • 02-Apr-2008
  • 08-Feb-2019

Environment

Novell ZENworks 10 Configuration management
Novell ZENworks 10 Configuration Management with Support Pack 1 - 10.1
Novell ZENworks 10 Configuration Management with Support Pack 2 - 10.2
Novell ZENworks 10 Configuration Management with Support Pack 3 - 10.3
Novell ZENworks 11 Configuration Management
Novell ZENworks Configuration Management 11.1
Novell ZENworks Configuration Management 11.2
Novell ZENworks Configuration Management 11.3
Novell ZENworks Configuration Management 11.4
ZENworks Configuration Management 2017
ZENworks Configuration Management 2017 Update 1
ZENworks Configuration Management 2017 Update 2

Situation

Troubleshooting ZENworks v10/v11/v2017 Configuration Management
Enable debug logs for ZCM v10/v11/v2017
*Specific to v10.1 or later
**Specific to v10.2 or later
***Specific to v10.2.1 or later
****Specific to v10.3 or later
*****Specific to v11 or later
******Specific to v11.2 or later
 

Resolution



References to %ZENWORKS_HOME% in this document refer to the following paths:
Windows (this is the default path, but can be changed during installation):
Windows 32 bit OS: C:\Program Files\Novell\ZENworks
Windows 64 bit OS: C:\Program Files (x86)\Novell\ZENworks
Linux: /opt/novell/zenworks


Component Name: All components ( zeninfocollect )
See the Novell Documentation for details on using zeninfocollect.

Windows: %ZENWORKS_HOME%\install\downloads\tools\ZENworksInfoCollect_Win.zip
Linux: %ZENWORKS_HOME%/install/downloads/tools/ZENworksInfoCollect_Linux.zip

Enable Debugging:
Windows device:
Extract ZENworksInfoCollect_Win.zip
Run zeninfocollect.exe
Linux server:
Extract ZENworksInfoCollect_Linux.zip
Run zeninfocollect.py


Component Name: zac zeninfo (**New in ZCM 10.2)
Novell Documentation update pending
By default copies zeninfo*.zip to:
Linux: /tmp
Windows: %TEMP%


Component Name: Adaptive Agent

Path to Service Executable:
Windows:
%ZENWORKS_HOME%\bin\ZenworksWindowsService.exe
Linux:
/etc/init.d/novell-zenagent (calls mono /opt/novell/zenworks/bin/ZenLinuxDaemon.exe)

Default Settings:
Device Refresh Schedule:
Full Refresh Schedule: Every 12 hours
Random Time to Wait:
300 seconds minimum, 360 seconds maximum
Enable Debugging:
Windows workstation:
Z Icon Properties > Logging > Log Messages if Severity is > Debug and Above
*or run zac log level debug
Windows server:
Z Icon Properties > Logging > Log Messages if Severity is > Debug and Above
*or run zac log level debug
Linux server:
modify /etc/opt/novell/zenworks/LoggerConfiguration-windows.xml DeviceLocalLogSeverity
*run zac log level debug
 
In 10.2 and later, setting zicon logging severity or zac log level sets HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Zenworks\LocalLogSeverity which governs ZENworks modules, zenlgn and nwgina logging.
In 10.3 and later, setting zicon logging severity or zac log level sets HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZCM\LocalLogSeverity which governs ZENworks modules, zenlgn and nwgina logging.

Log Location:
Windows workstation:
%ZENWORKS_HOME%\logs\LocalStore\zmd-messages.log
Windows server:
%ZENWORKS_HOME%\logs\LocalStore\zmd-messages.log
Linux server:
/opt/novell/zenworks/logs/LocalStore/zmd-messages.log
NOTE: 10.1.2 and later:
before copying zmd-messages.log run "zac emp WakeUp " to integrate all outstanding externalstore log entries.
 
Note 11 and later Linux only:
 
For more verbose logging:
 
zac set CaptureAxis2Logs true (an additional preference to enable the capture of web services responses in the debug logs)



Agent ZENThread logging (use only as needed)
 
Enable Debugging:
 
Set system environment variable:  ZMD_THREAD_POOL_DEBUG=1 reboot.
 
Log Location:  zmd-messages.log
Component Name: Bundles
  1. Obtain the zcc.log from the server (see ZENworks Control Center (ZCC)).
  2. Obtain the %ZENWORKS_HOME%\logs\LocalStore\zmd-messages.log from the managed device (see Adaptive Agent).
  3. Obtain the bundle configuration data by exporting the bundle into xml file using "zman betf <bundle_name> <filename_to_export>"  
***** Linux Bundles:
 
zmd-messages.log
/var/log/zmd-satbackend.log This log only deals with actions taken by the Agent to install an RPM.  It also shows the communication that happens (essentially API Calls) between the Agent and SATLIB. SATLIB is an interface to RPM which actually does the install.
 
 


Component Name: ZCC Helper - 2017

Device running ZCC:

\Users\<userid>\AppData\Roaming\Novell\ZENworks\ZCCHelper\log\zcchelper.log
Server logs:
service-messages.log
zcc.log


Component Name: xplat agent startup
/var/opt/novell/zenworks/novell-zenworks-xplatzmd.out
 

Component Name: Adaptive Agent Uninstall
Log Location:
Windows Workstation: %ZENWORKS_HOME%\logs\novell-zenworks-uninstall.log
****** zesm components also log to
CommonApplicationDataFolder\Novell\ZES\Install
ex:
C:\Documents and Settings\All Users\Application Data\Novell\ZES\
C:\Users\All Users\Application Data\Novell\ZES
setup.exe.log

Component Name: Authentication - NWGina (non-Vista machines)
Enable Debugging:

** The registry settings below are automatically enabled in ZCM 10.2 when "Debug and Above" is set on the agent properties.

Windows Workstation
Location: HKEY_LOCAL_MACHINE\SOFTWARE\Novell\NWGina
Name: EnableDebugMessageLogging
Type: DWORD
Data: 1
Name: MaxLogFileSize
Type: DWORD
Data: 100000

Log Location:
Windows workstation:
\windows\system32\nwgina.log

On Vista, there is no nwgina.log. See zennotify instead.

Note: it is necessary to reboot after enabling this option.

Component Name: Authentication - ZenNotify (Vista)
Enable Debugging:

** The registry settings below are automatically enabled in ZCM 10.2 when "Debug and Above" is set on the agent properties.

Windows Workstation (Vista machines)
Location: HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Authentication\Notify\ZenNotify
Type: DWORD
Value: 00000003
Name: Debug
Type: DWORD
Value: 00000003
 
Log Location:
\windows\system32\ZenNotify.log


Component Name: Authentication - ZenLgn
Enable Debugging:

** The registry settings below are automatically enabled in ZCM 10.2 when "Debug and Above" is set on the agent properties.

Windows workstation:
Location: HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZENworks\ZenLgn
Name: EnableDebugMessageLogging
Type: DWORD
Data: 1

Location: HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Authentication\ZenCredentialProvider
Name: Debug
Type: DWORD
Data: 00000003

Location: HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Authentication\Packages\ZenV1_0
Name: Debug
Type: DWORD
Data: 00000003

Log Location:
Windows workstation:
\windows\system32\zenlgn.log
Note: it is necessary to reboot after enabling this option.


Component Name: Authentication - miCASA client and CASA server

Managed Agent Workstation miCasa Client:

Enable Debugging:
Modify \Program Files\Novell\casa\etc\auth\client.conf to set:
DebugLevel 3
DebugLogFolderPath c:\logfolder (You must first create this folder location)
 
The DebugLevel and DebugLogFolderPath lines in the client.conf file by default are commented out with the # symbol.  Make sure you remove the # at the front of those lines.

Log Location:
Windows workstation:
 
c:\logfolder\casaauthtoken.log or the folder that was set in client.conf
 
****** micasad.log
 
On 32-bit device: Windows_Install_Drive:\Program Files\Novell\CASA\bin
On 64-bit device: Windows_Install_Drive:\Program Files (x86)\Novell\CASA\bin
 
For more verbose logging, modify micasad.exe.config to set TraceLevelSwitch value to 4 and restart the Novell Identity Service
 
ZCM CASA Server:
Path to Service Executable:
Windows: ZENWORKS_HOME \bin\casaserver.exe
Linux: /etc/init.d/casa_atsd (runs as a servlet)

Port: 2645 external CASA

Enable Debugging:
set log4j.rootLogger= (change warn to debug) and restart the service
(Windows):
%ZENWORKS_HOME%\share\ats\etc\svc\log4j.properties
(Linux):
etc/CASA/authtoken/svc/log4j.properties

Log Location (Windows):
all files in %ZENWORKS_HOME%\share\ats\catalinabase\logs\*.*
Log Location (Linux):
all files in /srv/www/casaats/logs/*
 
**** Embedded CASA - Standard ZENworks port (eg: 443):
 
Enable Debugging:
 
see instructions in
(Windows):
ZENWORKS_HOME\share\tomcat\webapps\common\classes\log4j.properties
(Linux)
/opt/novell/zenworks/share/tomcat/common/classes/log4j.properties
 
***** In ZENworks 11:
(Windows)
ZENWORKS_HOME\share\tomcat\conf
(linux)
/opt/novell/zenworks/share/tomcat/conf/log4j.properties
 
Log Location as specified in log4j.properties: log4j.appender.RootAppender.File

Notes:
  • To test if the CASA servlet is running on port 2645, from the managed agent run:
    https://server:2645/CasaAuthTokenSvc/
    collect ats.log and %ZENWORKS_HOME%/share/tomcat/logs/catalina.out (Windows: %ZENWORKS_HOME%\logs), if one exists. If it exists, include it with the ZCM logs.
  • Additionally, Microsoft WinHTTP utility can help for client side tracing. For more verbose listing of traffic to server: go to http://msdn2.microsoft.com/en-us/library/Aa384119.aspx for information about the WinHTTP trace utility and to download and use it.
  • casa service user on linux server: casaatsd member of group casaauth.
  • The catalina.out file should contain only output for tomcat logging and not ZCM logging. ZCC.log and Services-messages.log should now contain the ZCM output that use to go to the catalina.out file.

11.3 and later

zauthhandler.log (user %temp% folder collected with zeninfo)
ZENcredManager.log (windows\system32 not collected with zeninfo until 11.4.3)




Component Name: Bundles

Obtain the zcc.log from the server (see ZENworks Control Center (ZCC) below).

Obtain the %ZENWORKS_HOME%\logs\LocalStore\zmd-messages.logfrom the managed device (see Adaptive Agent above).



Component Name: ZESM logging (includes location awareness even if ZESM spoke is disabled)

See also https://www.novell.com/documentation/zenworks11/zen11_es_security_agent/?page=/documentation/zenworks11/zen11_es_security_agent/data/bookinfo.html
 
Open the ZESM about box
If ZESM is activated: See Endpoint Security link from ZENworks icon properties.
If ZESM is not activated: go to Start > All Programs > Novell > ZESM About
 
Click Diagnostic > logging > Turn on all logging (except NOT packet reports unless needed)  to debug > check save as defaults
 
Duplicate issue.
 
After issue duplication go back to the About Box > Diagnostics > Uncheck everything except System Information and System Event Logs > Create Package
 
The diagnostic package takes a couple minutes to complete and once completed it will be saved to the desktop.
 
Note:  For individual component logging only, optional registry setting may be used:
 
HKLM\Software\novell-zes\log
 
Make a DWORD value set to 1 for any of the components below (case sensitive):
 
Senstivity
General
EventBus
ReportBus
Component
Location
Volume
Policy
Adapter
Template
Firewall
Reporting
BlockedPackets
Ses
Portal
Hardware
FirewallDriver
FSFDDriver
TDIDriver
SesDriver
WirelessDriver
CSD
User
UserComment
Wireless
DFAC
NAC
PolicyComm
VPN
USB
ProcessDriver
Process
Device
Integrity
Script
Store
 


Component Name: Database Migration

Enable Debugging:
Windows: Edit %ZENWORKS_HOME%\conf \novell-zenworks-configure.properties
Linux: Edit /etc/opt/novell/zenworks/conf/novell-zenworks-configure.properties
Under General Settings
Uncomment: #Logger.logLevel (remove the #)
Set the Logger.logLevel= FINEST or FINE
(other log levels to set are CONFIG, INFO, WARNING, SEVERE ,FINE, FINEST Default is INFO)
After the log level is set run the Database Migration tool
Log Location:
Windows: %ZENworks home%\logs\novell-zenworks-configure.log and DBMigration.xml from zenworks_home\bin directory
Linux: /var/opt/novell/log/zenworks/novell-zenworks-configure.log and DBMigration.xml from /opt/novell/zenworks/bin directory
and
zenworks_home\bin\DBMigration.xml



Component Name: Deployment
Enable Debugging (self documenting xml file. Set to FINEST):
Windows server:
%ZENWORKS_HOME%\conf\loader\deployment.xml
Linux server:
/etc/opt/novell/zenworks/loader/deployment.xml
Restart loader service. (novell-zenworks-configure -c Start) will give you the option to restart.
Note: Modify the existing xml file. A file called "copy of discovery.xml" in the same directory will be used if it exists.

Log Location:
Windows server:
%ZENWORKS_HOME%\logs\loader-messages.log
Linux server:
/var/opt/Novell/log/zenworks/loader-messages.log
Windows Workstation:
ZDPASERV.EXE service logfile c:\RemoteSvc.log
%temp%\wincustomaction.log
event log viewer for preagent events
For linux servers that use Windows discovery/deployment proxy, additional logging will be in zmd-messages.log on the proxy device (set to debug).



Component Name: Discovery
 
Enable Debugging (self documenting xml file. Set to FINEST):
Windows server:
%ZENWORKS_HOME%\conf\loader\discovery.xml
Linux server:
/etc/opt/novell/zenworks/loader/discovery.xml
Restart loader service.
Note: Modify the existing xml file. A file called "copy of discovery.xml" in the same directory will be used if it exists.

Log Location:
Windows server:
%ZENWORKS_HOME%\logs\loader-messages.log
%ZENWORKS_HOME%\logs\DiscoveryHarness*.log
Linux server:
/var/opt/novell/log/zenworks/loader-messages.log
For linux servers that use Windows discovery/deployment proxy, additional logging will be in zmd-messages.log on the proxy device (set to debug).

Note:  For more verbose logging of Network Discovery action set the following registry key prior to launching discovery action:

x64:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Tally Systems Corp.\TSCensus\Task Server\Network Discovery]
"LogLevel"=dword:00000000

x32:

[HKEY_LOCAL_MACHINE\SOFTWARE\Tally Systems Corp.\TSCensus\Task Server\Network Discovery]
"LogLevel"=dword:00000000

This logs more information to DiscoveryHarness*.log


Component Name: Group Policies
Enable Debugging:
Windows XP Workstation:bb
Location: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
Name: UserEnvDebugLevel
Type: DWORD
Data: 00030002

Log Location:
Windows Managed Device:
c:\windows\system32\grouppolicy (note: this is a hidden folder). Make a zip file of this folder.
%ZENWORKS_HOME%\bin\handlers\cachefiles . Make a zip file of this folder.
C:\WINDOWS\Debug\UserMode\USERENV.LOG . USERENV.LOG is not enabled by default.
C:\WINDOWS\security\logs\scesrv.log

Windows Vista Windows 7 and Windows 2008 Only:
enable logs
 
set (reboot after setting):
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Diagnostics]
"GPSvcDebugLevel"=dword:00030002
 
  1. %windir%\debug\usermode\gpsvc.log
  2. For security settings get also %windir%\security\logs\scesrv.log
  3. Obtain the event logs by opening the event log viewer and export the logs from the following location:
    Applications and Services Logs\Microsoft\Windows\Group Policy\Operational



Component Name: Imaging
Configuration Files - in these files, the settings have comments to explain their use:
Windows:
%ZENWORKS_HOME%\conf\preboot\novell-pbserv.conf
%ZENWORKS_HOME%\conf\preboot\novell-proxydhcp.conf
%ZENWORKS_HOME%\conf\preboot\novell-tftp.conf
%ZENWORKS_HOME%\conf\preboot\novell-zenimgweb.conf
%ZENWORKS_HOME%\conf\preboot\novell-zmgmcast.conf
%ZENWORKS_HOME%\conf\preboot\novell-zmgprebootpolicy.conf
**%ZENWORKS_HOME%\share\tomcat\webapps\zenworks-preboot\WEB-INF\config.xml:
"...
 <Debug level="6"></Debug>
..."

Restart of novell-zenserver service required.
Linux:
/etc/opt/novell/zenworks/preboot/novell-pbserv.conf
/etc/opt/novell/zenworks/preboot/novell-zenimgweb.conf
/etc/opt/novell/zenworks/preboot/novell-zmgmcast.conf
/etc/opt/novell/zenworks/preboot/novell-zmgprebootpolicy.conf
/etc/opt/novell/novell-proxydhcp.conf
/etc/opt/novell/novell-tftp.conf
** /opt/novell/zenworks/share/tomcat/webapps/zenworks-preboot/WEB-INF/config.xml:
"...
 <Debug level="6"></Debug>
..."

Restart of novell-zenserver service required.

Path to Service Executable:
Windows:
%ZENWORKS_HOME%\bin\preboot\novell-pbserv.exe
%ZENWORKS_HOME%\bin\preboot\novell-proxydhcp.exe
%ZENWORKS_HOME%\bin\preboot\novell-tftp.exe
%ZENWORKS_HOME%\bin\preboot\novell-zmgprebootpolicy.exe
%ZENWORKS_HOME%\bin\preboot\zmgmcast.exe
Linux:
%ZENWORKS_HOME%/preboot/bin/novell-pbservd
%ZENWORKS_HOME%/preboot/bin/novell-zmgmcast
%ZENWORKS_HOME%/preboot/bin/novell-zmgprebootpolicyd
%ZENWORKS_HOME%/preboot/bin/zmgexp

Default Settings:
Path to Images:
Windows:
%ZENWORKS_HOME%\work\content-repo\images
Linux:
/var/opt/novell/zenworks/content-repo/images
 
Log Location:
Windows server:
%ZENWORKS_HOME%\logs\preboot\novell-proxydhcp.log
%ZENWORKS_HOME%\logs\preboot\novell-pbserv.log
%ZENWORKS_HOME%\logs\preboot\novell-tftp.log
%ZENWORKS_HOME%\logs\preboot\novell-zmgprebootpolicy.log
** %ZENWORKS_HOME%\logs\prebootlookup.log
Linux server:
/var/opt/novell/log/zenworks/preboot/novell-pbserv.log
/var/opt/novell/log/zenworks/preboot/novell-zmgprebootpolicy.log
/var/opt/novell/log/novell-proxydhcp.log
/var/opt/novell/log/novell-tftp.log
** /var/opt/novell/log/zenworks/prebootlookup.log
 
Imaging Agent
start Maintenance Mode Imaging, and at the "bash" prompt, type
export DEVELOPER_LOG=a
Then imglog file is created in / (see troubleshooting section of the ZENworks 10 Configuration Management Preboot Services and Imaging Reference)
 
also get

/var/log/boot.msg
 
****** Tuxera imaging driver
 
In addition to all of the above:
 
dmesg >dmesg.txt

SIDchanger sidChange.log is created in /. For more information see Understanding the ZENworks SIDchanger.

ISD update

%ZENWORKS_HOME%\logs\zisd.log
%ZENWORKS_HOME%\bin\preboot\novell-zisdservice.log (vista or higher)
ziswin.hst or ziswin*.log (xp class)



Component Name: Imaging (WIM & GHOST) (**New in ZCM 10.2)
Log Location:
Windows workstation:
%SystemRoot%\system32\WorkToDoDebug.txt
%SystemRoot%\system32\WorkToDoLog.txt
%SystemRoot%\system32\GHOSTerr.txt
%SystemRoot%\system32\TFTPLog


Component Name: Installation - Configuration Management
Path to Service Executable:
Windows: setup.exe
Linux: sh /media/cdrom/setup.sh

Enable Debugging:

Windows server:
setup.exe -j -DLogger.logLevel=(FINE|FINER|FINEST)
or
setup.exe –debug (defaults to FINER)

Linux server:
 
export LAX_DEBUG=true
sh ./setup.sh -j -DLogger.logLevel=(FINE|FINER|FINEST)
or
sh ./setup.sh –debug (defaults to FINER)
 
Log Location (xml files):

Windows server: %ZENWORKS_HOME%\logs

Linux server: /var/opt/novell/log/zenworks
 
Additional Verbose Information:
Windows server: Set the debug level and then while the installation is loading, before the first splash screen, hold down the "control” (Ctrl) key and a Java debug console window will appear after the installation is loaded. (This is the debug equivalent to running export LAX_DEBUG=true on Linux, which displays debug information in the parent terminal)




Component Name: Diagnostics/Probe
Diagnostics/Probe debugging:

zcc.log

Linux:

zen-jmxagent_* from system temp folder
zenserver logs to /var/tmp instead of tmp
external casa logs to /www/srv/casaats/temp

Windows: 

%ZENWORKS_HOME%\share\ats\catalinabase\temp
zen-jmxagent_61493.log

%ZENWORKS_HOME%\share\tomcat\temp
zen-jmxagent_61495.log

ZENworks Service user %temp% directory, eg:
C:\Users\__z_0_8__\AppData\Local\Temp
zen-jmxagent_61491.log
zen-jmxagent_61492.log


Component Name: Inventory
Managed Device Inventory debugging:

Enable Debugging for 2017:

On 2017 agent in debug will log inventory verbosely to zmd-messages.log.  

For test only if colw32 information is needed to use the old collector for comparison, HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZCM\EnableColw32 dword 1

 
 
Enable Debugging:
See Adaptive Agent for setting zmd-messages.log to debug and above
%ZENWORKS_HOME%\logs\LocalStore\zmd-messages.log

For specific inventory collector messages do the following.
  1. Go to <ZENWORKS_HOME>\logs and remove the Colw32.log file that is currently there.
  2. In ZCC | Configuration | Inventory | Inventory (the location to set the collector options) go to the bottom and check the box for Diagnostic Mode .
  3. On the workstation, right click the Z Icon in the System tray and select Show Properties.  Go to the Logging section and set the drop down to Debug and Above.
  4. Go to %ZENWORKS_HOME%\bin\ and open the options.xml file.  Change the diagnostic state to True so the line looks like this.  <option name="Diagnostic" state="true" /> .  Then save the Options.xml file. 
    or
    Create options.txt in program files\novell\zenworks\bin with single line:
    Diagnostic
  5. Restart the Novell ZENworks Agent Service. 
The colw32.log is included with zeninfo, but it is not set to debug level by default.  The above steps need to be followed before running zac zeninfo in order to gather the proper colw32.log.

Log Location:
%ZENWORKS_HOME%\logs\colw32.log

If ARP/MSI collection is enabled:
%ZENWORKS_HOME%\logs\arprecon.log

Test Services:
Inventory file location:
%ZENWORKS_HOME%\work\inventory

Unmanaged Device Inventory debugging:
 
Enable Debugging:
Windows:
 
  1. In ZCC | Configuration | Inventory | Inventory (the location to set the collector options) go to the bottom and check the box for Diagnostic Mode .
    or
    Create options.txt in program files\novell\zenworks\bin with single line:
    Diagnostic
  2. Restart the Novell ZENworks Service. 
 
Log Location
program files\novell\zenworks\logs\colw32.log
 
For more verbose logging (use sparingly!) set the registry (note for x64 under wow32section):
 
[HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZCM\UMIA\Debugging]
"LogName"="zenumia.log"
"LogLevel"=dword:00000001
 
and restart the agent service. 
 
For diagnostic (most verbose) logging create a file in ZENworks\bin folder called cps.ini with the following:

[CollectionClient]
Diagnostic=2

Restart the service and find the logs folder ZENumiaEvent*.log

OSX:
 
Logging is done to /var/log
 
That directory should exist and be writeable. 
 
Log files produced by zenumia are of the form:
zenumiaEventYYYYMMDD.log
zenumia logs are produced only when zenumia is run in diagnostic mode (ZCC Configuration Inventory Only) settings to set diagnostic mode.
 
Collector:  Run (must run as root):
 
./zenumia scannow diagnostic
colosx.log
 
To run system profiler in debug: system_profiler -xml -detailLevel full
 
Install:  /var/log/zenumia-install.log
 

**** Component Name: Inventory Compliance
%ZENWORKS_HOME%\conf\loader\compliance-engine.xml
/etc/opt/novell/zenworks/loader/compliance-engine.xml
set to FINEST

 

**** Component Name: License Collection and Compliance (11.4 and later)

Linux : /var/opt/novell/log/zenworks/loader-messages.log
Windows : %ZENWORKS_HOME%\ZENworks\logs\loader-messages.log
 

Component Name: Asset Management Usage Reporting
HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ZCM\Usage\    key,
create a new DWORD value named "UMDiagnostic " and with a value of 1
Restart the Novell ZENworks Agent Service / start TSUsage32.exe if it is not already running, and the diagnostic window will start.
 
Component Name: Inventory/Asset Management Legacy Reporting

Enable debug: go to
Windows:
%ZENWORKS_HOME%\share\tomcat\webapps\zenworks\WEB-INF\RtrletSetup.xml and change the LoggingLevel setting from INFO to DEBUG
Linux:
/opt/novell/zenworks/share/tomcat/webapps/zenworks/WEB-INF
 
Note: zenserver must be restarted to start the debugging.
Log Location: %ZENWORKS_HOME%\logs\inventory-servlet.log

Component Name: LDAP Import Task
Enable Debugging:
On Linux Server: /etc/opt/novell/zenworks/loader
On Windows Server: Program Files\Novell\Zenworks\conf\loader
File: dirimport.xml
 
<Module>
<Class>com.novell.zenworks.loader.modules.InventoryImportModule</Class>
<Parameters>
<Parameter Name="sleep-interval">30000</Parameter>
<Parameter Name="debug">true</Parameter> //Add this extra parameter
</Parameters>
</Module>
 
Must restart the loader service.



Component Name: Multizone - Zone Sharing

Publisher zone:  services-messages.log and zips,  zcc.log
Subscriber zone:  loader-messages.log and zips, zcc.log

Component Name: NalShell
Enable Debugging:

Note:  On 11.3 and higher this is enabled by default when the agent is set to debug level.  There is no need for the registry setting on 11.3x and higher.

Windows workstation:
Location: HKEY_LOCAL_MACHINE\SOFTWARE\NetWare\Nal\1.0\debug
Name: EnableFile
Type: DWORD
Data: 00000001
Name: Level
Type: DWORD
Data: 0000000f

Log Location:
Windows workstation:
%ZENWORKS_HOME%\logs\NalShell.txt
Windows 7:
%ZENWORKS_HOME%\logs\NSNalWin.txt




Component Name: novell-zenworks-configure
 
Linux:
run export LAX_DEBUG=true

Windows and Linux:
novell-zenworks-configure -c <command> -debug -DLogger.logLevel=FINEST
 
Log location:
screen output and novell-zenworks-configure.log


Component Name: Patch Management
Path to Service Executable:
Windows:
%ZENWORKS_HOME%\zpm\analyze.exe
%ZENWORKS_HOME%\zpm\cabarc.exe
%ZENWORKS_HOME%\zpm\qchain.exe
%ZENWORKS_HOME%\zpm\Remediate.exe

Log Location:
Windows workstation:
Windows Event Viewer - Application Event Log - WSH events
In 10.0.3 and later, enable additional debugging with zicon properties/Logging set Log Messages if Severity is: to Debug and above. Detection results logs and deployment results log files are written to %ZENWORKS_HOME%\ zpm.
%ZENWORKS_HOME%\zpm\*.state file after running zac patch-scan
 
Windows Server:
%ZENWORKS_HOME%\logs\loader-messages.log
%ZENWORKS_HOME%\zpm\rdy.txt
%ZENWORKS_HOME%\zpm\pkglist.txt
%ZENWORKS_HOME%\zpm\log.txt
Linux Server:
/var/opt/novell/log/zenworks/loader-messages.log
%ZENWORKS_HOME%/zpm/rdy.txt
%ZENWORKS_HOME%/zpm/pkglist.txt
%ZENWORKS_HOME%/zpm/log.txt
%ZENWORKS_HOME%/share/tomcat/logs/catalina.out



Component Name: PersonalityMigration

Enable Debugging: modify %ZENWORKS_HOME%\PersonalityMigration\app.config
set the following:  <add key="Enable_Debug" value="true">

Log Location (When executed as Stand Alone Application): %appdata%Novell\PersonalityMigration\PersonalityMigration\10.1.0.0\PersonalityMigration*.xml
Log Location (When executed as bundle - Store/Apply Bundle through ZCM): %ZENWORKS_HOME%\logs\PersonalityMigration\PersonalityLog.log (this is an xml file with .log extension)


Component Name: Pre Agent Installation
Log Location:
Windows workstation:
\windows\novell\zenworks\bin\ZENPreAgent.InstallErr
\windows\novell\zenworks\bin\ZENPreAgent.InstallLog
\windows\novell\zenworks\bin\ZENPreAgent.InstallState
\windows\novell\zenworks\bin\cmdline.txt (The command line executed when the managed agent package was launched)
\windows\novell\zenworks\bin\pre\actions.log (for preagent predeployment commands)
 
Note: Once the PreAgent service is installed, all logging goes to the system application event log.
 
*****Linux Adaptive Agent:
/opt/novell/zenworks/bin (location of original deployment package)
/opt/novell/zenworks/stage (location of extracted deployment package)
/opt/novell/zenworks/stage/ZENPreAgent.log (pre-agent logs)
/var/log/messages
 
****** zesm components also log to
CommonApplicationDataFolder\Novell\ZES\Install
setup.exe.log
 
 
**** if previous agent was removed: %ZENWORKS_HOME\logs\LocalStore\PreviousAgentUninstall.log

******Component Name:  Installation - Macintosh
Log Location:
 
Agent installation: /opt/novell/zenworks/stage/ZENPreAgent.log
Java detection and JRE link creation: /opt/novell/zenworks/stage/InstallJava.log
Verifying installed packages:
Check contents of folder
/Library/Receipts on 10.5
/private/var/db/receipts on 10.6 and 10.7
Agent packages identified by com.novell.pkg.zenworks.*
Patch management package identified by zpm-module
 

Component Name: Remote Management
Enable Debugging:
 
Device being remoted:
 
Set agent logging to debug and above with zicon.
 
Stop “Novell ZENworks Remote Management powered by VNC” service either using cmd or services.msc

Windows workstation set:

For 32 bit device:

HKEY_LOCAL_MACHINE\Software\Novell\ZCM\Remote Management\Agent

For 64 bit device:

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Novell\ZCM\Remote Management\Agent

Enable both of the following:

Name: DebugMode
Type: DWORD
Data: 2

Name: DebugLevel
Type: DWORD
Data: decimal value 10 or hex value ' a'

 
****In 11.4 and later only one key is required and it's the same location for both x32 and x64:

Path: HKLM\Software\Novell\ZCM\Remote Management\Agent
    DebugLevel
    Type: DWORD
    Value: 0-10(Decimal)

After the above registry changes, Restart “Novell ZENworks Remote Management powered by VNC” service either using cmd or services.msc

Device running the browser performing Remote Management:

In the Remote Management Dialog box, select "More Options" and check "Enable logging"
 
Log Locations:
 
Device being remoted:

Windows workstation:
%ZENWORKS_HOME%\logs\WinVnc.log and WinVNCApp.log
%ZENWORKS_HOME% \logs\LocalStore\zmd-messages.log

zac zeninfo is best 

Device running the browser performing Remote Management:

novell-zenworks-vncviewer.txt
location:
Internet Explorer 7 on W2003 or XP: Current user's desktop
Internet Explorer 7 on Vista: last directory browsed from IE 7
Firefox: Firefox directory, for example, C:\Program Files\Mozilla Firefox

11.3 and later viewer log is found in Users\Username\AppData\Roaming\Novell\ZENworks\Remote Management\bin
 
From the server used for ZCC to RM:
 
loader-messages.log
services-messages.log
zcc.log


 

Component Name: JoinProxy

Logs:  %ZENworks_HOME%\zen-join-proxy.log

plus logs above
 

Component Name: Remote Management Proxy (**New in ZCM 10.2)
Enable Debugging:
Windows workstation:
Location: HKLM\Software\Novell\ZENworks\Remote Management\Proxy
Name: DebugMode
Type: DWORD
Data: 2
Location: HKLM\Software\Novell\ZENworks\Remote Management\Proxy
Name: DebugLevel
Type: DWORD
Data: 10
Log Location: path of proxy install \logs\nzr-messages.log
 
For more verbose set DebugMode to 3. 
 
****Linux:
 
Configuration File:
/etc/opt/novell/zenworks/repeater/nzrepeater.ini
 
Log file:
/var/opt/novell/log/zenworks/repeater/nzrepeater.log

 



Component Name: Registration - Web Service
Log Location:
Windows server: %ZENWORKS_HOME%\logs\services-messages.log
Linux server: /var/opt/Novell/log/zenworks/services-messages.log


Component Name: Rights
 
Enable Logging:
%ZENWORKS_HOME%\share\tomcat\webapps\zenworks\WEB-INF\config.xml
Uncomment the line <!--<value>rights</value>--> to read <value>rights</value>
Restart the ZENWORKS Server service
 
Log Location: %ZENWORKS_HOME%\logs\zcc.log
 

Component Name: ZENworks Web Services
 
Log Location:
Windows server: %ZENWORKS_HOME%\logs\services-messages.log
Linux server: /var/opt/novell/log/zenworks/services-messages.log
Debug logging is enabled through the ZCC 'local device logging' setting in Device Managment area of the Configuration page or the device specific 'Settings' page.


Component Name: System Update

Managed Device Update:

Path to Service Executable:
Windows:
%ZENWORKS_HOME%\work\system-update\SystemUpdate.exe
%ZENWORKS_HOME%\bin\ZENUpdater.exe -v -c<path to update-commands.xml>
 
Enable Debugging:
ZENworks System Update service debug logging is enabled by default and cannot be configured.
 
Debug information on the agent can be seen by setting the Agent logging to "Debug and Above"

In addition, the system update loader module logging can be controlled by modifying the SystemUpdate.xml file in the conf/loader directory. The different levels of logging are OFF, SEVERE, WARNING, INFO, FINE, FINER, FINEST

Log Location:
Windows:
%ZENWORKS_HOME%\logs\system-update\<update GUID>\system-update.log and all msi logs
%ZENWORKS_HOME%\logs\LocalStore\zmd-messages.log
%ZENWORKS_HOME%\logs\loader-messages.log
Linux:
/var/opt/novell/log/zenworks/system-update/<update GUID>/system-update.log and all rpm logs
%ZENWORKS_HOME%/logs/LocalStore/zmd-messages.log
/var/opt/novell/log/zenworks/loader-messages.log
NOTE: 10.1.2 and later:
before copying zmd-messages.log run "zac emp WakeUp" to integrate all outstanding externalstore log entries.

FDE update or install

ZFDE_FAILURE_INFO.txt in addition to above.
 
Primary Server Update:

novell-zenworks-configure-migrate-csr.log file Migration of Closest Server Rules to Locations and Network Environment
<log folder>\ZENworks_Upgrade_<date+time>.log  Overall XMLformated upgrade log
<log folder>\system-update-import.log Logs system update commands import
%tmp%/err.log Logs system update install actions
<log folder>\pre-global-actions.log
Logs information related to the schema update
<log folder>\system-update-import.log
  Logs information related to import of the ZCM 11 update

Appliance Update (prior to 11.4):

On remote Appliance 11.2 that was upgraded
/var/opt/novell/log/zenworks/migrate_status
Upgrade Xml log
/tmp/err.log

On local 11.3 Appliance
Appliance_upgrade xml log
 
 

Component : Appliance framework 11.4 and later


/var/opt/novell/log/appliance
/var/opt/novell/jetty/logs
/var/opt/novell/jetty8/logs

setup

/opt/novell/jetty/logs/jetty.stderrout.out

system update

/tmp/err.log
ZENworks_update*.xml

Online update

/var/opt/novell/log/appliance/suse_register.log or suse_regiserE.log
/var/opt/novell/log/OS/zypper.log
/var/opt/novell/jetty/logs


Component : Satellite - Linux (**New in ZCM 10.2 and later)
Path to Service Executable: /etc/init.d/novell-zenworks-xplatzmd
Configuration Files: /etc/opt/novell/zenworks/conf/LoggerConfiguration.properties  (NOTE:  the LoggerConfiguration.properties  file is not created by default but is created upon executing the zac log level DEBUG listed below): DeviceLocalLogSeverity

Enable Debugging:
zac log level DEBUG (to enable Linux Agent debug logs)
zac set CaptureAxis2Logs true (an additional preference to enable the capture of web services responses in the debug logs)
Log location: /var/opt/novell/zenworks/logs/LocalStore/zmd-messages.log


Component: Satellite - Imaging (**New in ZCM 10.2)
Windows:
%ZENWORKS_HOME%\logs\LocalStore\zmd-messages.log
Linux:
/var/opt/novell/zenworks/logs/LocalStore/zmd-messages.log


**** Component: Satellite - Authentication (New in ZCM 10.3)
Linux:
Set zac log level DEBUG
and modify /etc/opt/novell/zenworks/conf/casa/log4j.properties
 
Server log location:
zmd-messages.log, /var/opt/novell/zenworks/logs/ats.log, /var/opt/novell/zenworks/logs/ats.trace
 
Windows:
Set zicon logging to debug and above.
modify /share/ats/etc/svc/log4j.properties
Jetty web server: zenworks\java\lib\core\configuration
Authentication Lock files
 

Component Name: Windows Group Policy Editor Helper

Log Location:
If running ZCC from a managed agent machine, zmd-messages.log; from a non-managed agent machine, zen_gp.log in user's temp directory.
(\Users\<userid>\AppData\Local\Temp\zen_gp.log)



Component Name: ZENworks Control Center (ZCC)

Log Location:
Windows server: %ZENWORKS_HOME%\logs\zcc.log
Linux server: /var/opt/novell/log/zenworks/zcc.log
share/tomcat/webapps/zenworks/web-inf/config.xml debug.tags may be modified for more logging as requested by NTS.
 
For very verbose debugging of ldap requests while drilling into user source in ZCC (use sparingly as it fills zcc.log quickly):
backup logging.properties
Windows: %ZENWORKS_HOME%\share\tomcat\webapps\zenworks\WEB-INF\classes Linux: /opt/novell/zenworks/share/tomcat/webapps/zenworks/WEB-INF/classes
Modify logging.properties to add the line:
log4j.category.com.novell.zenworks.ldap=DEBUG,RollingFileAppender
 
Restart services.
Log is written to zcc.log

To add timestamps modify further to change:

log4j.appender.RollingFileAppender.layout.ConversionPattern=%m%n

to

log4j.appender.RollingFileAppender.layout.ConversionPattern=[%t] %d{ISO8601} %p %C{2} %m%n

Note:  ldap logging can also be enabled to ldaputil.log instead of ZCC.log by modifying instead of above:  /opt/novell/zenworks/share/tomcat/conf/log4j.properties.  Remove # for ldap options.
 
Logging ZCC Libraries: (*** new to ZCM 10.2.1)
Windows: %ZENWORKS_HOME%\share\tomcat\webapps\zenworks\WEB-INF\classes Linux: /opt/novell/zenworks/share/tomcat/webapps/zenworks/WEB-INF/classes
Modify logging.properties to remove the comment (#) from the six lines following
# RollingFileAppender2
so that the section looks like this:
RollingFileAppender2
log4j.appender.RollingFileAppender2=org.apache.log4j.RollingFileAppender
log4j.appender.RollingFileAppender2.MaxFileSize=5MB
log4j.appender.RollingFileAppender2.MaxBackupIndex=10
log4j.appender.RollingFileAppender2.File=${zenworks.log.directory}/zcc-lib.log
log4j.appender.RollingFileAppender2.layout=org.apache.log4j.PatternLayout
log4j.appender.RollingFileAppender2.layout.ConversionPattern=%m%n

Restart services.
Log is written to the specified file (default is zcc-lib.log)
Windows server: %ZENWORKS_HOME%\logs\zcc-lib.log
Linux server: /var/opt/Novell/log/zenworks/zcc-lib.log

 Component Name: ZENworks Reporting Server 5 and 6.2 (Jaspersoft)

Configuration file:


/opt/novell/zenworks-reporting/conf/zrs-configuration.xml

Install Logs location:
Linux: logs from /var/opt/novell/zenworks-reporting/log, installation.log from /opt/novell/zenworks-reporting/js, logs from /opt/novell/zenworks-reporting/js/apache-tomcat/logs and ZENworks_Reporting_InstallLog.log from /opt/novell/zenworks-reporting
Windows: Logs from %ZRS_HOME%\log and ZENworks_Reporting_InstallLog from %ZRS_HOME%, logs from %ZRS_HOME%\js\apache-tomcat\logs and installation.log %ZRS_HOME%\js
 
Configuration Logs location:
Linux: Logs from /var/opt/novell/zenworks-reporting/log
Windows: Logs from %ZRS_HOME%\log
 
Domain and reports Logs location:
Linux: Logs from /opt/novell/zenworks-reporting/js/apache-tomcat/webapps/jasperserver-pro/WEB-INF/logs
Windows: Logs from %ZRS_HOME%\js\apache-tomcat\webapps\jasperserver-pro\WEB-INF\logs



Component Name: ZAM Migration

Enable debug tab: Ctrl-shift-click on Novell icon
Log Location: %ZENWORKS_HOME%\logs\ZAMMigration.log
Note: Debug logging is always enabled

 

Component Name: ZENworks Migration

Ctrl+Shift+double click header (red N) opens unit test and debug log.

Logs Location and History files: C:\Documents and Settings\<USERNAME>\Application Data\Novell\ZENworks\Migration

For file upload problems, see Server services-messages.log File [Upload Servlet] for the same guid.zip listed on the migration log.


Component Name: ZENworks Reporting Server (Business Objects Enterprise) -Installation and Deployment and Uninstall
Enable Debugging:
 
Enable Debugging:
Windows server:
setup.exe -j -DLogger.logLevel=(FINE|FINER|FINEST)
or
setup.exe debug (defaults to FINER)
 
Linux server:
 
export LAX_DEBUG=true
sh ./setup.sh -j -DLogger.logLevel=(FINE|FINER|FINEST)
or
sh ./setup.sh debug (defaults to FINER)
 
Log Location (xml files):
Windows server: %ZENWORKS_HOME% \logs
Linux server: /var/opt/novell/log/zenworks
 
Additional Verbose Information:
Windows server: Set the debug level and then while the installation is loading, before the first splash screen, hold down the "control (Ctrl) key and a Java debug console window will appear after the installation is loaded. (This is the debug equivalent to running export LAX_DEBUG=true on Linux, which displays debug information in the parent terminal)
 
Log Locations:
 
If you install ZENworks Reporting Server through the Graphical User Interface (GUI) Installer on the Reporting Server DVD, then the logs can be found at:

Windows:
%ZENWORKS_HOME%\logs\ZENworks Reporting Server_<date> <time>.log.xml
%ZENWORKS_HOME%\logs\wdeploy-<date>-<time>.log
Windows event logs
%zenworks_home%\share\boe\Business Objects Enterprise 12.0\logging\*.*

Linux:
/var/opt/novell/log/zenworks/ZENworks Reporting Server__<date> <time>.log.xml
/var/opt/novell/log/zenworks/wdeploy-<date>-<time>.log
/var/opt/novell/share/boe/setup/logs/*.*
/opt/novell/zenworks/share/boe/bobje/logging/boe_install.log or install*.log
 
If you install ZENworks Reporting server install GUI:
%ZENWORKS_HOME%\logs\zenworks_install__.log
 
If reporting was installed through command line:
Run "novell-zenworks-configure” with "-ddd” option to enable full logging
%ZENWORKS_HOME%\logs\novell-zenworks-configure.log file
%ZENWORKS_HOME%\logs\wdeploy__.log
Windows: %ZENWORKS_HOME%\share\boe\Business Objects Enterprise 115\logging\install.log file
Linux: %ZENWORKS_HOME%/share/boe/logs
Uninstall logs:ZRSUninstall.*
 

Component Name: ZENworks Reporting Server (Business Objects Enterprise) - Services

To enable logging for BOE services, add a -trace option in the command to start services using Central Configuration Manager.
Log Locations:
%ZENWORKS_HOME%\share\boe\Business Objects Enterprise 115\logging
** 10.2 and later
Windows :
Go To : Start > Program Files > ZENworks Reporting Server > Central Configration Manager
Stop the SIA , Double click it. Add ‘-trace’ to End of Command field and start SIA.
Linux :
add '-trace' to the line starts with 'ZENReportingLAUNCH' in /opt/novell/zenworks/share/boe/bobje/ccm.config
restart ZRS Server.

Windows:
Windows Event Logger.
%zenworks_home%\share\boe\Business Objects Enterprise 120\logging
Linux:
/opt/novell/zenworks/share/boe/bobje/logging/
 
ZCC.log
 
all files from /opt/novell/zenworks/share/boe/bobje/tomcat/logs
all files from /opt/novell/zenworks/share/boe/bobje/logging
 

Component Name: ZENworks Reporting Server (Business Objects Enterprise) - User Source Report
 
%ZENWORKS_HOME%\logs\ZRS_LDAP_DRIVER.trace

Component Name: ZENworks Web Services

Log Location:
Windows server: %ZENWORKS_HOME%\logs\services-messages.log
Linux server: /var/opt/novell/log/zenworks/services-messages.log



Component Name: ZENworks Server Connections

Enable Debugging for server busy:
Warning: This creates many large files so use only temporarily
 
backup and modify %ZENWORKS_HOME%/share/tomcat/conf/server.xml
find and modify the following line to add debug:
<Valve className="com.novell.zenworks.tomcat.ZENRequestValve" debug="true"/>
Log File:
%ZENWORKS_HOME%/share/tomcat/logs/zenrequestvalve-xxxx.log



Component Name: ziswin

Path to Service Executable: %ZENWORKS_HOME%\bin\preboot
 
Enable Debugging: Create a registry entry ZISWin Log with DWORD value 1 under HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Zenworks
Log Location: C:\WINDOWS\Temp\ZISWIN.log
 

Component Name: zicon menu display
zenicon.log in  users %TEMP% directory
****** Macintosh agent: find /private -name zenicon.log


Component Name: zman
Configuration Files:
Windows:
%ZENWORKS_HOME%\conf\zman\properties\zman-config.properties
Set DEBUG_LEVEL=4
Linux:
/etc/opt/novell/zenworks/zman/properties/zman-config.properties
Set DEBUG_LEVEL=4
Path to Service Executable:
Windows:
%ZENWORKS_HOME%\bin\zman.exe
Linux:
%ZENWORKS_HOME%/bin/zman
Enable Debugging:
Windows Server:
%ZENWORKS_HOME%\conf\zman\properties\zman-config.properties
Set DEBUG_LEVEL=4
Linux:
/etc/opt/novell/zenworks/zman/properties/zman-config.properties
Set DEBUG_LEVEL=4

Log Location:
Windows server:
%ZENWORKS_HOME%\logs\zman.log
Linux server:
/var/opt/novell/log/zenworks/zman.log

For more verbose logging use level 4 and --debug to output trace debugging to screen.  
 

Component Name: General SQL Logging
Enable logging by editing the log at:
Windows: %ZENWORKS_HOME%\share\tomcat\common\classes\log4j.properties
Linux: /opt/novell/zenworks/share/tomcat/common/classes/log4j.properties
 
*****ZENworks 11
Windows: %ZENWORKS_HOME%\share\tomcat\conf\log4j.properties
Linux: /opt/novell/zenworks/share/tomcat/conf/log4j.properties
 
Add the following info to the file (Make sure the path to the log file reflects either the platform of the primary server.)

log4j.logger.org.hibernate.SQL=DEBUG, HibernateAppender
log4j.logger.org.hibernate.type=TRACE, HibernateAppender
log4j.additivity.org.hibernate.SQL=false
log4j.appender.HibernateAppender=org.apache.log4j.RollingFileAppender
# Uncomment the following line when configuring it on Windows platform
#log4j.appender.HibernateAppender.File=C:\\Program Files\\Novell\\ZENworks\\logs\\hibernate.log
# Uncomment the following line when configuring it on Linux platform
log4j.appender.HibernateAppender.File=/var/opt/novell/log/zenworks/hibernate.log
log4j.appender.HibernateAppender.MaxFileSize=20MB
log4j.appender.HibernateAppender.MaxBackupIndex=5
log4j.appender.HibernateAppender.layout=org.apache.log4j.PatternLayout
log4j.appender.HibernateAppender.layout.ConversionPattern=%d{ISO8601} %p [%x] %m%n
 
*After collecting the logs rename the log4j.properties file, to disable the logging, and restart 'Novell ZENworks Server' service through the Windows service manager (services.msc) or '/etc/init.d/novell-zenserver restart' on Linux.

Component Name: OEM Sybase Database
 
Use Sparingly only as needed, as log can get big!!!! 

Make a backup of the file and Enable Logging by adding the following to the zenworks_database.conf file and restarting the sybase database:
-zs 50M
-zr all
-z
-zt
-o /var/opt/novell/zenworks/database/sybase_debug.log
 
Log Location:
As specified in the zenworks_database.conf file located at:
 
Windows server: %ZENWORKS_HOME%\conf\zenworks_database.conf
Linux server: /etc/opt/novell/zenworks/zenworks_database.conf
 
To restart the database,
On Linux run: /etc/init.d/sybase-asa restart
On Windows, open up service manager (services.msc) and restart the "Novell ZENworks Embedded Datastore" service.
 

*****Component Name: Subscription Processing - also referred to as Linux Package Management (LPM) or ZENworks Linux Management (ZLM)
Location: /var/opt/novell/log/zenworks
zman.log
zcc.log
services_messages.log This log shows communication to the database to get object information.
loader_messages.log  This log shows replication and download information such as from the NCC, content-repo activity, and information related to exporting a repository.
Enable Debug:
/etc/opt/novell/zenworks/lpm-server.properties set Debug=true This affects only what goes into the loader-messages.log file. This setting will override whatever the settings is in the zone, only for Subscriptions

 
*****Component Name: 11.4 Appliance migration
Logs Location
/tmp/ApplianceMigrationUtility.log

*****Component Name: Admin Studio
Logs:  Install Directory\common\*.log 




 

Additional Information

iPrint logging for iPrint policies:

Enable the following registry options and retart "Spooler" service or reboot to enable the iPrint logging under "C:\NDPS\" folder:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Novell-iPrint\Settings]
"TraceOn"=dword:00000002

[HKEY_LOCAL_MACHINE\SOFTWARE\Novell-iPrint\Settings\Trace Options]
"TimeOn"=dword:00000001
"ThreadOn"=dword:00000001
"ModuleOn"=dword:00000001
"LineOn"=dword:00000001
"UserOn"=dword:00000001
"TcpOn"=dword:00000001
"HttpOn"=dword:00000001
"IppOn"=dword:00000001
"ProvidorOn"=dword:00000001
"BrowserOn"=dword:00000001
"MemoryOn"=dword:00000000
"Session"=dword:00000001