3.0 Troubleshooting ZENworks Command Line Utilities

The following sections provide solutions to the problems you might encounter while working with Micro Focus ZENworks command line utilities:

When you run the zman db command, Java heap space error might occur

Source: ZENworks 2017 Update 2
Explanation: When you run the zman db command, OutOfMemoryError: Java heap space error might occur.
Possible Cause: Limited java heap memory configured for the zman process.
Action: Using the new configure action UpdateZManConfigPropertiesConfigureAction you can configure the heap-size. By default, maximum heap-size is set to 512.

To increase the heap size:

In the command prompt, run the following command:

novell-zenworks-configure -c UpdateZManConfigPropertiesConfigureAction -Dzman.jvm.max.heapSize=<user-input>

Where <user-input> can be between max.heapSize: 512 (default) to 1024 (upper-bound)

Apart from max.heapsize, you can configure other parameters such as min.heapSize, scrollSize and debugLevel.

novell-zenworks-configure -c UpdateZManConfigPropertiesConfigureAction -Dzman.jvm.max.heapSize=<user-input> -Dzman.jvm.min.heapSize=<user-input> -Dzman.renderer.scrollSize=<user-input> -Dzman.debugLevel=<user-input>

Where <user-input> for min.heapSize can be between 64(default) to 512(upper-bound)

scrollSize accepts any integer value (-1 default)

debugLevel accepts 1, 2, 3(default) and 4 values

NOTE:If the zman-config.property file is corrupted or deleted, run the novell-zenworks-configure -c UpdateZManConfigPropertiesConfigureAction command without parameters to get the default values in the file.

zman hangs when the output of a command is redirected to a file by using the command line redirection operators such as > or >>

Source: ZENworks; zman.
Possible Cause: zman requires the ZENworks administrator username and password for executing each command. If the credentials are not provided with the command, you are prompted to enter the same. However, if the output of the command is redirected to file, you are not prompted to enter the credentials because the prompts for username and password are also redirected to the file. Consequently, zman hangs, waiting for the credentials to be entered.
Action: Specify the credentials as part of the command by using -U|--User and -P|--Password options.
Action: Store the credentials by using the admin-store-credential command and then execute the command.
Action: Redirect the output to a file by using the -R|--Redirect option instead of a redirection operator such as > or >>.

An incorrect success message is displayed when the "stage group name" optional argument is not passed to the system-update-staging-group-create command

Source: ZENworks; zman.
Explanation: zman displays the following incorrect message if the stage group name optional argument is not passed to the system-update-staging-group-create command: 
Successfully created the object "null"
Action: To view the list of staging groups that would include the newly created staging group, execute the system-update-staging-group-list (susgl) command at the console prompt.

The Imaging role added to a Satellite by using the zman ssaimg command is not immediately applied to the server

Source: ZENworks; zman.
Explanation: If you configure the Imaging role by the using the zman ssaimg command, the role is immediately added to the device. If the role is not immediately added, it is added only during the next device refresh schedule.
Action: If you want to immediately apply the role to the device, you must manually refresh the device in one of the following ways:

  • At the command prompt, run the zman workstation-refresh|wrf command. If the managed device is a server, run the zman server-refresh|srf command.

  • On the managed device, right-click the ZENworks icon, then click Refresh.

The zman commands do not work for non-root users on a ZENworks Linux server

Source: ZENworks; zman.
Explanation: If a non-root user executes the zman commands on a ZENworks Linux server, the following error message is displayed:

You do not have sufficient privileges to run zman commands. As a non-root user in Linux, you should be part of the zmanusers group to run zman commands.

Action: Add the non-root user to the zmanusers group before executing the zman commands.

  1. Log in to the ZENworks server as root.

  2. At the server console prompt:

    • If the user already exists on the Linux device, execute the following command:

      groupmod -A non-rootusername zmanusers

    • If the user does not exist on the Linux device, execute the following command:

      useradd -G zmanusers non-rootusername

  3. Log in to the ZENworks server as a non-root user.

