Related Manuals for Novell ZENWORKS LINUX MANAGEMENT 7.2 IR2 - TROUBLESHOOTING GUIDE 08-22-2008
Summary of Contents for Novell ZENWORKS LINUX MANAGEMENT 7.2 IR2 - TROUBLESHOOTING GUIDE 08-22-2008
- Page 1 AUTHORIZED DOCUMENTATION Troubleshooting guide Novell ® ZENworks Linux Management ® 7.2 IR2 August 22, 2008 www.novell.com Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
- Page 2 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.
- Page 3 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.
-
Page 5: Table Of Contents
Contents About This Guide Part I Installation, Upgrade, and ZENworks Database 1 Installation and Upgrade Troubleshooting Strategies Troubleshooting the Installation ..........11 Troubleshooting the Upgrade Scripts. - Page 6 Inventory ............84 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 7: About This Guide
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,”... - Page 8 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 9: Part I Installation, Upgrade, And Zenworks Database
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 Installation, Upgrade, and ZENworks Database... - Page 10 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 11: Installation And Upgrade Troubleshooting Strategies
Troubleshooting Strategies The following sections provide solutions to the problems you might encounter when installing or ® ® upgrading to Novell ZENworks Linux Management: Section 1.1, “Troubleshooting the Installation,” on page 11 Section 1.2, “Troubleshooting the Upgrade Scripts,” on page 13 1.1 Troubleshooting the Installation... - Page 12 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. Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 13: Troubleshooting The Upgrade Scripts
Source: ZENworks Linux Management. Upgrade. 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. - Page 14 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 15: Part Ii Policy Handlers
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. - Page 16 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 17: Policy Handlers Error Messages
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... -
Page 18: The Policy_Name Could Not Be Enforced Because It Contains Invalid Keys
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... -
Page 19: The Policy_Name Could Not Be Enforced Because The Username Has Not Been Specified In The Policy
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;... -
Page 20: The Policy_Name Could Not Be Enforced Because There Was An Error In Setting Or Unsetting The Values Into The Configuration Source
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 Novell ZENworks 7.2 Linux Management Troubleshooting Guide... -
Page 21: 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
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... - Page 22 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. Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 23: Remote Execute Policy Error Messages
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. - Page 24 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 25: Policy Handlers Troubleshooting Strategies
Policy Handlers Troubleshooting 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,”... - Page 26 If you want your existing Display Manager to change to GDM, KDM, or XDM: ® If you are using the Novell Linux Desktop or SUSE Linux and you want to change to GDM, KDM, or XDM: 1 Edit the /etc/sysconfig/displaymanager file as follows: DISPLAYMANAGER=<<GDM, KDM, or XDM>>...
- Page 27 3 On the Summary page, increment the revision number and refresh the device. To check the version of the policy available in the Cache: 1 Open the /var/opt/novell/zenworks/cache/zmd/ PolicyManager/Policies.xml file. 2 Search for the policy name. The version should be listed in between <Version>...
-
Page 28: Troubleshooting The Epiphany Policy
Explanation: The Generic GNOME policy defines setting for many applications. Not all the applications reflect the settings that are defined in the policy. Possible Cause: The applications that do not reflect the policy settings might not be working properly with GConf. Novell ZENworks 7.2 Linux Management Troubleshooting Guide... -
Page 29: Troubleshooting The Remote Execute Policy
Source: ZENworks Linux Management; Policy Handlers; Generic GNOME Policy Explanation: GNOME-based policies such as Epiphany*, Evolution*, Firefox*, Generic GNOME*, Novell Linux Desktop, and SUSE® Linux Enterprise Desktop might not be enforced. Action: Log in as an administrator and remove all the hidden files (file names starts with '.') with .status.completed extension from the HOME directory of the user,... -
Page 30: Troubleshooting The Text File Policy
“How to ensure that the post-change action has been successful when the Text File policy was enforced” on page 32 The Text File policy is not enforced Source: ZENworks Linux Management; Policy Handlers; Text File Policy Possible Cause: Policy Enforcement might have failed. Novell ZENworks 7.2 Linux Management Troubleshooting Guide... - Page 31 Action: Ensure that the policy has been enforced correctly by checking the Event Log of the policy or of the managed device. Possible Cause: The search string was not found in the file. Action: Verify that the Additional Info field in a log message contains a list of changes that were not performed.
- Page 32 Action: Verify the value of the post-change action exit code in the message that was logged after policy was enforced. This value is the exit code, which was returned by the program or script launched in the post-change action. Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 33: Part Iii Event Monitoring
Event Monitoring I I I ® ® If the Event Monitoring component of Novell ZENworks Linux Management displays an error message or if specific instructions for an error message are not available, you can try the more general troubleshooting strategies to resolve the problem. - Page 34 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 35: Event Monitoring Troubleshooting Strategies
Event Monitoring Troubleshooting Strategies ® ® This section provides solutions to problems you might encounter when using Novell ZENworks Linux Management Event Monitoring component. 4.1 Troubleshooting Event Monitoring “Changing the severity level for a local log from the Centralized Message Logging setting in Novell Control Center is not taking effect”... - Page 36 I am receiving unknown traps on the trap console Severity: ZENworks Linux Management; Event Monitoring Possible Cause: The messagelogger.mib file is not compiled on the server. Action: Compile the messagelogger.mib file located at /opt/novell/ zenworks/share/messagelogger. For example, if you want to compile messagelogger.mib on the Management...
-
Page 37: Part Iv Inventory
Inventory ® ® If the Inventory 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. - Page 38 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 39: Inventory Roll-Up Error Messages
Inventory Roll-Up Error Messages This section contains detailed explanations of the error messages you might encounter using the ® ® Inventory Roll-Up component of Novell ZENworks Linux Management. “Incorrect input for the time interval between roll-ups” on page 39 “DNS name not found. Will exit now.” on page 39 “The IP address of destination Inventory server has not been configured in the Inventory Roll-... - Page 40 Action: Ensure that the network connection between the ZENworks Linux Management server and the ZENworks Desktop Management or ZENworks Server Management server is working. Unable to initiate the file transfer Source: ZENworks 7.2 Linux Management; Inventory Roll-Up Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
- Page 41 Action: On the destination Inventory server, start the Receiver from the Service Manager. Action: If the Sender fails to connect to the Receiver even after the retries, contact Novell Support (http://support.novell.com). Action: Ensure that the network connection between the ZENworks Linux Management server and the ZENworks Desktop Management or ZENworks Server Management server is working.
- Page 42 Source: ZENworks 7.2 Linux Management; Inventory Roll-Up Severity: Critical Action: Contact Novell Support (http://support.novell.com). An exception occurred while writing to an STR file Source: ZENworks 7.2 Linux Management; Inventory Roll-Up Severity: Critical Action: Contact Novell Support (http://support.novell.com). Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 43: Inventory Troubleshooting Strategies
Strategies This section provides solutions to problems you might encounter when using the Inventory Roll-Up ® ® component of Novell ZENworks 7 Linux Management. Section 6.1, “Troubleshooting Inventory Roll-Up,” on page 43 Section 6.2, “Troubleshooting Hardware Inventory,” on page 44 6.1 Troubleshooting Inventory Roll-Up... -
Page 44: Troubleshooting Hardware Inventory
Ensure that the Inventory module is loaded by executing the rug ping command. If the module is loaded, the zmd-messages.log file contains the following message: INFO ModuleLoader Loaded 'Inventory' - 'Software and Hardware inventory module for Linux' Novell ZENworks 7.2 Linux Management Troubleshooting Guide... -
Page 45: How Do I Control The Interval Of Hardware Inventory Update To The Server
2. Stop and start the ZENworks agent service, /etc/init.d/ novell-zmd, and verify that the new schedule is now added. Ensure that the hardware inventory is collected and sent successfully from the managed device. -
Page 46: How Do I Control The Probing Of Hardware Information Of Specific Component On Managed Device
All delayed schedules for inventory are added during the device registration and subsequently, when refresh schedules are triggered. The “Software Inventory delay” schedule is added to update inventory when packages are installed or removed on a client. Novell ZENworks 7.2 Linux Management Troubleshooting Guide... -
Page 47: Part V Disaster Recovery
Disaster Recovery ® ® If the Disaster Recovery 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. - Page 48 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 49: Disaster Recovery
Maintenance” in the Novell ZENworks 7.2 Linux Management Administration Guide. 7.1.2 The Object Store The ZENworks Object Store is Novell eDirectory 8.7.3. For information on backing up and restoring the ZENworks Object Store, see “ZENworks Object Store and Data Store Maintenance” in Novell ZENworks 7.2 Linux Management Administration... -
Page 50: The Zlmmirror Configuration Files
ZENworks Primary Server is lost, the secondary servers continue to have access to the Data Store. 7.2.2 Object Store The ZENworks Object Store is Novell eDirectory 8.7.3. The ZENworks Primary Server holds a master replica of the Object Store and the next two consecutive ZENworks Secondary Servers installed in the Management Zone hold a read/write replica of the Object Store. -
Page 51: Package Repository
Data Store is restored to the environment. Additionally, if the Data Store is down, the conversion does not function properly. For more information on the Message Logger, see “Message Logger” in the Novell ZENworks 7.2 Linux Management Administration Guide. 7.3 Restoring Your System after a Primary Server Failure This section is applicable only if the PostgreSQL or Oracle datastore is hosted remotely. -
Page 52: Converting A Secondary Server To A Primary Server
Linux. 8a Download the Linux version of ConsoleOne from www.novell.com/download. You are prompted to enter your Novell account username and password. If you don't have a Novell account, use the “create new account” link. 8b Save the ConsoleOne compressed file to disk and uncompress it. -
Page 53: Moving Devices To The New Primary Server
After you have set up a new primary server, the devices managed by the old primary server need to be moved to the new primary server. For instructions on how to do that, see “Registering Devices” in the Novell ZENworks 7.2 Linux Management Administration Guide. Disaster Recovery... - Page 54 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 55: Disaster Recovery Error Messages
Possible Cause: The zlm.conf file that is required to obtain the LDAP connection information does not exist in /etc/opt/novell/zenworks. Action: Ensure that the zlm.conf file exists in /etc/opt/novell/zenworks. Possible Cause: The hibernate.cfg.xml file that is required to obtain database connection and configuration information does not exist in /etc/opt/ novell/zenworks. - Page 56 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 57: Part Vi Remote Management
Remote Management ® ® If the Remote Management 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. - Page 58 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 59: Remote Management Error Messages
Action: Configure the firewall on the managed device to allow incoming connections for the required port. For example, to configure the firewall on Novell Linux Desktop: 1 In the System menu, click Administrator Settings to launch YaST. 2 In the YaST Control Center, click Security and Users. - Page 60 2 Change the runlevel of the managed device to 3 by entering the following command at the shell prompt: init 3 3 Change the runlevel back to 5 by entering the following command at the shell prompt: init 5 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
- Page 61 host post is not an RFB Server Source: ZENworks Linux Management; Remote Management Severity: Important Possible Cause: The Remote Control Service has failed to authenticate to the X server. Action: Restart the Display Manager. 1 Switch to any one of the text consoles by pressing Ctrl + Alt + F1 in your graphical session.
- Page 62 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 63: Remote Management Troubleshooting Strategies
Remote Management Troubleshooting Strategies ® This section provides solutions to problems you might encounter when using the Novell ® ZENworks Linux Management Remote Management component: “Multiple Remote Login sessions to the same managed device fail” on page 63 “The Remote Management session does not proceed if the managed device is displaying the GNOME logout dialog box”... -
Page 64: The Remote Management Viewer Window Fails To Refresh After Multiple Remote Management Sessions From The Same Browser Session
“host port is not an RFB Server”. Possible Cause: The Remote Control Service has failed to authenticate to the X Server. Action: Restart the Display Manager. 1 Switch to any one of the text console. Novell ZENworks 7.2 Linux Management Troubleshooting Guide... -
Page 65: Only A Grey Screen Is Displayed While Performing A Remote Login Session
X cursor. Possible Cause: XDMCP was not enabled on the managed device. Action: Manually enable XDMCP by running /opt/novell/zenworks/bin/novell-rm- fixrl.sh with the required options. If you use the -restartdm option, make sure that all applications are closed, then run the script from the text console. - Page 66 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 67: Part Vii Dell Dtk
Dell DTK V I I ® ® If the Dell OpenManage Deployment Toolkit (DTK) component of Novell ZENworks Linux Management displays an error message, or if specific instructions for an error message are not available, you can try the more general troubleshooting strategies to resolve the problem. - Page 68 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 69: Dell Configuration Bundle Troubleshooting Strategies
2 Do one of the following: Assign the bundle to a managed device (see “Creating Dell Configuration Bundles” in the Novell ZENworks 7.2 Linux Management Administration Guide). Create a Preboot Work Assignment rule for an unmanaged device (see “Creating Dell Configuration Bundles”... - Page 70 12 After each trial run, reboot the device or reassign the Preboot work so that your troubleshooting starts at a known state, then repeat these steps to troubleshoot a different Dell Configuration bundle. Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 71: Part Viii Package And Content Management
V I I I Management ® ® If the Package and Content Management features 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. - Page 72 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 73: Package And Content Management Error Messages
Action: Do the following:. 1 Increase the memory-threshold value in the zmd.conf file. The zmd.conf file is located in /etc/zmd/ on SLES 10 and SLED 10 devices, and in /etc/opt/novell/zenworks/zmd/ on other devices. 2 Restart the zmd. Error receiving message: Read failure Source: ZENworks Linux Management;... - Page 74 Possible Cause: There is more than one bundle with the same name in different folders in ZENworks Control Center, and you are trying to install one of them. Action: On the managed device, use the rug bin -g GUID command to install the required bundle. Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 75: Package And Content Management Troubleshooting Strategies
Management Troubleshooting Strategies ® ® This section provides solutions to problems you might encounter when using Novell ZENworks Linux Management Package and Content Management features: “Installing updates that were mirrored from the Update sites, such as http://updates.novell.com (http://updates.novell.com/), using the rug up command fails with dependency errors” on page 75 “Rug refresh hangs”... -
Page 76: Bundle Or Package Installation Might Fail With The Error Message, "Resolvable Id (Number) Does Not Exist
Explanation: The following error message might be displayed when you add a custom repository: ERROR: Could not add 'http://foobar.com/sled-10-i586': Failed to parse XML metadata: Unsigned file '/repodata/repomd.xml (file:/ var/cache/zmd/web/files/foobar.com/sled-10-i586/)' Action: Log in as root, and execute the following command: rug set security- level checksum. Novell ZENworks 7.2 Linux Management Troubleshooting Guide... -
Page 77: Installing The You Patches Without Any Particular Order Using The Rug Command Fails
Action: Increase the JVM heap memory capacity on the local primary server: 1 In the /opt/novell/zenworks/bin/zlmmirror file, change the value of -Xmx to 256 or 512 in the following line depending on the memory capacity of your device and the load on the server: /opt/novell/zenworks/lib/SunJava2-1.4/bin/java... - Page 78 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 79: Part Ix Preboot Services
Preboot Services ® ® If the Preboot Services features 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. - Page 80 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 81: Preboot Services Troubleshooting Strategies
Preboot Services Troubleshooting Strategies ® ® This section provides solutions to problems you might encounter when using Novell ZENworks Linux Management Preboot Services: “The zislnx service fails to shut down on a RHEL 3 device” on page 81 The zislnx service fails to shut down on a RHEL 3 device Source: ZENworks Linux Management;... - Page 82 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
-
Page 83: A Documentation Updates
This section contains information on documentation content changes that were made in this ® ® Troubleshooting Guide after the initial release of Novell ZENworks 7.2 Linux Management. The information can help you to keep current on updates to the documentation. -
Page 84: Package And Content Management
The following changes were made in this section: Location Change Section 6.2, “Troubleshooting Added the following scenario: Hardware Inventory,” on page 44 “How to control delayed schedules for updating inventory on the ZENworks Linux Management server?” on page 46 Novell ZENworks 7.2 Linux Management Troubleshooting Guide...
Need help?
Do you have a question about the ZENWORKS LINUX MANAGEMENT 7.2 IR2 - TROUBLESHOOTING GUIDE 08-22-2008 and is the answer not in the manual?
Questions and answers