Skip to content

Latest commit

 

History

History
19 lines (16 loc) · 971 Bytes

2020-05-06_misconfiguration.md

File metadata and controls

19 lines (16 loc) · 971 Bytes
title date severity affectedsystems resolved modified
Misconfiguration
2020-05-06T06:08:24.873Z
under-maintenance
us-nw-1
true
2020-05-06T06:45:04.965Z

A misconfiguration in the router service is preventing a rollover to v2.21.0. As far as we are aware this is not affecting any services.

::: update Resolved | 2020-05-06T06:45:04.965Z The router service has been rolled back to v2.20.7. There was a temporary outage while we resolved this issue. The issue stemmed from the monitor service erroring due to a known issue with Prometheus. We are looking into fixing that, but also ways to avoid the router baulking if an upstream service is unavailable as happened in this situation: nginx: [emerg] host not found in upstream "monitor" in /etc/nginx/conf.d/default.conf:24. :::