HI @steve.hoffman
Thanks for your response.
We tried to upgrade to the latest version but unfortunately, Mysql azure servers ended up with SSL issues.
Now deleted the latest version and installed 2.14.0.
Now QAN service and click house not starting
Below is the status
[root@8c31b038c6c9 logs]# supervisorctl status
alertmanager RUNNING pid 153, uptime 0:14:29
clickhouse FATAL Exited too quickly (process log may have details)
cron RUNNING pid 19, uptime 0:14:31
dashboard-upgrade EXITED Sep 29 03:51 AM
dbaas-controller STOPPED Not started
grafana RUNNING pid 928, uptime 0:13:56
nginx RUNNING pid 18, uptime 0:14:31
pmm-agent RUNNING pid 37, uptime 0:14:31
pmm-managed RUNNING pid 34, uptime 0:14:31
pmm-update-perform STOPPED Not started
postgresql RUNNING pid 15, uptime 0:14:31
prometheus STOPPED Not started
qan-api2 BACKOFF Exited too quickly (process log may have details)
victoriametrics RUNNING pid 119, uptime 0:14:30
vmalert RUNNING pid 25, uptime 0:14:31
Below is the qan agent error logs
stdlog: qan-api2 v2.14.0.
INFO[2021-09-29T04:00:44.653+00:00] Log level: info.
stdlog: Connection: dial tcp 127.0.0.1:9000: connect: connection refused
stdlog: qan-api2 v2.14.0.
INFO[2021-09-29T04:01:18.757+00:00] Log level: info.
stdlog: Connection: dial tcp 127.0.0.1:9000: connect: connection refused
stdlog: qan-api2 v2.14.0.
INFO[2021-09-29T04:01:53.838+00:00] Log level: info.
stdlog: Connection: dial tcp 127.0.0.1:9000: connect: connection refused
stdlog: qan-api2 v2.14.0.
INFO[2021-09-29T04:02:30.036+00:00] Log level: info.
stdlog: Connection: dial tcp 127.0.0.1:9000: connect: connection refused
stdlog: qan-api2 v2.14.0.
INFO[2021-09-29T04:03:07.315+00:00] Log level: info.
stdlog: Connection: dial tcp 127.0.0.1:9000: connect: connection refused
stdlog: qan-api2 v2.14.0.
INFO[2021-09-29T04:03:45.448+00:00] Log level: info.
stdlog: Connection: dial tcp 127.0.0.1:9000: connect: connection refused
stdlog: qan-api2 v2.14.0.
INFO[2021-09-29T04:04:24.655+00:00] Log level: info.
stdlog: Connection: dial tcp 127.0.0.1:9000: connect: connection refused
stdlog: qan-api2 v2.14.0.
INFO[2021-09-29T04:05:04.715+00:00] Log level: info.
stdlog: Connection: dial tcp 127.0.0.1:9000: connect: connection refused
stdlog: qan-api2 v2.14.0.
INFO[2021-09-29T04:05:45.759+00:00] Log level: info.
stdlog: Connection: dial tcp 127.0.0.1:9000: connect: connection refused
stdlog: qan-api2 v2.14.0.
INFO[2021-09-29T04:06:28.126+00:00] Log level: info.
stdlog: Connection: dial tcp 127.0.0.1:9000: connect: connection refused
Docker logs
2021-09-29 03:54:51,234 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 03:55:12,288 INFO spawned: ‘qan-api2’ with pid 1826
2021-09-29 03:55:12,332 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 03:55:34,623 INFO spawned: ‘qan-api2’ with pid 1900
2021-09-29 03:55:34,669 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 03:55:58,080 INFO spawned: ‘qan-api2’ with pid 1969
2021-09-29 03:55:58,126 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 03:56:22,317 INFO spawned: ‘qan-api2’ with pid 2081
2021-09-29 03:56:22,358 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 03:56:47,102 INFO spawned: ‘qan-api2’ with pid 2159
2021-09-29 03:56:47,147 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 03:57:13,168 INFO spawned: ‘qan-api2’ with pid 2270
2021-09-29 03:57:13,213 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 03:57:40,222 INFO spawned: ‘qan-api2’ with pid 2355
2021-09-29 03:57:40,261 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 03:58:08,344 INFO spawned: ‘qan-api2’ with pid 2465
2021-09-29 03:58:08,386 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 03:58:37,500 INFO spawned: ‘qan-api2’ with pid 2562
2021-09-29 03:58:37,543 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 03:59:08,081 INFO spawned: ‘qan-api2’ with pid 2681
2021-09-29 03:59:08,127 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 03:59:39,142 INFO spawned: ‘qan-api2’ with pid 2771
2021-09-29 03:59:39,185 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 04:00:11,288 INFO spawned: ‘qan-api2’ with pid 2898
2021-09-29 04:00:11,329 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 04:00:44,623 INFO spawned: ‘qan-api2’ with pid 2994
2021-09-29 04:00:44,660 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 04:01:18,712 INFO spawned: ‘qan-api2’ with pid 3138
2021-09-29 04:01:18,758 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 04:01:53,791 INFO spawned: ‘qan-api2’ with pid 3246
2021-09-29 04:01:53,840 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 04:02:29,992 INFO spawned: ‘qan-api2’ with pid 3377
2021-09-29 04:02:30,037 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 04:03:07,281 INFO spawned: ‘qan-api2’ with pid 3510
2021-09-29 04:03:07,316 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 04:03:45,411 INFO spawned: ‘qan-api2’ with pid 3623
2021-09-29 04:03:45,450 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 04:04:24,619 INFO spawned: ‘qan-api2’ with pid 3765
2021-09-29 04:04:24,658 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 04:05:04,675 INFO spawned: ‘qan-api2’ with pid 3905
2021-09-29 04:05:04,717 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 04:05:45,719 INFO spawned: ‘qan-api2’ with pid 4019
2021-09-29 04:05:45,761 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 04:06:28,081 INFO spawned: ‘qan-api2’ with pid 4172
2021-09-29 04:06:28,127 INFO exited: qan-api2 (exit status 1; not expected)
2021-09-29 04:07:11,187 INFO spawned: ‘qan-api2’ with pid 4322
2021-09-29 04:07:11,229 INFO exited: qan-api2 (exit status 1; not expected)
AttachedProcessing: pmm-server_2021-09-29_04-08.zip…
PMM server logs
can you please assist us with what went wrong