1.1 Troubleshooting the Installation

Install randomly fails when zlm-config fails to complete

Source: ZENworks7.3 Linux Management, Installation of the ZENworks Agent.
Action: Re-run zlm-config.

Zmd hangs randomly on the managed device

Source: ZENworks 7.3 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 7.3 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:

     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 7.3 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.3 Linux Management Installation Guide.

How do I recover the password for the ZENworks Server?

Source: ZENworks 7.3 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 7.3 Linux Management; ZENworks Agent
Possible Cause: On the PPC, IPF, and zSeries devices, the rug set hardware-inventory-enabled preference is set to True.
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.

ZENworks Linux Management installation hangs in an X session on a 32-bit SUSE Linux Enterprise 11

Source: ZENworks 7.3 Linux Management, Installation
Action 1: Download and install the gpg2 2.0.9-25.25.1or later package and the gpg2-lang 2.0.9-25.25.1or later package from Novell Update, then run the ZENworks 7.3 Linux Management installation.
Action 2: Install the ZENworks 7.3 Linux Management in one of the following ways:

  • Log in to the device in the init 3 mode by using the following command, then run the ZENworks Linux Management installation:

    /sbin/init 3

  • Remotely log in to the device by using either RSH or SSH and run the ZENworks Linux Management installation.

NOTE:This might close any applications that are open.

Unable to upgrade the default ZENworks Linux Management agent installed on SUSE Linux Enterprise Server 10 devices by using the upgrade bundles

Source: ZENworks 7.3 Linux Management; Installation
Explanation: The upgrade bundles do not contain the python-xml package to successfully upgrade the default ZENworks Linux Management agent.
Action: Manually add the python-xml package from the SUSE Linux Enterprise Server (SLES) 10 media to the upgrade bundle.

Upgrading from ZENworks 7.2 Linux Management with IR2 or later to ZENworks 7.3 Linux Management might fail on a SUSE Linux Enterprise Server 10 GM device

Source: ZENworks 7.3 Linux Management; Installation
Possible Cause: The Python version in the default ZENworks Linux Management installation is earlier than Python 2.4.2-18.7.
Action 1: Do the following:

  1. Upgrade the appropriate Python package to version 2.4.2-18.7 by using the ZENworks 7.2 Linux Management with IR2 media or the SLES 10 SP1 media.

  2. Install the nici package from the ZENworks 7.2 Linux Management with IR2 media.

  3. Run the zlm-upgrade script again by using the ZENworks 7.3 Linux Management media.

Action 2: Before upgrading to ZENworks 7.3 Linux Management on a SLES 10 GM device, ensure that the Python package version that is installed is 2.4.2-18.7. If the Python package version is earlier, upgrade it to version 2.4.2-18.7 by using the ZENworks 7.2 Linux Management with IR2 media or the SLES 10 SP1 media.

During ZENworks Linux Management installation, the ndsd runlevel scripts from the eDirectory packages display warning messages

Source: ZENworks 7.3 Linux Management; Installation
Explanation: The zmd-messages.log file displays the warning messages if you are installing ZENworks Linux Management in debug mode (--zlm-debug), and the log-level setting for zmd is set to debug.

For example:

