Skip to content

GCP CloudSQL: Changing the internal network of a database instance

When changing the internal network of an instance, you can expect a five minute downtime: Warning! Changing You can also expect to see these errors on #tms-alerts slack channel:

critical      %!s(<nil>)
service       tms-booking v1.4.56.3 (attracs-tms-backend-3 stable)
[attracs-tms-backend-3] booking: health check failed: database SELECT failed: pq: the database system is shutting down

critical      %!s(<nil>)
service       tms-planner v1.5.13.1 (attracs-tms-backend-3 stable)
[attracs-tms-backend-3] planner: health check failed: database SELECT failed: dial tcp 34.88.30.27:5432: connect: connection refused

critical      %!s(<nil>)
service       tms-drivers v1.5.2 (attracs-tms-backend-3 stable)
[attracs-tms-backend-3] drivers: health check failed: database SELECT failed: pq: the database system is shutting down

error         rpc
service       tms-booking v1.4.56.3 (attracs-tms-backend-4 stable)
RPC.Bookings: twirp error internal: dial tcp 34.88.30.27:5432: connect: connection refused

error         rpc
service       tms-booking v1.4.56.3 (attracs-tms-backend-4 stable)
RPC.Bookings: twirp error internal: pq: the database system is shutting down

critical      %!s(<nil>)
service       tms-planner v1.5.13.1 (attracs-tms-backend-4 stable)
[attracs-tms-backend-4] planner: health check failed: database SELECT failed: dial tcp 34.88.30.27:5432: connect: connection refused

critical      %!s(<nil>)
service       tms-booking v1.4.56.3 (attracs-tms-backend-4 stable)
[attracs-tms-backend-4] booking: health check failed: database SELECT failed: dial tcp 34.88.30.27:5432: connect: connection refused

critical      %!s(<nil>)
service       tms-feedback v1.5.2 (attracs-tms-backend-4 stable)
[attracs-tms-backend-4] feedback: health check failed: database SELECT failed: dial tcp 34.88.30.27:5432: connect: connection refused

critical      %!s(<nil>)
service       tms-fleet v1.5.11 (attracs-tms-backend-4 stable)
[attracs-tms-backend-4] fleet: health check failed: database SELECT failed: dial tcp 34.88.30.27:5432: connect: connection refused

critical      %!s(<nil>)
service       tms-feedback v1.5.2 (attracs-tms-backend-3 stable)
[attracs-tms-backend-3] feedback: health check failed: database SELECT failed: dial tcp 34.88.30.27:5432: connect: connection refused

error         %!s(<nil>)
service       tms-planner v1.5.13.1 (attracs-tms-backend-3 stable)
[tms.v1]: tms_v1.ExecuteBackoff: TripOptionsTo.bookings attempt 3/3 with 1m 30s timeout failed: twirp error internal: dial tcp 34.88.30.27:5432: connect: connection refused

critical      %!s(<nil>)
service       tms-booking v1.4.56.3 (attracs-tms-backend-3 stable)
[attracs-tms-backend-3] booking: health check failed: database SELECT failed: context deadline exceeded

critical      %!s(<nil>)
service       tms-fleet v1.5.11 (attracs-tms-backend-3 stable)
[attracs-tms-backend-3] fleet: health check failed: database ping failed: context deadline exceeded

critical      %!s(<nil>)
service       tms-planner v1.5.13.1 (attracs-tms-backend-3 stable)
[attracs-tms-backend-3] planner: health check failed: database ping failed: context deadline exceeded

critical      %!s(<nil>)
service       tms-drivers v1.5.2 (attracs-tms-backend-4 stable)
[attracs-tms-backend-4] drivers: health check failed: database ping failed: context deadline exceeded

critical      %!s(<nil>)
service       tms-feedback v1.5.2 (attracs-tms-backend-3 stable)
[attracs-tms-backend-3] feedback: health check failed: database ping failed: context deadline exceeded