ZENworks client management service overload

Hi!

I have 5 servers, 3 of which have zookeeper (1,3,5)

When I simulate a failure, I turn off servers 1, 2 and 3. I still have servers 4 and 5 online.

In this case, the ZENworks Client Management service saturates on the diagnostics page, and access to the database is 100%.

This leads to problems managing requests from stations that go out on time and are not processed by the servers (inventory, refreshing, teledistribution).

Do you have any ideas?


Kind Regards,

Parents Reply Children
  • 0 in reply to   

    We've checked with support in the database and on the server configurations and it's fine from that point of view.

    Servers 1, 2 and 3 are on one server network and located on one physical site, and servers 4 and 5 are on another physical site and on another server network. During normal operation, the servers communicate correctly with each other.

    I don't think the problem is the network.

    From my point of view, it's the servers remaining up in the zone that saturate the connections with the database and block the release of the ZENworks Client management service, but I don't understand why.

    Is it possible that the last remaining server is saturated because the 2 switched-off servers with zookeeper can't communicate?
    If so, is there any way to free up resources or work around the problem?