10.0 Troubleshooting ZENworks Server

Unable to regenerate joinproxy_config.properties and joinproxy_hostnamemap.xml regeneration on Primary Servers

Explanation: When you run the microfocus-zenworks-configure -c CreateJoinProxySettingsConfigureAction -Z command to create proxy setting files, joinproxy_config.properties and joinproxy_hostnamemap.xml are generated with 0 byte.
Action: Perform the following steps to regenerate the files on Primary Server:

  1. Run the microfocus-zenworks-configure -c CreateJoinProxySettingsConfigureAction command.

  2. Run zac ref bypasscache.

  3. Restart the service by running the systemctl restart microfocus-zenjoinproxy.service command.

ZENRequest Valve Flooded with 503, 403, and 500 Statuses

Source: The source of the message.
Explanation: While downloading content using Ondemand Content Master, the ZENRequest Valve in the content server is flooded with 503, 403, and 500 statuses.
Possible Cause: This might be due to broken URLs. By default, all the broken URLs are falling back to default or public link, which might not be accessible at the time.
Action: None

Unable to start ZENworks ZooKeeper Service on Primary Servers

Source: ZENworks; ZENworks Server
Explanation: Unable to start the Zookeeper service as the log files are corrupted.
Possible Cause: The Zookeeper service was stopped after creating a new transaction log file before flushing the log header into the log file.

Hence, the transaction log is left without a valid header and fails to start the Zookeeper server.

Action: If the stack traces are pointing to EOFException in zookeeper-messages.log as shown below, then perform the workaround steps (On Windows and On Linux): 
DEBUG persistence.FileTxnLog: EOF exception java.io.EOFException: Failed to read /data/version-2/log.100f5387f
DEBUG persistence.FileTxnLog: Created new input stream /data/version-2/log.100f538e7
 ERROR server.ZooKeeperServerMain: Unexpected exception, exiting abnormally java.io.EOFException

at org.apache.zookeeper.server.ZooKeeperServerMain.main(ZooKeeperServerMain.java:64)
at org.apache.zookeeper.server.quorum.QuorumPeerMain.initializeAndRun(QuorumPeerMain.java:128)
at org.apache.zookeeper.server.quorum.QuorumPeerMain.main(QuorumPeerMain.java:82)
DEBUG server.NIOServerCnxn: Closed socket connection for client /xxx.xx.xxx.xx:48666 (no session established for client)

The paths are as follows:

  • Linux/Xplat: /var/opt/microfocus/zenworks/common

Workaround On Windows: Perform the following steps:

  1. Go to Services (services.msc), search Microfocus ZENworks Zookeeper, and Stop the service.

  2. If the stack traces are pointing to EOFException in zookeeper-messages.log, DELETE the <PATH>/zookeeper/version-2/log.*.

  3. After deleting, Start the Microfocus ZENworks Zookeeper service.

  4. Check the status and verify if the service is Running.

Workaround On Linux: Perform the following steps:

  1. To stop the service, run the following commands in the console:

    systemctl stop microfocus-zenzookeeper.service

  2. If the stack traces are pointing to EOFException in zookeeper-messages.log, DELETE the <PATH>/zookeeper/version-2/log.*.

  3. After deleting, Start the Microfocus ZENworks Zookeeper service by running the following command:

    systemctl start microfocus-zenzookeeper.service

  4. Check the status and verify if the service is running by using the following command:

    systemctl status microfocus-zenzookeeper.service

Server installation will fail on a Windows server if the free space is less than 35 GB

Source: ZENworks, ZENworks Server
Explanation: Server installation fails on a Windows server, if you select a drive which has free space less than 20 GB.
Action: Re-initiate the installation process and select another drive that has at least 20 GB of free space.

The ZENworks Application Window (ZAPP) might not work when you upgrade a server from Windows 2008 to 2012 and then you upgrade to ZENworks 2017

Source: ZENworks, ZENworks Server
Explanation: The ZENworks Application Window (ZAPP) might not work, when you upgrade the Primary Server from ZENworks 11.4.x to ZENworks 2017 after upgrading the operating system from Windows Server 2008 to Windows Server 2012.
Action: After upgrading the operating system, manually install the latest .NET Framework (4.5.x), and then upgrade the Primary Server.

When a second Primary Server is added to the zone, an out of memory error message might be displayed

Source: ZENworks; ZENworks Server
Explanation: When a second Primary Server is added to the zone, though the installation is successful, you might receive an error message indicating that the installation failed due to insufficient memory.
Action: None, Ignore the message.