jprdonnelly/docs
1
0
Fork 0
mirror of synced 2025-12-19 18:10:59 -05:00
Code Issues Projects Releases Wiki Activity

Update docs with node rejoin timeout and workaround (#52296)

Browse Source 
Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com>
This commit is contained in:
Pallavi
2024-10-08 04:40:11 -07:00
committed by GitHub
parent 6a85662f9c
commit a7fee1a7a9
1 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
content/admin/installing-your-enterprise-server/setting-up-a-github-enterprise-server-instance/setting-up-a-staging-instance.md
View File

@@ -154,6 +154,21 @@ Then, review the staging instance's configuration in the {% data variables.enter
To apply the configuration from the {% data variables.enterprise.management_console %}, click **Save settings**.
## Bringing a staging instance back online
You may want to power off a staging instance to save costs and power it back on when needed.
An instance can stay offline for {% ifversion ghes = 3.10 %}7 days{% elsif ghes < 3.14 %}60 days as of the latest patch release of this version, increased from 7 days{% else %}60 days{% endif %}.
If you bring the instance back online within the allowed offline time period, {% data variables.product.product_name %} instantiates successfully. If the instance stays offline for longer than the allowed period, {% data variables.product.product_name %} fails to instantiate successfully, and an error message with the text `server has been offline for more than the configured server_rejoin_age_max` may appear in the system logs. See "[AUTOTITLE](/admin/monitoring-and-managing-your-instance/monitoring-your-instance/about-system-logs)."
If the instance is stuck in the error state, you can run these commands to recover.
```shell
sudo mv /data/user/consul/server_metadata.json /data/user/consul/server_metadata.json.bak
ghe-config-apply
```
## Further reading
* "[AUTOTITLE](/admin/overview/about-upgrades-to-new-releases)"