Data synchronization between the ZENworks Database and the Antimalware Database is managed by the Kafka service, and can be optimized by tuning Kafka settings and database connections. If you are seeing potential issues with data synchronization post database configuration, information for tuning database synchronization in the ZENworks Best Practices Guide is a good place to get a health check of these settings in your zone. For more information, see Tuning Antimalware Database Synchronization
in the ZENworks Best Practices Guide.
If Antimalware Database tuning appears to be in order, reference the following sections for potential troubleshooting scenarios with the Antimalware Database:
When enabling Kafka for Antimalware, you should get a green status for all the components in the Kafka Cluster panel on the Diagnostics page. If subsequently the Populate Database action fails when configuring the Antimalware Database, check the microfocus-zenworks-configure-service.log. If the log states Successfully started the loader service on that server (<server name>)
, then check the loader message of the server. If the zookeeper timeout exception (shown below) is logged, then the issue might be because of the zookeeper exception.
ZookeeperClientException: Timed out waiting to connect to ZooKeeper!
To try fixing this issue, do one of the following:
Single Primary Server zone: Click the Status link for Configure Database, and rerun the Populate Database action.
Multi-Primary Server zone: Run the PopulateAMDatabaseConfigureAction command again on one of the primary servers. For more information, see Populate the Antimalware Database.
If the issue persists, please contact Micro Focus Customer Support.
Configuration replication across all primary servers in the zone is a key task that ZENworks runs when configuring the Antimalware Database. If the configuration replication task fails on any of these servers, the Configure Database (Status:) might read “Completed with Issues”, and the Populate Database option will not be enabled.
Servers that failed to replicate should be listed in the Database Configuration Status dialog box when opened. If you have one or more servers listed here that can be ignored for Antimalware configuration replication, you can still run the PopulateAMDatabaseConfigureAction command on the primary server where configuration replication is successfully completed. For information on running the command, see Populate the Antimalware Database.
To fix the configuration replication issue on these servers, copy the amedatasource.properties file from a primary server without issues on to the servers with issues, in the following directory:
Linux: /etc/opt/microfocus/zenworks/antimalware
Windows: C:\Program Files (x86)\Micro Focus\ZENworks\services\antimalware\conf
If your zone is integrated with Vertica for ZENworks dashboard enhancements prior to upgrading to ZENworks 2020 Update 2, you could potentially experience loss of Antimalware Enforcement Policy synchronization with the ZENworks Database. If you see this issue in your Antimalware environment, execute the zman command below on the ZENworks Primary Server to fix it:
zman server-role-kafka-reconfigure-connectors
-or-
zman srkccn