Gateway Restore command (gwcmd) showing warning and needs manual startup

Ignition
1

I am trying to automate the gateway upgrade process and noticing this error. Even though everything seems to be restored the gateway is asking to manually startup the gateway [need to click (1) agree, (2) provide user/pwd (3) finish setup + login]

sh gwcmd.sh --restore /tmp/backup.gwbk -y
Restoration success message was not received from the Gateway. Will attempt to place a __restore.gwbk file in the data folder.
Gateway backup restored, manual startup required

PS - got same error message while upgrading from 7.9.14 to 8.1.24 and 8.1.24 to 8.1.25

Appreciate any help in avoiding this error.

2

Upgrades from 7.9 to 8.1 have a different EULA that requires manual acceptance via commissioning. You may get some inspiration for bypass from Kevin Collins' official unofficial Docker image.

3

Thanks @PGriffith, I used the command based on ignition documentation itself as well as recommendation from on L416 here .

I used "-m" option too but no luck
sh gwcmd.sh --restore /tmp/backup.gwbk -y -m

Also if 7.9 to 8.1 is an issue due to different EULA, I wonder why I got the same error when testing upgrade from 8.1.24 to 8.1.25 ?

Thanks for the insights in advance.

4

The good news for some of this is that the environment variables for automating the commissioning steps function in the base platform as well as the Docker images. The environment variables you need are ACCEPT_IGNITION_EULA, GATEWAY_ADMIN_PASSWORD, and possibly IGNITION_EDITION. More details here, although like I mentioned, you can supply these particular environment variables to a regular installation of Ignition too..

EDIT: I should also mention for clarity that if you do the above combined with restoring your GWBK (with the skip-gateway-contact option, documented here), it should skip commissioning and restore your gateway backup, all in one shot.

1 Like
5

@kcollins1 - Since I am not using docker in this case, could you please provide an example/sample of how to supply below parameters as part of base platform aka regular installation of ignition?

ACCEPT_IGNITION_EULA , GATEWAY_ADMIN_PASSWORD , and possibly IGNITION_EDITION

PS: We use the zip file to install ignition and not the installer file, on our linux OS.

Do we need to do this at the OS level using export commands?

6

I recommend placing them in a SystemD override file prior to starting the service. You can alter the override after successful commissioning.

7

Agreed on the systemd override configuration so that it will persist across Ignition upgrades (that might set/reset the base service configuration). Take a look at this post for some demo's you might find useful.

8

Thanks everyone for the recommendations, will try and get back here if I still have any issues.

9

I don't leave the commissioning environment variables in the override. After commissioning, I reduce it to just the AmbientCapabilities I need.