Hi All!
We decided to migrate our server from 2.26 to 2.28 directly from the app button. However this doesn´t work because after that the server return a 500 internal error from nginx.
We had a backup of the server for safe and we just got the system restored.
Today we tried to perform the update with the playbook with ansible.
ansible-playbook --flush-cache /usr/share/pmm-update/ansible/playbook/tasks/update.yml
But we got the same error.
The service pmm-managed it is always restarting
So we need any ideas to workaround.
Logs from the supervisor.log are the next
2022-06-01 10:11:55,228 INFO success: pmm-managed entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2022-06-01 10:11:55,765 INFO exited: pmm-managed (exit status 1; not expected)
Thanks in advance!!
1 Like
look in /srv/logs/pmm-managed.log…that should have the first hints at what is going wrong…my guess is the error will repeat every second so hopefully be easy to pick out.
1 Like
Hi Steve, I work alongside Simon.
The pmm-managed.log gives us the following:
time="2022-05-31T13:41:31-03:00" level=info msg="Environment variable \"PERCONA_PLATFORM_API_TIMEOUT\" is not set, using \"30s\" as a default timeout for platform API." request="saasreq init"
INFO[2022-05-31T13:41:31.258-03:00] Log level: info.
ERRO[2022-05-31T13:41:31.259-03:00] telemetry config ID duplication: PMMServerDBaaSEnabled component=config
INFO[2022-05-31T13:41:31.259-03:00] Using default SaaS host "check.percona.com".
INFO[2022-05-31T13:41:31.259-03:00] Using SaaS host "check.percona.com".
INFO[2022-05-31T13:41:31.259-03:00] Migrating database... component=migration
FATA[2022-05-31T13:41:31.296-03:00] Could not create telemetry service: Failed to ping QAN DB: dial tcp: lookup localhost on 192.168.100.5:53: no such host component=main
That log block is constantly repeated given the constant restart of the service.
Hope you can help us with that.
Thank you!
Cheers!
1 Like