SystemLink Forum

cancel
Showing results for 
Search instead for 
Did you mean: 

RabbitMQ stopped working and cannot re-connect!

Solved!
Go to solution

Hello all, 

We do have a support ticket in with NI, but I would like to see if if anyone else has had this issue with their SystemLink Server. 

We have had a server running for a little over a year now, with little to no issues regarding anything regarding RabbitMQ/Erlang. Today when coming into the office we had noticed that our Web Applications have all stopped working. Once logging onto our host PC, we have discovered that RabbitMQ has stopped working. When trying to relaunch, we get the windows Error 1067, terminated. 

We have tried: 
-SystemLink server repair through NI Package Manager. 
-Uninstalling and re-installation of RabbitMQ for the latest version. 
-Uninstalling and re-installing of Erlang for the latest version. 
-Verifying that all of the Environment Variables are set to directories on the PC instead of anything on the cloud/virtual (suggestion from Google). 

At this point, Windows Services says RabbitMQ is running. But the NI SystemLink Server Configuration says it is unable to connect... Anyone got any insight on this issue? 


"I am prepared to go anywhere, provided it be forward." - David Livingstone
0 Kudos
Message 1 of 7
(3,502 Views)

What version of the SL Server are you running? The only thing that I could think of is the TLS certificate for RabbitMQ that gets created after the initial install expired and the process that automatically renews it isn't working.

0 Kudos
Message 2 of 7
(3,493 Views)

It is also possible the reinstalling Rabbit messed up the credentials. If rabbit is running and configured correctly you should be able to do the following:

 

  1. Get web credentials for RabbitMQ credentials from C:\ProgramData\National Instruments\Skyline\SkylineConfigurations\skyline_localhost.json
  2. Log into RabbitMQ web interface locally on the server at https://localhost:15673/
0 Kudos
Message 3 of 7
(3,492 Views)
Solution
Accepted by topic author CMullinsEE

If that doesn't work you may want to try upgrading to the latest version of SystemLink Server, which should reprovision rabbit.

Message 4 of 7
(3,491 Views)

Thanks for these suggestions! We are currently running SystemLink 2020 R1. 

 

I will try what you have mentioned above and see how that fairs for us, we are hoping that we do not have to go through and do a complete re-installation of everything that would cause us to lose all of our handy work. 😥


"I am prepared to go anywhere, provided it be forward." - David Livingstone
0 Kudos
Message 5 of 7
(3,473 Views)

This AM we successfully logged into Rabbit (thank you for the suggestion to find the credentials), but we still are unsuccessfully booting rabbit utilizing the SystemLink server. 

We are going to try an upgrade of the SL version. 


"I am prepared to go anywhere, provided it be forward." - David Livingstone
0 Kudos
Message 6 of 7
(3,471 Views)

As of right now, it looks like installing the latest version SL 2021 R3 has resolved the RabbitMQ issue. We have some TagHistorian issues now but we are making progress! 

Thank you for your suggestion.


"I am prepared to go anywhere, provided it be forward." - David Livingstone
0 Kudos
Message 7 of 7
(3,467 Views)