Forum archive
tklbam error after AWS server migration
We have migrated an EC2 instance from our vendor's account to our own. After migrating we tried to point the backups to our turnkey api. We get a fault with the server ID does not exist. Any suggestions?
Also, how do we put this instance into our new Turnkey Hub account?
console commands:
tunkey-init
(update pw and api key)
rm -rf /var/lib/tklbam
tunkey-init
(update pw and api key)
rm -rf /var/lib/tklbam
apt-get remove --purge tklbam
apt-get install tklbam
tklbam-init --force
From Webmin:
Run Backup (or tklbam backup from console)
> tklbam-backup
Traceback (most recent call last):
File "/bin/tklbam-backup", line 510, in <module>
main()
File "/bin/tklbam-backup", line 374, in main
get_server_id())
File "/usr/lib/tklbam/hub.py", line 270, in new_backup_record
response = self._api('POST', 'record/create/', attrs)
File "/usr/lib/tklbam/hub.py", line 226, in _api
return self.api.request(method, self.API_URL + uri, attrs, headers)
File "/usr/lib/tklbam/hub.py", line 126, in request
raise APIError(e.code, e.name, e.description)
hub.APIError: Server ID does not exist: XXXXXXXXXXXXXXXXXXXXXXXX
As noted the server was moved between AWS accounts. We have seemingly moved the TKLBAM ownership. How do we also reset the Cron email notification?
As noted below, would also be nice to have this server attach to the owner's Hub account.
(thanks again for the hubclient fix!)