Agent application failed to start

Issue description

The Protection Agent fails to start with a log error: APPLICATION FAILED TO START. 

How to identify the problem

When manually starting up the agent, the Cibecs icon does not load and only returns an error in the log.

If you have a look through the Cibecs Agent log, you will find the following entries.  Find the Protection Agent log here: C:\Users\username\AppData\Roaming\Cibecs\Agent\Logs\agent.log


Log entry:

Parameter 9 of constructor in mu.cibecs.components.websocket.client.WebSocketClientProtocolHandler required a bean of type 'org.eclipse.jetty.client.HttpClient' that could not be found.

Consider defining a bean of type 'org.eclipse.jetty.client.HttpClient' in your configuration.

What caused this problem?

The agent configuration changed or went missing. This could have been caused by a sudden unexpected shutdown of the Protection Agent, for example, an abrupt power loss that took place. It was also noted that the installed version of the agent was outdated and unsupported.

How do I resolve this problem?

Upgrade or re-install the Protection Agent in order to fix the agent configuration.


It is best practice to upgrade the Protection Agent to the latest supported version.

Check if the problem has been fixed

If the problem has been fixed, then you should be able to successfully run the agent. You should also run a test restore and manual backup to confirm.