Start a Conversation

Solved!

Go to Solution

1238

May 16th, 2022 06:00

MQTT E:LockBoxKey and Cert Password Error

Hi,

we encountered that MQTT is reported as 'closed' by the ThinClients.

A restart of the mqtt service will lead to following log entries:

12.05.2022 18:11:38 [6] E:Exception caughtUnable to connect to the remote server
12.05.2022 18:11:38 [6] I:Lock box key received as null
12.05.2022 18:11:39 [6] E:Certificate error: keytool error: java.io.IOException: Keystore was tampered with, or password was incorrect
12.05.2022 18:11:39 [6] E:LockBoxKey and Cert Password Error. Retrying... 1
12.05.2022 18:11:44 [6] I:Got API Response as System.Net.HttpWebResponse
12.05.2022 18:11:44 [6] I:Getting some response from lockbox url
12.05.2022 18:11:44 [6] E:The path contains invalid characters. Program will not continue

 

The older log is showing the step from working to not working. There was no change on the system during this time.

26.04.2022 17:31:52 [6] I:MessageQueueSize:0 AssignedClients:0 MessagsProcessed:0 EventQueuesProcessed:0
26.04.2022 17:31:52 [6] I:MessageQueueSize:0 AssignedClients:0 MessagsProcessed:0 EventQueuesProcessed:0
26.04.2022 17:31:52 [6] I:ConnGotten:0 ConnReturned:0 ConnAvailable:279999 MsgAvailable:7 n:0, read_n10, write_n2
26.04.2022 17:31:52 [6] I:pingReq=31566, accCount:5682, MsgAdd:7962, ThState:8:8:8974:8974, to:212, kaD:620
26.04.2022 17:31:52 [6] I:Sessions:147 SubscriptionByTopic:141
26.04.2022 17:31:52 [6] E:Pulse End-669974234
26.04.2022 17:31:52 [6] E:Error Object reference not set to an instance of an object.
Stack trace: at MQTTServer.MainService.ServiceMainProc()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
26.04.2022 17:32:21 [6] E:Exception caughtUnable to connect to the remote server
26.04.2022 17:32:21 [6] I:Lock box key received as null
26.04.2022 17:32:22 [6] E:Certificate error: keytool error: java.io.IOException: Keystore was tampered with, or password was incorrect
26.04.2022 17:32:22 [6] E:LockBoxKey and Cert Password Error. Retrying... 1
26.04.2022 17:32:27 [6] I:Got API Response as System.Net.HttpWebResponse
26.04.2022 17:32:27 [6] I:Getting some response from lockbox url
26.04.2022 17:32:27 [6] E:The path contains invalid characters. Program will not continue

 

A roll-back of the server into an earlier version is not bringing back a working mqtt service.

Any suggestions or hints? Thanks!

4 Posts

June 7th, 2022 16:00

Hi, I too ran into a similar problem after upgrading to 3.6.1 from 3.5.1.

So far my work around to at least get MQTT functioning again was to edit the mqtt conf file in Notepad running as Administrator 

C:\Program Files\DELL\WMS\wmsmqtt\mqtt.conf

1. First comment out these lines:
# sslport 8443

# server_cert_path certSsl
# server_cert_auth UGFzc3dvcmQ5MTE=

2. Check if you are missing this line in the conf file and if so readd it
lockbox_url https://localhost:9443/lockbox/

3. Restart the MQTT service or reboot the server and check your clients afterwards


It seems that the upgrade breaks the service. I installed the newest version on a clean test server and had no problems (of course) and both the MQTT and Secure MQTT service are running. 

This isn't a permanent fix but will get your clients talking again.




3 Posts

May 16th, 2022 07:00

2022-05-16 16:04:58,061 ERROR com.dell.lockbox.interceptor.LockboxInterceptor [qtp1517328406-20] invalid authentication request received
2022-05-16 16:04:58,087 ERROR com.dell.lockbox.interceptor.LockboxInterceptor [qtp1517328406-20] invalid authentication request received
2022-05-16 16:29:56,382 INFO com.dell.lockbox.LockBoxServer [main] Starting LockBoxServer v1.2.0 using Java 11.0.13 on TCMANAGER with PID 3304 (C:\Program Files\DELL\WMS\SoftwareVault\LockBoxServer-1.2.0.jar started by WMSUser in C:\Program Files\DELL\WMS\SoftwareVault)
2022-05-16 16:29:56,382 DEBUG com.dell.lockbox.LockBoxServer [main] Running with Spring Boot v2.6.6, Spring v5.3.18
2022-05-16 16:29:56,382 INFO com.dell.lockbox.LockBoxServer [main] The following 1 profile is active: "private"
2022-05-16 16:29:57,945 INFO com.dell.lockbox.service.LockboxServiceImpl [main] Environment profile : private
2022-05-16 16:29:59,164 INFO com.dell.lockbox.LockBoxServer [main] Started LockBoxServer in 3.725 seconds (JVM running for 4.97)
2022-05-16 16:32:03,380 ERROR com.dell.lockbox.interceptor.LockboxInterceptor [qtp229995302-17] invalid authentication request received
2022-05-16 16:32:03,412 ERROR com.dell.lockbox.interceptor.LockboxInterceptor [qtp229995302-17] invalid authentication request received

3 Posts

June 8th, 2022 00:00

Thanks!
After commenting out the 3 lines (lockbox_url was already in the conf file) and rebooting the machine, the service is back and working.

No Events found!

Top