You are here
So I just tested with the same Odoo image as well as the same Backup set.
I can restore to a ISO created Linode server.
I just installed Virtual Box however (and also did an update to current)
When I install the current OVA install, everything installs but when I go to run a restore I get:
Any thoughts as to why? Is it something to do with Virtualbox being behind NAT or something similar? I suppose I could install from ISO but was hoping to save some time with the OVA install.
thank you.
Linked TKLBAM to your Hub account.
Downloaded turnkey-odoo-16.1-buster-amd64 profile
root@odoo ~# tklbam restore 162
Executing Duplicity to download s3://s3.amazonaws.com/tklbam-us-east-1-deletednumber
y to /tmp/tklbam-7syZVk
===========================================================================================================
========================
// started squid: caching downloaded backup archives to /var/cache/tklbam/restore
# duplicity --archive-dir=/var/cache/duplicity --s3-unencrypted-connection s3://s3.amazonaws.com/tklbam-us-
east-1-deletednumber/deletedhas/tmp/tklbam-something
Last full backup date: none
Traceback (most recent call last):
File "/usr/bin/duplicity", line 1405, in <module>
with_tempdir(main)
File "/usr/bin/duplicity", line 1398, in with_tempdir
fn()
File "/usr/bin/duplicity", line 1332, in main
restore(col_stats)
File "/usr/bin/duplicity", line 637, in restore
restore_get_patched_rop_iter(col_stats)):
File "/usr/bin/duplicity", line 659, in restore_get_patched_rop_iter
backup_chain = col_stats.get_backup_chain_at_time(time)
File "/usr/lib/python2.7/dist-packages/duplicity/collections.py", line 947, in get_backup_chain_at_time
raise CollectionsError("No backup chains found")
CollectionsError: No backup chains found
Traceback (most recent call last):
File "/usr/bin/tklbam", line 46, in <module>
CliWrapper.main()
File "/usr/lib/tklbam/cliwrapper.py", line 88, in main
commands[command].main()
File "/usr/lib/tklbam/cmd_restore.py", line 502, in main
backup_extract_path = get_backup_extract()
File "/usr/lib/tklbam/cmd_restore.py", line 474, in get_backup_extract
ignore_err=opt_ignore_err)
File "/usr/lib/tklbam/duplicity.py", line 182, in __call__
command.run(target.secret, target.credentials, debug=debug)
File "/usr/lib/tklbam/duplicity.py", line 114, in run
raise Error("non-zero exitcode (%d) from backup command: %s" % (exitcode, str(self)))
duplicity.Error: non-zero exitcode (30) from backup command: duplicity --archive-dir=/var/cache/duplicity -
-s3-unencrypted-connection s3://s3.amazonaws.com/tklbam-us-east-deletedID/deletedhas/tm
p/tklbam-something
TKLBAM init was run (and took)
expecting you will ask.
I have to install the Init via either Webshell or Webmin as I can't paste the keycode in to Virtualbox for some reason...
Anyway, I did this to 2 different VM installs. Same result.
I personally use SSH
Even when running local VMs (e.g. in VirtualBox) I still use an SSH client to connect to the server (rather than using the VM window directly. That ensure that you can interact with your VM the same as you would interact with a remote server. Anyway...
I hope you don't mind but I reformatted your original post to make it a bit easier to read. I'm not sure why it didn't work properly when you originally posted it. I tried to format it in a code block, but for some reason, that isn't working?! So I just made it normal text...
Regards to the actual issue though, see this line in the stacktrace:
That suggests to me that you did a typo when you put in the Backup ID number. Are you 100% sure that the backup ID is 162? If you are sure that it's the right backup ID, then be sure to push a full backup. I.e. log into the server that is related to the backup ID and run this:
All good bits of info - but still not
After a full backup I still get "No backup chains found".
It looks to me like something is not passing through, perhaps on account of the network routing and that ultimately the IP on VirtualBox is behind NAT. The Init Key is working in that I can run backups successfully from the VirtualBox install.
I tested 2 different backup sets to VirtualBox that each had had new full backups per your syntax above.
Failure was the same - you can read one below but they were the same.
And just to be sure, Linode to linode, I did the same restore command with my backup install and it is plugging along as we speak (I will likely need to manually pull the Odoo Database, but that is a separate issue, and I see those errors rolling in now when it is trying to overwrite the database with the same name and general structure - lots of constraint xyz already exists).
Noting the Syntax here for a forced full backup
Picture with error text did not post. (sending separate).
Sending the picture separately as it (a screenshot) did not post.
I posted the pic for you.
Hey Landis. I posted the pic for you.
Can you please show me the output of:
Output tklbam-list
-Hi Jeremy,
I can't "copy/paste" via the connection but what it shows is:
The instance itself has backed up with ID #172 on 2022-09-14
I thought I would test on that so running.
Same result
thanks for helping.
Landis
Uploaded from VirtualBox to Oracle Cloud (free) and restoring..
So something with the routing on the internal system. Strange.
I just uploaded to Oracle Cloud a new "initialized" TKL Odoo, and am now running tklbam-restore
It is working in Putty. I need to get access to the web side still but should just be a few settings.
Fair bit work to get that Oracle connection working, but it is..
So on the local VirtualBox I need to tweak something with the Network, but wierd that it seems to do everything but restore.
all for now.
Must be some weird routing or proxy config?
Hmm, it should "just work", but it does sound like there is some weird routing or proxy config that is interfering with the network traffic?! We have had some limited experience with poorly configured proxy networks messing with TKLBAM, but never that explicit message - that's a new one!
Where are you running VirtualBox? If you're running it on on a Windows host, perhaps there is some weird firewall filtering or something?
Windows Server 2016 has the VirtualBox
Virtual Box is on a Windows 2016 Server. I put it there because it is running but not doing too much. I will see if there is some firewall filtering goiing on. I don't really want to put another server into action..
It is strange though.. Are there any other ports I should look to open up for TKLBAM? Backups are fine. Just the restore issue.
Related, of sorts, is that I was able to move that server instance over to Oracle Cloud and TKLBAM did run.. unfortunately I have to figure out how to get Port 80 and 443 to pass some content. Webshell and Webmin (and I believe Putty) are working fine.
More interesting.. initially after restore my Conconsole was all bunged up. I was about to pull the plug on it, but instead I forgot about it. Came back 10 days later and confconsole is working fine. I will kick around a bit more.
It looks like you can run 4 micro instances on Oracle Cloud before they start charging you. Not sure if that means you can also run 2 Small instances or not. Web responsiveness first.
Do you have an exception in Windows Firewall set for VirtualBox?
I'm not sure, but I'd guess that by default, VirtualBox networking is filtered through the built-in Windows firewall. If you haven't already, I'd try adding an explicit exception to allow all VirtualBox traffic to be unfiltered.
Yes it is very strange! All TKLBAM traffic is outgoing (i.e. remote connections are initiated by TKLBAM). So it will use whatever local port it's given by the system. As I note above, VirtualBox networking is likely being filtered through the Windows firewall.
Great work. I've never tried Oracle Cloud and TBH, I'm not the biggest fan of Oracle. However, if they're offering free servers, then can't say I blame you for giving it a go. Re port 80 & 443, my guess is that they have some sort of firewall setup (like AWS has "security groups").
I'm not 100% sure exactly what you are referring to, but I suspect that either it got resized to a size that was incompatible (e.g. can happen if you resize a terminal window too small). If/when that occurs, closing the current connection (e.g. if it's a PuTTY session, just close PuTTY) and restart the session and it should be "fixed".
The other thing that can happen is that it can get overwritten by service output. I don't think that's what you're referring to, but perhaps? The only way to clean that up is to restart Confconsole.
Good luck with Oracle Cloud. Please keep us updated on how it goes.
In other news, no promises and don't hold your breath, but I've been speaking with Alon about doing some dev work on the Hub.
Add new comment