After startup, the client shuts down again. The following causes are possible:

No Client Certificates

If no client certificate is available, the following entry appears in the client log: PKIX path building


unable to find valid certification path to requested

  1. Make sure that a client certificate called agent.jts is available under $JAVA_HOME/lib/security.
  1. If the client certificate is not available, complete the following steps:
  • Open the /usr/share/gmg/server/gmg/conf directory on the server.
  • Transfer the certificate securely to the client PC.
  • Copy the agent.jts certificate to the $JAVA_HOME/lib/security directory.

Several Sites and Certificates

It is possible to use several sites and therefore also several certificates. The certificates have to be renamed so that several certificates can be stored in the same folder on the client. However, the certificates on the server must not be modified.

  • At least two different Siveillance Control servers called Server1, Server 2 etc. exist.
  1. Change the name of Server1 certificate on the client from agent.jts to agent-Server1.jts.
  1. Change the certificate for the other servers accordingly.
  • You can also access several different sites on the client.

Non-synchronous Time on Windows Client and Server Machines

The time of Windows client machine and server machine are not synchronized. It is recommended to synchronize time by using NTP. For more information refer to: Synchronizing Time by Using NTP. Otherwise, set time of Windows client and server machines manually.

  1. On the Windows client, right-click the date and time in the Windows task bar.
  1. In the Settings dialog box, choose Date and Time.
  1. Enter the correct date and time.
  1. On the engineering and runtime server machines, login as user root.
  1. To set the time, enter the following command:
    date -s [hh:mm:ss], for example: date -s 10:15:00
  1. To set the date, enter the following command:
    date -s [YYYY-MM-DD], for example: date -s 2023-07-10

Communication to Server is Blocked

If the TCP port 61617 is blocked by firewall settings or the ActiveMQ is not running an error dialog is displayed.

  • The client shows an error dialog at startup that the communication to the server cannot be established.
  1. Make sure that the necessary communication ports are open. For more information refer to: Communication Overview in IT Security.
  1. Make sure that ActiveMQ is running on the servers. Enter the following command to check the status of the AcitveMQ service:
    siveillancecontrol status