Novell®
www.novell.com
Troubleshooting guide
ZENworks® Linux Management
novdocx (en) 11 July 2008
AUTHORIZED DOCUMENTATION
7.2 IR2
August 22, 2008
Novell ZENworks 7.2 Linux Management Troubleshooting Guide
Legal Notices
Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and
specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose.
Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time,
without obligation to notify any person or entity of such revisions or changes.
Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims
any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc.
reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to
notify any person or entity of such changes.
Any products or technical information provided under this Agreement may be subject to U.S. export controls and the
trade laws of other countries. You agree to comply with all export control regulations and to obtain any required
licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities
on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export
laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses.
See the Novell International Trade Services Web page (http://www.novell.com/info/exports/) for more information
on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export
approvals.
novdocx (en) 11 July 2008
Copyright © 2007-2008 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied,
stored on a retrieval system, or transmitted without the express written consent of the publisher.
Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this
document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S.
patents listed on the Novell Legal Patents Web page (http://www.novell.com/company/legal/patents/) and one or
more additional patents or pending patent applications in the U.S. and in other countries.
Novell, Inc.
404 Wyman Street, Suite 500
Waltham, MA 02451
U.S.A.
www.novell.com
Online Documentation: To access the online documentation for this and other Novell products, and to get
updates, see the Novell Documentation Web page (http://www.novell.com/documentation).
Novell Trademarks
For Novell Trademarks, see the Novell Trademark and Service Mark list (http://www.novell.com/company/legal/
trademarks/tmlist.html)
Third-Party Materials
All third-party trademarks are the property of their respective owners.
novdocx (en) 11 July 2008
novdocx (en) 11 July 2008
Contents
About This Guide 7
Part I Installation, Upgrade, and ZENworks Database 9
1 Installation and Upgrade Troubleshooting Strategies 11
1.1 Troubleshooting the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.2 Troubleshooting the Upgrade Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Part II Policy Handlers 15
2 Policy Handlers Error Messages 17
2.1 General Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.2 Remote Execute Policy Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
novdocx (en) 11 July 2008
3 Policy Handlers Troubleshooting Strategies 25
3.1 General Troubleshooting Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.2 Troubleshooting the Epiphany Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.3 Troubleshooting the Generic GNOME Policy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3.4 Troubleshooting the Remote Execute Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.5 Troubleshooting the Text File Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Part III Event Monitoring 33
4 Event Monitoring Troubleshooting Strategies 35
4.1 Troubleshooting Event Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Part IV Inventory 37
5 Inventory Roll-Up Error Messages 39
6 Inventory Troubleshooting Strategies 43
6.1 Troubleshooting Inventory Roll-Up. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
6.2 Troubleshooting Hardware Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Part V Disaster Recovery 47
7 Disaster Recovery 49
7.1 Safeguarding Your System through Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7.1.1 The Data Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7.1.2 The Object Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Contents 5
7.1.3 The Package Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
7.1.4 The zlmmirror Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
7.2 Safeguarding Your System through Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
7.2.1 Data Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
7.2.2 Object Store. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
7.2.3 Package Repository. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
7.2.4 Message Logger . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
7.3 Restoring Your System after a Primary Server Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
7.3.1 Converting a Secondary Server to a Primary Server. . . . . . . . . . . . . . . . . . . . . . . . . 52
7.4 Moving Devices to the New Primary Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
8 Disaster Recovery Error Messages 55
Part VI Remote Management 57
9 Remote Management Error Messages 59
10 Remote Management Troubleshooting Strategies 63
novdocx (en) 11 July 2008
Part VII Dell DTK 67
11 Dell Configuration Bundle Troubleshooting Strategies 69
Part VIII Package and Content Management 71
12 Package and Content Management Error Messages 73
13 Package and Content Management Troubleshooting Strategies 75
Part IX Preboot Services 79
14 Preboot Services Troubleshooting Strategies 81
A Documentation Updates 83
A.1 August 22, 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
A.2 May 19, 2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
A.2.1 Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
A.2.2 Package and Content Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
A.3 August 23, 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
A.3.1 Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
A.4 May 21, 2007 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
A.4.1 Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6 Novell ZENworks 7.2 Linux Management Troubleshooting Guide
About This Guide
novdocx (en) 11 July 2008
This guide includes troubleshooting strategies that you can use and error messages that might be
displayed for problems that could occur as you use Novell
your production environment.
As administrators gain experience using Linux Management, some unusual or previously untested
implementation scenarios and undocumented product limitations might surface. We will gather this
feedback from Novell customers and add it to this guide as it becomes practical to do so.
The guide is intended for network administrators and is divided into the following sections:
Part I, “Installation, Upgrade, and ZENworks Database,” on page 9
Part II, “Policy Handlers,” on page 15
Part III, “Event Monitoring,” on page 33
Part IV, “Inventory,” on page 37
Part V, “Disaster Recovery,” on page 47
Part VI, “Remote Management,” on page 57
Part VII, “Dell DTK,” on page 67
Part VIII, “Package and Content Management,” on page 71
Appendix A, “Documentation Updates,” on page 83
Documentation Conventions
®
ZENworks® 7.2 Linux Management in
In Novell documentation, a greater-than symbol (>) is used to separate actions within a step and
items in a cross-reference path.
A trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party
trademark.
When a single pathname can be written with a backslash for some platforms or a forward slash for
other platforms, the pathname is presented with a backslash. Users of platforms that require a
forward slash, such as Linux* or UNIX*, should use forward slashes as required by your software.
Feedback
We want to hear your comments and suggestions about this manual and the other documentation
included with this product. Please use the User Comments feature at the bottom of each page of the
online documentation, or go to Novell Documentation Feedback site (http://www.novell.com/
documentation/feedback.html) and enter your comments there.
Additional Documentation
For the latest documentation on installing or upgrading to ZENworks 7.2 Linux Management, see
the Novell ZENworks 7.2 Linux Management Installation Guide.
For the latest documentation on configuring and managing ZENworks 7 Linux Management, see the
Novell ZENworks 7.2 Linux Management Administration Guide.
About This Guide 7
novdocx (en) 11 July 2008
8 Novell ZENworks 7.2 Linux Management Troubleshooting Guide
I
Installation, Upgrade, and
novdocx (en) 11 July 2008
ZENworks Database
The following section provides solutions to problems you might encounter when installing the
®
Novell
ZENworks® 7.2 Linux Management, or working with the ZENworks Database:
Chapter 1, “Installation and Upgrade Troubleshooting Strategies,” on page 11
I
Installation, Upgrade, and ZENworks Database
9
novdocx (en) 11 July 2008
10 Novell ZENworks 7.2 Linux Management Troubleshooting Guide
1
Installation and Upgrade
novdocx (en) 11 July 2008
Troubleshooting Strategies
The following sections provide solutions to the problems you might encounter when installing or
upgrading to Novell
Section 1.1, “Troubleshooting the Installation,” on page 11
Section 1.2, “Troubleshooting the Upgrade Scripts,” on page 13
1.1 Troubleshooting the Installation
“Install randomly fails when zlm-config fails to complete” on page 11
“Zmd hangs randomly on the managed device” on page 11
“Installation of signed packages using rug fails on SLES 9, NLD, and Red Hat platforms” on
page 11
“ZENworks Server installation on SLES 10 fails with the error, “Resolvable not found”” on
page 12
“How do I recover the password for the ZENworks Server?” on page 12
“Executing the rug ref command on the PPC, IPF, and zSeries devices results in exceptions
related to Inventory” on page 12
®
ZENworks® Linux Management:
1
Install randomly fails when zlm-config fails to complete
Source: ZENworks Linux Management, Installation of the ZENworks Agent.
Action: Re-run zlm-config.
Zmd hangs randomly on the managed device
Source: ZENworks Linux Management, Installation of the ZENworks Agent.
Explanation: The ZENworks Agent (zmd) hangs on the managed device and displays the
message “zmd inactive” when the managed device is kept idle for more than a
day.
Action: Restart zmd on the managed device.
Installation of signed packages using rug fails on SLES 9, NLD, and Red Hat
platforms
Source: ZENworks Linux Management, Installation
Explanation: If the zmd security- level preference is set to signature, the installation of a
signed package using rug would fail with the following error: Unable to
verify package signature.
Action: Do the following:
1 Verify signature manually using the following rpm command:
Installation and Upgrade Troubleshooting Strategies
11
rpm --checksig -v package_name
2 Change the security- level preference to checksum or none as shown
below:
rug set security-level checksum
ZENworks Server installation on SLES 10 fails with the error, “Resolvable not found”
Source: ZENworks Linux Management, ZENworks Server
Action: Do the following:
1 Remove the openldap2 package from the system by executing rpm -
e openldap2 command.
2 Install the ZENworks Server. For detailed information on installing the
ZENworks Server, see “Installation” in the Novell ZENworks 7.2 Linux
Management Installation Guide.
How do I recover the password for the ZENworks Server?
novdocx (en) 11 July 2008
Source: ZENworks Linux Management, ZENworks Server
Action: Do the following:
1 After successfully installing the ZENworks Server components, take a
reliable backup of the following files:
/etc/opt/novell/zenworks/hibernate.cfg.xml
/etc/opt/novell/zenworks/tomcat/base/
server.xml
/etc/opt/novell/zenworks/serversecret
2 Replace /etc/opt/novell/zenworks/serversecret with the
serversecret file that you have backed up in Step 1.
3 In /etc/opt/novell/zenworks/tomcat/base/
server.xml, change the value of keystorePass and
connectionPassword to the values configured in backed up
serversecret file.
4 In /etc/opt/novell/zenworks/hibernate.cfg.xml,
change the value of <property
name="connection.password"> to the values configured in
backed up serversecret file.
Executing the rug ref command on the PPC, IPF, and zSeries devices results in
exceptions related to Inventory
Source: ZENworks Linux Management; ZENworks Agent
Possible Cause: On the PPC, IPF, and zSeries devices, the rug set hardware-
inventory-enabled preference is set to True.
12 Novell ZENworks 7.2 Linux Management Troubleshooting Guide
Action: Do one of the following:
Ignore the exceptions because Inventory is not supported for the PPC,
IPF, and zSeries devices.
To avoid the exceptions, set the rug set hardware-inventory-
enabled preference is set to False.
1.2 Troubleshooting the Upgrade Scripts
“Execution of the Upgrade Script Fails on Managed Devices Other Than SLES 10 and SLED
10” on page 13
“Execution of the Upgrade Script Fails on the SLES 10 or SLED 10 Managed Devices” on
page 13
Execution of the Upgrade Script Fails on Managed Devices Other Than SLES 10 and
SLED 10
Source: ZENworks Linux Management. Upgrade.
novdocx (en) 11 July 2008
Possible Cause: The Remote Execute policy is not implemented on the device. To verify that
the policy has not been implemented, check that the /var/opt/novell/
zenworks/cache/zmd/policymanager/policies.xml file does
not have reference to the Remote Execute policy.
Action: Do the following on the managed device:
1 Ensure that the zmd version is 7.1.100 by executing rpm -qi
novell-zenworks-zmd.
2 Restart the zmd service by executing /etc/init.d/novell-zmd
restart.
Execution of the Upgrade Script Fails on the SLES 10 or SLED 10 Managed Devices
Source: ZENworks Linux Management, Upgrade.
Action: Do the following on the managed device:
1 Ensure that the zmd version is 7.1.100 by executing rpm -zmd.
2 Restart the zmd service by executing /etc/init.d/novell-zmd
restart.
Installation and Upgrade Troubleshooting Strategies 13
novdocx (en) 11 July 2008
14 Novell ZENworks 7.2 Linux Management Troubleshooting Guide
II
Policy Handlers
If the Policy Handlers component of Novell® ZENworks® Linux Management displays an error
message, you can look it up in the Error Messages section. If a problem is not accompanied by an
error message, or if specific instructions for an error message are not available, you can try more
general troubleshooting strategies to resolve the problem.
This section contains the following topics:
Chapter 2, “Policy Handlers Error Messages,” on page 17
Chapter 3, “Policy Handlers Troubleshooting Strategies,” on page 25
novdocx (en) 11 July 2008
II
Policy Handlers
15
novdocx (en) 11 July 2008
16 Novell ZENworks 7.2 Linux Management Troubleshooting Guide
2
Policy Handlers Error Messages
This section contains detailed explanations of the error messages you might encounter using the
®
Novell
ZENworks® Linux Management Policy Handler component:
“General Error Messages” on page 17
“Remote Execute Policy Error Messages” on page 23
2.1 General Error Messages
“The policy_name could not be enforced because it contains invalid keys” on page 18
“The policy_name could not be enforced because few keys defined in the policy could not be
cleared appropriately before enforcement” on page 18
“The policy_name could not be enforced because the format of the policy data was invalid” on
page 18
“The policy_name could not be enforced because the user specified was invalid” on page 18
novdocx (en) 11 July 2008
2
“The policy_name could not be enforced because the username has not been specified in the
policy” on page 19
“The GConfEnforcer could not find any settings to read from the device” on page 19
“The GConfEnforcer could not read the requested settings from the device for the specified
user” on page 19
“The settings made by the policy_name enforcers could not be cleared completely. Settings
made by policies of this type might still be in effect on the device” on page 19
“The policy_name could not be enforced because there was an error in setting or unsetting the
values into the configuration source” on page 20
“The read settings operation could not be performed by the enforcer GConf Enforcer because
there was an error in reading from the configuration source” on page 20
“The enforcement of policy_name was unsuccessful and the application is not installed/
compatible. The version of name of the application should be >= minimum required version”
on page 20
“The enforcement of name of the policy was unsuccessful and the operating system distribution
is not compatible. The distribution should be >= distribution required version. Only some keys
might be enforced” on page 21
“The policy_name will not be enforced because the name of the application is not installed” on
page 21
“The policy_name will not be enforced because the operating system is not required
distribution version or higher” on page 21
“The policy_name was requested to be enforced, however, it is already executing, therefore, we
will not start it again.” on page 21
“Rescheduling the enforcement of name of the policy for 2 minutes later, because its type is not
re-entrant and another policy of this type is already executing.” on page 22
Policy Handlers Error Messages
17
The policy_name could not be enforced because it contains invalid keys
Source: ZENworks Linux Management; Policy Handlers
Severity: Critical
Possible Cause: Some other application might have locked the settings that are defined in the
policy they cannot be written to GConf.
Action: Ask the user to login again to the managed device.
The policy_name could not be enforced because few keys defined in the policy
could not be cleared appropriately before enforcement
Source: ZENworks Linux Management; Policy Handlers
Severity: Critical
Possible Cause: Some other application might have locked the settings that are defined in the
policy. They could not be removed from GConf.
Action: Ask the user to log in again to the managed device.
novdocx (en) 11 July 2008
The policy_name could not be enforced because the format of the policy data was
invalid
Source: ZENworks Linux Management; Policy Handlers
Severity: Critical
Possible Cause: The policy details were corrupted while retrieving or applying it.
Action: Perform the following:
1 To refresh the policy details, run the following command from the
command line:
/opt/novell/zenworks/bin/rug refresh
2 If the policy is not enforced, stop zmd by running the following command
from the command line:
/etc/init.d/novell-zmd stop
3 Remove the policy cache files from /var/opt/novell/zenworks/
cache/zmd/PolicyManager/policies.xml.
4 Start zmd by running the following command from the command line:
/etc/init.d/novell-zmd start
5 Ask the user to log in again to the managed device.
The policy_name could not be enforced because the user specified was invalid
Source: ZENworks Linux Management; Policy Handlers
Severity: Critical
Possible Cause: The user's login entry for device does not exist in the /etc/passwd file.
Action: Make sure that the user's entry exists in the /etc/passwd file.
18 Novell ZENworks 7.2 Linux Management Troubleshooting Guide
Possible Cause: An internal error occurred while applying the policy.
Action: Perform the following:
1 Restart zmd by running the following command from the command line:
/etc/init.d/novell-zmd restart
2 Ask the user to log in again to the managed device.
The policy_name could not be enforced because the username has not been
specified in the policy
Source: ZENworks Linux Management; Policy Handlers
Severity: Critical
Possible Cause: An internal error occurred while applying the policy.
Action: Perform the following:
1 Restart zmd by running the following command from the command line:
novdocx (en) 11 July 2008
/etc/init.d/novell-zmd restart
2 Ask the user to login again to the managed device.
The GConfEnforcer could not find any settings to read from the device
Source: ZENworks Linux Management; Policy Handlers
Severity: Critical
Possible Cause: The default schema files of GConf are corrupted or not valid.
Action: Ensure that the default schema files of GConf are valid.
Possible Cause: You might not have configured any specific GConf values for the user.
Action: Configure some values for the user.
For more information about configuring GConf values, refer “Understanding
Policies” in the Novell ZENworks 7.2 Linux Management Administration
Guide.
The GConfEnforcer could not read the requested settings from the device for the
specified user
Source: ZENworks Linux Management; Policy Handlers
Severity: Critical
Possible Cause: The user's entry does not exist in the /etc/passwd file.
Action: Make sure that the user's entry exists in the /etc/passwd file.
The settings made by the policy_name enforcers could not be cleared completely.
Settings made by policies of this type might still be in effect on the device
Source: ZENworks Linux Management; Policy Handlers
Severity: Critical
Policy Handlers Error Messages 19
Possible Cause: Some other application might have locked the settings that are defined in the
policy, so cannot be removed from GConf.
Action: Perform the following:
1 Ask the user to log in again to the managed device.
2 Clear the policy enforcement again on the managed device.
The policy_name could not be enforced because there was an error in setting or
unsetting the values into the configuration source
Source: ZENworks Linux Management; Policy Handlers
Severity: Critical
Possible Cause: The home directory of a user who has logged in to the managed device does
not exist in the /etc/passwd file.
Action: Ensure that a valid home directory is specified for a user on the managed
device in the /etc/passwd.
Possible Cause: Root has insufficient rights to access the home directory of a user on the
managed device.
novdocx (en) 11 July 2008
Action: Ensure that root has sufficient rights to access the home directory.
Possible Cause: Some other application might have locked the settings that are defined in the
policy, so they cannot be written to GConf.
Action: Ask the user to log in again to the managed device.
The read settings operation could not be performed by the enforcer GConf Enforcer
because there was an error in reading from the configuration source
Source: ZENworks Linux Management; Policy Handlers
Severity: Critical
Possible Cause: The home directory of a user whose settings are being retrieved from the
managed device does not exist in the /etc/passwd file.
Action: Ensure that a valid home directory is specified for a user on the managed
device in /etc/passwd file.
Possible Cause: The user does not have sufficient rights to access the directory from the
ZENworks Management Daemon.
Action: Ensure that the user has sufficient rights to access the ZENworks Management
Daemon.
Possible Cause: Some other application might have locked the settings that are defined in the
policy, so they cannot be written to GConf.
Action: Retry importing the settings.
The enforcement of policy_name was unsuccessful and the application is not
installed/compatible. The version of name of the application should be >= minimum
required version
Source: ZENworks Linux Management; Policy Handlers
20 Novell ZENworks 7.2 Linux Management Troubleshooting Guide
Severity: Critical
Possible Cause: The application (Firefox*, Epiphany*, or EvolutionTM) is not installed or the
specified version is earlier than the minimum supported version.
Action: Upgrade the application to the minimum required version and try enforcing the
policy again.
The enforcement of name of the policy was unsuccessful and the operating system
distribution is not compatible. The distribution should be >= distribution required
version. Only some keys might be enforced
Source: ZENworks Linux Management; Policy Handlers
Severity: Critical
Possible Cause: The distribution or version of the operating system is not compatible with the
policy you are trying to enforce.
Action: Associate the policy to a device with the required distribution and version of
the operating system.
novdocx (en) 11 July 2008
The policy_name will not be enforced because the name of the application is not
installed
Source: ZENworks Linux Management; Policy Handlers
Severity: Critical
Possible Cause: The policy might be associated to a device that does not have the application
installed.
Action: Install the required application.
The policy_name will not be enforced because the operating system is not required
distribution version or higher
Source: ZENworks Linux Management; Policy Handlers
Severity: Critical
Possible Cause: The Novell Linux Desktop policy or the SUSE Linux Enterprise Desktop
policy is associated to a device that does not have Novell Linux Desktop or
SUSE Linux Enterprise Desktop operating system respectively.
Action: Associate the Novell Linux Desktop policy only to devices having Novell
Linux Desktop operating system installed, and the SUSE Linux Enterprise
Desktop policy only to the devices having the SUS Linux Enterprise Desktop
operating system installed.
The policy_name was requested to be enforced, however, it is already executing,
therefore, we will not start it again.
Source: ZENworks Linux Management; Policy Handlers
Severity: Important
Policy Handlers Error Messages 21
Explanation: If two or more users are logging into the device at the same time, the policy
enforcement might not have finished for the first user before it started for the
other user. The specified policy is not enforced for users other than the first
user.
Possible Cause: Two or more users have logged in to the device at the same time.
Action: The users after the first user should login again for the policies to take effect.
Possible Cause: One of the policies is taking a long time.
Action: For Text File and Remote Execute policies, review any scripts/programs
specified in the policy to see if they could take excessive time. Correct those
situations to reduce the amount of time and try enforcing the policy again. For
GConf-based policies, do not include any settings in the policy that are not
relevant to you. If the policy data is correct, then restart ZMD and enforce the
policy again.
Possible Cause: The time interval for enforcing the policy is too small compared to the amount
of time it takes to enforce the policy.
Action: Increase the time interval.
novdocx (en) 11 July 2008
1 In the ZENworks Control Center, click Policies.
2 Click any Remote Execute or Text File policy for which you want to
increase the time interval.
3 On the Summary page, click Relative to Refresh in Assignments section.
4 In the Edit Schedule dialog box, increase the time interval you have
specified in After Executing, Repeat Every option.
Rescheduling the enforcement of name of the policy for 2 minutes later, because its
type is not re-entrant and another policy of this type is already executing.
Source: ZENworks Linux Management; Policy Handlers
Severity: Important
Possible Cause: A read settings request was made to the managed device while a user was
trying to login.
Action: Ask the user to login again to the managed device.
Possible Cause: There is an internal error.
Action: Restart ZMD and ask the user to login again to the managed device.
The enforcer executable, enforcer_name, could not be located
Source: ZENworks Linux Management; Policy Handlers
Explanation: The Policy Manger logs the error message in the ZENworks Control Center
when you log into a managed device that does not have the GConf binaries
installed.
Possible Cause: The ZENworks Agent is installed with the -x option on the managed device
that does not have GConf binaries installed.
Possible Cause: The ZENworks Agent installation is corrupted.
22 Novell ZENworks 7.2 Linux Management Troubleshooting Guide
Action: If the error message is displayed when a GConf based policy is assigned, do
one of the following:
To apply the GConf based policy, reinstall the ZENworks Agent without -
x option.
Remove the assignment between the policy and the device that does not
have the Gconf binaries installed.
Action: If the error message is displayed when a GConf based policy is not assigned,
ignore the message and acknowledge it in ZENworks Control Center.
2.2 Remote Execute Policy Error Messages
“The policy_name was enforced and the program launched did not complete the execution” on
page 23
The policy_name was enforced and the program launched did not complete the
execution
Explanation: This message indicates that the launched script or binary or Java* program
didn’t complete the execution when the enforcer returned, so the exit code
returned by the launched program could not be reported in the message. This
message does not mean that the launched program was terminated abnormally.
novdocx (en) 11 July 2008
Possible Cause: While creating the policy, the Maximum Time to Wait setting was specified as
Do Not Wait or Wait For number of seconds Secs.
Action: In the Maximum Time to Wait setting, select Wait Till the Program Completes
the Execution.
Policy Handlers Error Messages 23
novdocx (en) 11 July 2008
24 Novell ZENworks 7.2 Linux Management Troubleshooting Guide
3
Policy Handlers Troubleshooting
novdocx (en) 11 July 2008
Strategies
This section provides solutions to problems you might encounter when using Novell® ZENworks®
Linux Management Policy Handler component.
Section 3.1, “General Troubleshooting Strategies,” on page 25
Section 3.2, “Troubleshooting the Epiphany Policy,” on page 28
Section 3.3, “Troubleshooting the Generic GNOME Policy,” on page 28
Section 3.4, “Troubleshooting the Remote Execute Policy,” on page 29
Section 3.5, “Troubleshooting the Text File Policy,” on page 30
3.1 General Troubleshooting Strategies
“The new policy is not enforced on the device after multiple refreshes” on page 25
“The updated policy is not being enforced on the device after multiple refreshes” on page 27
“A new policy is not enforced following an immediate manual refresh after policy assignment”
on page 27
“The assigned policies are enforced but applications do not reflect the specified behavior” on
page 27
“The policy is not displayed in the Effective Policies list” on page 28
3
The new policy is not enforced on the device after multiple refreshes
Source: ZENworks Linux Management; Policy Handlers
Possible Cause: The policy does not display in the effective policies list of the device.
Action: In the policy Summary page, assign the policy to the device by using
Assignment section.
Possible Cause: The minimum system requirements for the policy to be enforced on the device
are not met.
Action: Ensure that the minimum system requirement for the policy to be enforced on
the managed device are met.
Possible Cause: The policy enforcement schedule is not set.
Action: For the Text File and Remote Execute policies, verify that the schedule to
enforce a policy has been set.
Action: For GNOME-based policies, verify that the User Login event has occurred by
viewing the /var/opt/novell/log/zenworks/zmd-
messages.log file.
Possible Cause: For policies other than Remote Execute and Text File, there might be more
than one policy of the same type associated with the device.
Action: Define all your settings only in one policy and associate it to the device.
Policy Handlers Troubleshooting Strategies
25
Possible Cause: The policy was not refreshed on the device.
Action: Perform the following:
1 If you have recently assigned the policy to the managed device, wait for a
few minutes to see if the policy is simply slow in being enforced.
2 If it is not enforced within a few minutes, on the ZENworks Control
Center, go to the Devices page and select the device where you have
assigned a policy.
3 In the Action menu, select Refresh Device.
4 On the managed device, open the file /var/opt/novell/
zenworks/cache/zmd/PolicyManager/Policies.xml.
5 Search for the policy you have defined by using its name as the search
string.
6 Refresh the device multiple times.
Possible Cause: You have not logged in through the user interface login on the device.
Explanation: If the policy is set to run on User Login, a user for whom the policy has not
applied should log in by using the user interface on the device.
novdocx (en) 11 July 2008
Action: Make sure that you log in through the user interface and verify the policy
status again.
Possible Cause: The window manager is not GDM and KDM.
Action: By default, GConf-based policies support GDM, KDM, or XDM display
managers. If you want your existing Display Manager to change to GDM,
KDM, or XDM:
If you are using the Novell Linux Desktop or SUSE
change to GDM, KDM, or XDM:
1 Edit the /etc/sysconfig/displaymanager file as follows:
DISPLAYMANAGER=<<GDM, KDM, or XDM>>
For more details, refer to the GNOME Documentation (http://
www.gnome.org/projects/gdm/docs.html)
2 Edit the /usr/X11R6/bin/gnome file and add the following to the
beginning of the file:
/opt/novell/zenworks/bin/checkEnforcement
If you are using Red Hat* and you want to change to GDM, KDM, or XDM:
1 Edit the /etc/sysconfig/desktop file as follows:
DISPLAYMANAGER=<<GDM, KDM, or XDM>>
®
Linux and you want to
2 Edit the /etc/X11/xdm/Xsession file and add the following to the
beginning of the file:
/opt/novell/zenworks/bin/checkEnforcement
26 Novell ZENworks 7.2 Linux Management Troubleshooting Guide
Loading...