When attempting to start the MySQL Monitor VM, it fails starting the replication-canary process:
starting jobs: mysql_monitor/xxxxx (0) (canary) (00:05:25)
L Error: 'mysql_monitor/xxxxx(0)' is not running after update. Review logs for failed jobs: replication-canary
Looking at the file
/var/vcap/sys/log/replication-canary/replication-canary.stdout.log shows:
{"timestamp":"2022-05-12T06:57:31.234677302Z","level":"fatal","source":"/var/vcap/packages/replication-canary/bin/replication-canary","message":"/var/vcap/packages/replication-canary/bin/replication-canary.Canary setup failed","data":{"error":"Get \"https://1-proxy-p-mysql-<system-domain>/v0/backends\": stopped after 10 redirects","trace":"goroutine 1 [running]:\ncode.cloudfoundry.org/lager.(*logger).Fatal(0xc00004e420, 0x7ef039, 0x13, 0x870960, 0xc00006d470, 0x0, 0x0, 0x0)\n\t/var/vcap/data/compile/replication-canary/replication-canary/vendor/code.cloudfoundry.org/lager/logger.go:138 +0xc6\nmain.main()\n\t/var/vcap/data/compile/replication-canary/replication-canary/main.go:171 +0x1187\n"}}
Checking the router logs shows the request and issue:
gorouter/access.log: 0-proxy-p-mysql-<system-domain> - [2022-05-12T09:02:34.891525785Z] "GET /v0/backends HTTP/1.0" 302 0 94 "https://0-proxy-p-mysql-<system-domain>" "Go-http-client/1.1" "<IP>" "<IP>" x_forwarded_for:"<IP>,<IP>" x_forwarded_proto:"https, https"
The issue is caused by the duplicate
https values included in the
x_forwarded_proto field
.