-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Difficult to debug 'Destination not ready to receive commands.' errors even with '--debug' flag. #233
Comments
@t-gh-ctrl It is looking for 'archive.ini' file in the destination dir. I'll try to reproduce the |
I'm not sure that's the culprit: I took [edit] - here's a log with the archive that used to work:
|
@t-gh-ctrl I've been trying to improved detection at the dest location. Pushed an update to 08wip. Also, when you run Wyng with |
Yes, that's fixed! (by the way I tested 20250117 meanwhile - it works - so one of the recent changes in v20250121 broke something; but why it worked for a couple days and then stopped working out of the blue is a mistery).
Oh, I didn't know, that will be helpful. Thank you! [edit - you rock; I donated via liberapay but I realized after making my payment that instead of receiving the whole amount you'll get a fraction of it each week over the next 12 months. So you'll drink only one coffee/beer a week from me :) ] |
Thank you for the donation! :) |
[apologies for spamming you with issues; this issue is somehow related to #232 but with a specific problem that I don't manage to debug]
wyng 20250121 on QubesOS 4.2.3
All of a sudden I began to have 'Destination not ready to receive commands.' errors when backup'ing volumes with a qubes-ssh destination ([edit: I get the issue with a local filesytem destination too ; logs appended]). That setup has been working well for the past month or so (automated backups running while the machine becomes idle), even while doing many tests over the last week when testing new versions.
The only two things that I remember that have changed are 1/ the ssh host got restarted after a nightly kernel update (there weren't any other updates) and 2/ I removed a user on that host, but it wasn't related to wyng.
So, I'm quite puzzled, as I can't manage to find/debug what's going on.
For the sake of debugging, I'm starting from scratch with
arch-init
but I get the same thing while sending volumes (I haven't tried other commands though).Yet, ssh to the ssh host with the options used by wyng works, the folder on the ssh host is writeable, wyng has even created an archive there:
Any tip on how to debug this further?
[edit] - I thought the problem would be because of something that may have changed on the remote host, but I just tried with a "blank" installation and a local destination, and it fails too:
Cleanup:
arch-init
:wyng created files in the dest folder:
The text was updated successfully, but these errors were encountered: