Skip to content

Consul cluster fails to start after a restart due to /etc/consul.d/server_metadata.json: invalid config key last_seen_unix #14757

Consul cluster fails to start after a restart due to /etc/consul.d/server_metadata.json: invalid config key last_seen_unix

Consul cluster fails to start after a restart due to /etc/consul.d/server_metadata.json: invalid config key last_seen_unix #14757

Triggered via issue July 16, 2024 18:38
Status Success
Total duration 19s
Artifacts

issue-comment-created.yml

on: issue_comment
Fit to window
Zoom out
Zoom in

Annotations

1 error and 4 warnings
triage
Error: failed to remove labels: waiting-reply
triage
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-ecosystem/action-remove-labels@2ce5d41b4b6aa8503e285553f75ed56e0a40bae0. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
triage
The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions-ecosystem/action-remove-labels@2ce5d41b4b6aa8503e285553f75ed56e0a40bae0. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
triage
failed to remove label: waiting-reply: HttpError: Label does not exist
triage
The process '/usr/bin/git' failed with exit code 128