[BUG] Error installing utm agent

[agauttam]

Describe the bug
UTMStack: error: error installing UTMStack services: error installing UTMStackAgent service: Check the file /logs/utmstack_agent.log for more details

error while reinstalling the agent

Environment

• OS: [e.g. Windows 11, Ubuntu 22.04]
• Browser [e.g. Firefox, Chrome, Safari]
• Version [e.g. v10.4.2]

Additional context

Add any other context about the problem here.
2024-05-10T09:10:46.5000876Z INFO eea81247-9adb-4112-a621-098ca1360422 C:/Users/aimng/actions-runner/_work/UTMStack/UTMStack/agent/agent/main.go 38 Installing UTMStack Agent service...
2024-05-10T09:10:49.1631865Z INFO 2ac16034-2ad8-43e7-afb5-9dfe91b04b01 C:/Users/aimng/actions-runner/_work/UTMStack/UTMStack/agent/agent/conn/conn.go 35 trying to connect to Server...
2024-05-10T09:10:49.1643543Z INFO fa2c2df2-8ca0-46b4-b7cd-873be667947d C:/Users/aimng/actions-runner/_work/UTMStack/UTMStack/agent/agent/main.go 60 Connection to Agent Manager successful!!!
2024-05-10T09:10:49.4070763Z ERROR f2098e0b-aa51-46be-aae2-901f59df720d C:/Users/aimng/actions-runner/_work/UTMStack/UTMStack/agent/agent/main.go 64 failed to register agent: rpc error: code = Unauthenticated desc = unable to connect with the panel to check the connection key

[agauttam]

on Backend server getting the below error

Checking elasticsearch connection:
> Success
2024-05-16 10:48:17.300 ERROR 1 --- [ XNIO-1 task-1] c.p.utmstack.web.rest.UserJWTController : UserJWTController.authorizeFederationServiceManager: Connection key is corrupt, unrecognized instance
2024-05-16 10:48:17.300 ERROR 1 --- [ XNIO-1 task-1] c.p.utmstack.web.rest.util.HeaderUtil : Entity processing failed, UserJWTController.authorizeFederationService Manager: Connection key is corrupt, unrecognized instance
Checking elasticsearch connection:
> Success
Checking elasticsearch connection:
> Success
2024-05-16 10:50:25.239 WARN 1 --- [ XNIO-1 task-1] com.zaxxer.hikari.pool.PoolBase : Hikari - Failed to validate connection org.postgresql.jdbc.PgConnectio n@40bc43ce (This connection has been closed.). Possibly consider using a shorter maxLifetime value.

[c3s4rfred]

Hi @agauttam that kind of error occours during a bad installation, permission issues or if somebody touches the utmstack.yml file located on the root. Those values are used from internal services to communicate with each other and for encryption purposes, so, if the connection key can't be accessed or if it is changed, the system won't work properly. In this case you must consider a full reinstallation if you don't have a way to restore the file to its original state.

[agauttam]

I have the key. The issue began when I disabled the Admin user and then re-enabled it after noticing some misbehavior in the system. A few days later, after performing an upgrade, I started encountering these errors.

[c3s4rfred]

Also can be a network issue that avoid the communication between the agent's machine and the UTMStack's instance machine.
Best regards

[agauttam]

Hi Freddy,
It's not due to a network issue; it happened because the key was corrupted. Please help me with the steps to replace the key.

[c3s4rfred]

Hi, @agauttam corrupted keys are a big problem because are used for encryption as said before, let me check with a teammate to look for a workaround.

[agauttam]

Hi Freedy,

As i remembered, I have spinned the installer from the another path, because of that this issue occured.
It will be helpful if you can share the process to recover from this situation.

Regards,
Arun

[osmontero]

It doesn't matter where you run the installer. The persistence file will always be in the /root folder and the ephemeral compose file will be created in the user folder, but it is not important and can be deleted, etc. because the installer always generates it from the persistence file in /root.

[agauttam]

Than maybe due to something esle my key is corrupted, As i remembered issue occurred after upgrade.

Regards,
Arun