A non-root user is unable to configure a Satellite role by using the zman ssc command

Source: ZENworks; zman.
Explanation: If a non-root user tries to configure a Satellite role by using the zman ssc command on a Linux Primary Server, the following error message is displayed: 
The role you specified (Satellite_role_name) is not a valid satellite server role. Valid roles are:
ZoneConfig.ROLE_COLLECTION
ZoneConfig.ROLE_CONTENT
ZoneConfig.ROLE_AUTHENTICATION
Action: Do the following:

  1. Ensure that the non-root has been added to the zmanusers group.

    1. Log in to the ZENworks server as root.

    2. At the server console prompt:

      • If the user already exists on the Linux device, execute the following command:

        groupmod -A non-rootusername zmanusers

      • If the user does not exist on the Linux device, execute the following command:

        useradd -G zmanusers non-rootusername

  2. Add the non-root user to the ZENworks user group by using the usermod -A non-root_username command. Subsequently, the non-root user can configure Satellite roles.

The zac cuo command does not upload the agent audit files from the Satellite Server to the Primary Server when the collectionStatsDB database is corrupted.

Source: ZENworks; zac.
Explanation: When the agent audit files are uploaded to the Satellite Server, the server maintains references to the audit files in the collectionStatsDB database. If the database is corrupted, all the references are lost and the files get orphaned. Hence, when you run the zac cuo command to upload the agent audit files to the Primary Server, you will receive an error.
Action: To upload the agent audit files to the Primary Server, you should perform the following steps on the Satellite Server:

  1. Stop the agent service.

  2. Delete the /var/opt/novell/zenworks/work/collection/collectionStatsDB folder that has references to the orphaned audit files.

  3. Start the agent service.

  4. Execute the zac cuo command.

Some zman commands fail with an OutOfMemoryError

Source: ZENworks; zman.
Explanation: Some zman commands might fail with an OutOfMemoryError.
Action: Increase the max heap size for zman:

Windows: In the %ZENWORKS_HOME%\conf\zman\properties\zman-config.properties file, increase the max heap size value of the JVM_STARTUP_OPTIONS from 128m to 512m.

Linux: In the /opt/novell/zenworks/bin/zman file, increase the max heap size of MEM_OPTS from 256m to 512m.

The zman command ssd that is used for removing a satellite role fails

Source: ZENworks; zman
Explanation: The zman command ssd fails with the following error:

An internal error occurred. Please check the zman log for more

When you use ssd, the zman command for removing a role from the satellite, this command removes the role but fails to send the refresh satellite quicktask.

Possible Cause: This is because the refresh satellite quicktask is already in process for the satellite or about to be processed.
Action: None

zac commands hang on RHEL Satellite Servers when the content replication schedule is configured for a short duration

Source: ZENworks; zac
Explanation: When you run zac commands on an RHEL Satellite Server, the process hangs indefinitely.
Possible Cause: Content replication schedule is configured for a short duration. For example, 5 minutes.

NOTE:It is recommended to configure the content replication schedule for 12 hours.

Action: Log into ZENworks Control Center and add a zone system variable, enable.cdp.cleanup.thread.wait.time, and set the value to True.

Configure action fails with exception ZEN configure action container is not responding

Source: ZENworks
Explanation: The configure action completes with the following warning:

com.novell.zenworks.configure.NonFatalConfigureException: ZEN configure action container is not responding

Possible Cause: This issue occurred because the ZENConfigure container failed to initialize within the wait time.
Action: Increase the wait time of the ZENConfigure container by using the max-retries-for-configure-server=<number of retries> configuration property in the /etc/opt/microfocus/zenworks/host-configure-action.properties directory. The default value for max-retries-for-configure-server is 60.

NOTE:Create the file with the entry if it does not exist.