# Gateway Restore command (gwcmd) showing warning and needs manual startup **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [June 13, 2023, 2:08am UTC](https://forum.inductiveautomation.com/t/gateway-restore-command-gwcmd-showing-warning-and-needs-manual-startup/74937 "2023-06-13T02:08:30Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![jaydeepcheruku](https://avatars.discourse-cdn.com/v4/letter/j/c77e96/32.png) [@jaydeepcheruku](https://forum.inductiveautomation.com/u/jaydeepcheruku)\ **Post date:** [June 13, 2023, 2:08am UTC](https://forum.inductiveautomation.com/t/gateway-restore-command-gwcmd-showing-warning-and-needs-manual-startup/74937/1 "2023-06-13T02:08:31Z")
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. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [June 13, 2023, 2:13am UTC](https://forum.inductiveautomation.com/t/gateway-restore-command-gwcmd-showing-warning-and-needs-manual-startup/74937/2 "2023-06-13T02:13:03Z")
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. ---
**Author:** ![jaydeepcheruku](https://avatars.discourse-cdn.com/v4/letter/j/c77e96/32.png) [@jaydeepcheruku](https://forum.inductiveautomation.com/u/jaydeepcheruku)\ **Post date:** [June 13, 2023, 2:24am UTC](https://forum.inductiveautomation.com/t/gateway-restore-command-gwcmd-showing-warning-and-needs-manual-startup/74937/3 "2023-06-13T02:24:28Z")
> [@paul-griffith](#): > Thanks @paul-griffith, I used the command based on ignition documentation itself as well as recommendation from [on L416 here](https://github.com/thirdgen88/ignition-docker/blob/main/7.9/docker-entrypoint.sh#L416). 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. ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [June 13, 2023, 2:40am UTC](https://forum.inductiveautomation.com/t/gateway-restore-command-gwcmd-showing-warning-and-needs-manual-startup/74937/4 "2023-06-13T02:40:29Z")
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](https://docs.inductiveautomation.com/display/DOC81/Docker+Image#DockerImage-AutomatetheCommissioningofaFreshGateway), 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](https://docs.inductiveautomation.com/display/DOC81/Gateway+Command-line+Utility+-+gwcmd#GatewayCommandlineUtilitygwcmd-Command-lineUtility'gwcmd'Options)), it should skip commissioning and restore your gateway backup, all in one shot. ---
**Author:** ![jaydeepcheruku](https://avatars.discourse-cdn.com/v4/letter/j/c77e96/32.png) [@jaydeepcheruku](https://forum.inductiveautomation.com/u/jaydeepcheruku)\ **Post date:** [June 13, 2023, 2:54am UTC](https://forum.inductiveautomation.com/t/gateway-restore-command-gwcmd-showing-warning-and-needs-manual-startup/74937/5 "2023-06-13T02:54:58Z")
> [@kcollins](#): > > `ACCEPT_IGNITION_EULA`, `GATEWAY_ADMIN_PASSWORD`, and possibly `IGNITION_EDITION` @kcollins - 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? ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 13, 2023, 11:09am UTC](https://forum.inductiveautomation.com/t/gateway-restore-command-gwcmd-showing-warning-and-needs-manual-startup/74937/6 "2023-06-13T11:09:46Z")
> [@jaydeepcheruku](#): > > Do we need to do this at the OS level using `export` commands? I recommend placing them in a SystemD override file prior to starting the service. You can alter the override after successful commissioning. ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [June 13, 2023, 1:40pm UTC](https://forum.inductiveautomation.com/t/gateway-restore-command-gwcmd-showing-warning-and-needs-manual-startup/74937/7 "2023-06-13T13:40:26Z")
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](https://forum.inductiveautomation.com/t/ignition-8-1-commissioning-automation/61034/7) for some demo's you might find useful. ---
**Author:** ![jaydeepcheruku](https://avatars.discourse-cdn.com/v4/letter/j/c77e96/32.png) [@jaydeepcheruku](https://forum.inductiveautomation.com/u/jaydeepcheruku)\ **Post date:** [June 13, 2023, 1:42pm UTC](https://forum.inductiveautomation.com/t/gateway-restore-command-gwcmd-showing-warning-and-needs-manual-startup/74937/8 "2023-06-13T13:42:05Z")
Thanks everyone for the recommendations, will try and get back here if I still have any issues. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 13, 2023, 1:44pm UTC](https://forum.inductiveautomation.com/t/gateway-restore-command-gwcmd-showing-warning-and-needs-manual-startup/74937/9 "2023-06-13T13:44:01Z")
> [@kcollins](#): > > so that it will persist across Ignition upgrades I don't leave the commissioning environment variables in the override. After commissioning, I reduce it to just the `AmbientCapabilities` I need.