Lee Thornhill's picture

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:
(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>
File "/bin/tklbam-backup", line 374, in main
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


Jeremy Davis's picture

Apologies on the radio silence. This is a new issue for me that I've never encountered before. I've been looking into it but I neglected to let you know what was going on. I should have let you know that was what I was up to.

Anyway, I've worked it out. The fix is pretty simple. Just delete the 'hubclient' info, like this:

rm -r /var/lib/hubclient

Then (assuming that it's already initialized) tklbam should "just work".

Please post back if you continue to have issues.

L. Arnold's picture

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!)


L. Arnold's picture

Very Helpful.  Thanks for asking and posting that.

Next is, how to attach the migrated (between AWS accounts) to an attached Hub account?

If TKLBAM restore goes well that could be a way but if they have updated odoo Code in

/usr/lib/python3/odoo  that needs to also move.

Easiest would be to simply attach to the hub.  Hub is active on the AWS account this server we moved is attached to.

Add new comment