Good Morning,
I have tried to restore a back up from a backup created in another computer to my working laptop , and after the backup was restored, I have the following message and I can’t see the logs on the website. I have opened the Wrapper.log but I am failing to see where the problem is, please find the file attached, at the moment I have lost all connections to the gateway, I can’t access anything when I restart the webbrowser all I get is this message so, I don’t know how to go back to a previous backup even.:
Error message:
The Ignition Gateway has failed to successfully start.
Reason: java.lang.IllegalStateException: Cannot sort list of change ops with duplicate manifest changes. Check the logs for more details.
wrapper.log (1.4 MB)
If you want to get into the UI, I guess you can stop your Ignition service, go into your “data” folder in the Ignition directory and rename your “commissioning.json” file to “commissioning_old.json“. Be sure to make a backup of the data folder prior to this if you want to retain any configurations or data.
After this you can start the service and you will be shown the EULA screen from a fresh install of Ignition.
Hopefully from here you can set it up again and retrieve some of your data afterwards from the data folder if needed.
Removing the commissioning file won’t affect your gateway data resources, it will just force you to go through the commissioning process again. Your projects and gw config will remain.
I can't see anything from that log that indicates what caused it to crash, but I would start by looking at the ignition.conf file to see what the heap memory is set to and if the new system can support it
You'll need to contact support to get help fixing your system.
The restore disabled option in 8.3.0/1 unfortunately cause this issue if you use it on a gateway with multiple projects due to an oversight on our part. Now that you're in this state, it's very awkward to get out of to get a successful gateway launch.
We're tracking this as a high priority bug internally, hoping to get it fixed in 8.3.2 or 8.3.3.
1 Like
When restoring a full gateway backup via the web interface or gwmcd you can set an option to restore it in a "disabled" state - the intention being that all of the things in your gateway backup that connect to "live" systems (databases, device connections, etc) will end up "disabled" and not actually affect anything.
It's sort of a bandaid from a world (long) before we had deployment modes. In 8.3, because everything participates in the resource system/is aware of the enabled flag in the same way, restoring a system disabled ends up affecting a lot more than it did before, in a mostly unintentional way. We're not going to change that (it's ultimately more desirable) but there's some rough edges that show up as a result that we're going to iron out.
All of which is separate from the underlying issue with the gateway failing to start the OP is running into - that's just an overzealous assertion in a comparison operation that needs to be relaxed.
1 Like