Hello, we have an MQTT engine 5.0.1 on an ignition gateway 8.3. We are using source control and after switching branches where the MQTT config doesn’t change, we are having an issue where the gateway webpage stops displaying the settings in the config file, all the checkboxes and entry fields go blank. In addition, when we go to select an option and save it this error pops up.
This is causing an issue for us where the gateway starts to block node and device commands even tho in the config its set to false.
We are able to fix this manually sometimes if we delete the entire mqtt config folder(com.cirruslink.mqtt.engine.gateway) and allow it to regenerate and then we overwrite it with our old mqtt config folder with our settings and do a filescan. This method is mostly repeatable but sometimes we need to do it multiple times. The webpage will start working again after this and we can unblock the node/device commands.
Any advice here on how to prevent this issue would be appreciated! thank you
When it is in this state, what is the value of the ‘securityContextHashingAlgorithm’ in the following file:
[IGNITION_HOME_DIR]/data/config/resources/core/com.cirruslink.mqtt.engine.gateway/general/config.json
i don’t believe its here, i’ve tried manually adding it in and saving it/file scan but it didn’t seem to help
some more detailed info on how i’ve been fixing it, this should be the exact order of events starting from a broken state:
-
were running our dev gateways in a docker, first i docker compose down and stop the gateway
-
delete the entire com.cirruslink.mqtt.engine.gateway folder
-
docker compose up and start gateway
-
a new default com.cirruslink.mqtt.engine.gateway folder is generated, webpage works
-
i copy my desired mqtt folder back into …config/resources/core, it overwrites the default generated mqtt folder
-
file scan, and it continues to work but now with my original settings and includes some default generated servers/sets
-
looking at the git diff it seems that these are the two files that have changed aside from the expected ones being resource files and the default server/set that was added
It seems like there is something wrong with your base config. This is what should be in the namespace-server-set dir by default:
./Sparkplug B-Default Set
./Sparkplug B-Default Set/config.json
./Sparkplug B-Default Set/resource.json
./Elecsys-Default Set
./Elecsys-Default Set/config.json
./Elecsys-Default Set/resource.json
Is it possible for you to start with a clean config and build it up from scratch? It seems like something got mangled in this one. Also, the securityContextHashingAlgorithm should exist in the general config.
got it, ill post in a couple of replies as it only lets me include one screenshot per reply, so I deleted the entire com.cirruslink.mqtt.engine.gateway folder, composed down then up my gateway and let it make a new default version of that mqtt folder, the webpage is in a working state.
checking some key contents you mentioned of the default generated version of the folder:
-
and then i noticed these were generated
the webpage is still working at the moment, i believe this should be the process we followed when originally setting this up, we deleted the Default Set and the default server Chariot SCADA and made our own instances for each, so i think the Elecsys-Default Set and Sparkplug B-Default Set folders were removed. At this point, for some reason after a couple of branch switches in git where we don’t touch these settings or config files, the webpage will then stop working and start complaining about the securityContextHashingAlgorithm.
thanks for your help so far!
