@Mirai Thanks for following-up. I re-opened the issue and posted a workaround in fix08.
I’m unsure how introducing a tty/login shell will impact remote access, so I went with a simpler solution which is to prefix the command with sh -c.
@tasket thanks for the quick response.
Unfortunately it still fails
Wyng-util-qubes v0.9 beta rel 20251105
Wyng 0.8.1 (fix08) release 20260427
XXXXXXXXX)'.
mkdir -p -m 777 /tmp/wyngrpc/ && tdir=$(mktemp -d /tmp/wyngrpc/tmpXXXXXXXXXXXX) && echo && echo $tdir && cat >$tdir/dest_helper.py
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^
[0, 127]
StorageError: (5, 'Destination not ready to receive commands.')
@Mirai Seems to be an odd artifact of ssh and its shell invocation. But this new workaround I just posted works on my Ubuntu server when its set to use fish. Hopefully it works for you, too.
@tasket 
fish is version 4.2 on fedora 33 in both the sending and receiving qube.
Wyng-util-qubes v0.9 beta rel 20251105
Wyng 0.8.1 (fishpass) release 20260430
.1 (fishpass) release 20260430
warning: An error occurred while redirecting file '/tmp/wyngrpc/tmpnojr7lxm'
warning: Path '/tmp/wyngrpc' does not exist
/bin/sh: /tmp/wyngrpc/tmpnojr7lxm: No such file or directory
[0, 127]
StorageError: (5, 'Destination not ready to receive commands.')
@Mirai OK, I left out a necessary mkdir before creating the script at that path. Error doesn’t occur if the /tmp/wyngrpc dir already exists.
The fishpass branch has been updated with the necessary changes.
1 Like
@tasket thank you no problems now <3
Wyng is fantastic
1 Like
Please check out the Wyng v0.8.1 and v0.9alpha2 releases being readied…
v0.8.1 in the fix08 branch has some bug fixes and enhanced data recovery in arch-check.
v0.9alpha has arch-copy, which efficiently copies/updates duplicate archives. It also allows passphrase changes, cc @solene. These are some of the most-requested new features, though there are more to come.
3 Likes
can wyng backup running qubes?
what happens if backup destination does not exist and it auto runs the backup (like missing external hdd)?
can i choose not to encrypt the backup (my disk already encrypted)?
@ssh1 By itself Wyng will backup a running VM in the state it had when it was started, not the current state. Similar to the built-in qubes-backup tool, to backup the most recent information with Wyng VMs should be shutdown or restarted prior to running the backup.
Its also possible to run a script to create snapshots of the live VM volumes, possibly by running fsfreeze beforehand to help ensure the VM filesystem is taken in a consistent state. This would allow backing up new information in running VMs without a shutdown or restart. An issue exists for making this an automatic Wyng feature in the future.
Encryption is optional, just use --encrypt=off when creating the archive with wyng arch-init.