insserv: warning: script 'post_ndsd_stop' missing LSB tags and overrides
insserv: Default-Start undefined, assuming default start runlevel(s) for script `post_ndsd_stop
Action: Ignore the warning messages, and continue with the ZENworks Linux Management installation.

Unable to install the ZENworks 7.3 Linux Management with IR3 agent on ia64 and s390x devices that have a default installation of SLES 11 SP1

Source: ZENworks 7.3 Linux Management; Installation
Possible Cause: You cannot install the ZENworks 7.3 Linux Management with IR3 agent on ia64 and s390x devices that have a default installation of SLES 11 SP1 because the novell-zenworks-gtk-sharp2 package requires the libglade2 package, which is not a part of the default installation of SLES 11 SP1.
Action: Do the following on the ia64 and s390x devices on which you want to install the ZENworks 7.3 Linux Management with IR3 agent:

  1. Install the libglade2 package from the SLES 11 SP1 installation media.

  2. Install the ZENworks 7.3 Linux Management with IR3 agent by running the zlm-install command.

The ZENworks Linux Management agent restores the old values of the deviceid and secret files on SLES 11 and SLED 11 managed devices even after deleting them

Source: ZENworks 7.3 Linux Management; Installation.
Explanation: If the SLES 11 or SLED 11 managed devices are registered to Novell Customer Center through YaST, the ZENworks Linux Management agent restores the old values of the deviceid and secret even after you delete them and restart the agent.
Action: See TID 7006537 on the Novell Support Web site.

Unable to install SLES 9 patch bundles on a ZENworks Linux Management agent

Source: ZENworks 7.3 Linux Management; Installation.
Possible Cause: You might not be able to install patch bundles if the local YOU cache has obsolete SLES 9 patches.
Action: Do the following:

  1. On the server, remirror the SLES 9 patches to the same folder that contains the old SLES 9 patches by using the zlmmirror m -o -c conf.xml command.

  2. On the managed device, clear the YOU cached content present under /var/lib/YaST2/you/mnt directory by using rug command rug you-clean-cache.

  3. Assign the bundle that you mirrored in Step 1 to the agent.

    The SLES 9 patch bundles are installed on the agent.

ZENworks Control Center fails to load after successfully installing or upgrading the ZENworks 7.3 Linux Management Server or later on a 64-bit device

Source: ZENworks 7.3 Linux Management; Installation.
Explanation: The ZENworks Control Center Management Console does not load on the Web browser after you install the Primary Server or upgrade from the previous version. The Tomcat /var/opt/novell/log/zenworks/tomcat/Catalina.start log file displays the following exception: 
LifecycleException:  Exception opening directory server connection:  javax.naming.CommunicationException: localhost:389 [Root exception is java.net.ConnectException: Connection refused

The following error message is displayed when you execute any of the Novell eDirectory commands on a 64-bit ZENworks Linux Management Server.

Error when loading shared libraries
Possible Cause: On a 64-bit device, eDirectory 8.8.3 does not configure the 64-bit equivalent path to search for its shared libraries at run time. This shared path is configured incorrectly in the /etc/ld.so.conf.d/novell-NDSbase.conf file.
Action 1: Add a path for 64-bit libraries:

  1. Edit the /etc/ld.so.conf.d/novell-NDSbase.conf file as follows:

    • Replace /opt/novell/eDirectory/lib with /opt/novell/eDirectory/lib64.

    • Replace /opt/novell/eDirectory/lib/nds-modules with /opt/novell/eDirectory/lib64/nds-modules.

    • Append the /opt/novell/lib with the /opt/novell/lib64 path to the file.

  2. Run the ldconfig command.

  3. Restart the eDirectory services by using the /etc/init.d/ndsd restart command.

Action 2: Before executing the eDirectory commands, execute the following command at the command prompt:

. /opt/novell/eDirectory/bin/ndspath

Unable to log in to ZENworks Control Center of the ZENworks Linux Management Server with the Primary or Secondary configuration because of no time synchronization

Source: ZENworks 7.3 Linux Management; Installation.
Explanation: You cannot log in to ZENworks Control Center because of no time synchronization between ZENworks Linux Management Servers (Primary or Secondary) with their eDirectory instances. Sometimes the objects in the eDirectory instances on the Primary or Secondary Server in the zone do not synchronize if they cannot communicate.
Action: To synchronize the time between ZENworks Linux Management Servers (Primary or Secondary) with their eDirectory instances:

  1. Ensure that the Primary or Secondary Server device is configured to synchronize the time through the external NTP Server.

    You can also update the Primary or Secondary Server time stamp by running the following command:

    ntpdate - s <NTP-server-host>

  2. Synchronize the time between the eDirectory instances on the ZENworks Linux Management Server by running the following command:

    . /opt/novell/eDirectory/bin/ndspath

    ndsrepair -T

  3. Restart the ZENworks Linux Management services by running the following command:

    zlm-config --restart