abra app move hangs, probably non-passwordless sudo? #801

Open
opened 2026-03-24 03:14:12 +00:00 by 3wordchant · 2 comments
Owner
$ abra -d app move foo.bar server.two
(many lines)
INFO <app/move.go:141> moving volume foo_bar_content from server.one to server.two
DEBU <app/move.go:147> creating volume foo_bar_content on server.two
DEBU <app/move.go:157> creating foo_bar_content_outgoing.tar.gz on server.one
(hangs for a long time even with a few kB of data in the volume)

I suspect this is because sudo requires a password on server.one.

If this is an unavoidable limitation, maybe let's document in the -h output?

``` $ abra -d app move foo.bar server.two (many lines) INFO <app/move.go:141> moving volume foo_bar_content from server.one to server.two DEBU <app/move.go:147> creating volume foo_bar_content on server.two DEBU <app/move.go:157> creating foo_bar_content_outgoing.tar.gz on server.one (hangs for a long time even with a few kB of data in the volume) ``` I suspect this is because `sudo` requires a password on `server.one`. If this is an unavoidable limitation, maybe let's document in the `-h` output?
Owner

Hmmmmm yes, that does like sound like a sudo interactive prompt hang? It is documented but is there actually instead a way to test this up front and bail out? I'm not sure. More CAPSLOCK in the sub-command docs and/or a warning output when running the command? I'm open to whatever people feel is proportional 😛

cli/app/move.go Lines 49 to 51 in e04a1e15c4
The "tar" command is required on both the old and new server as well as "sudo"
permissions. The "rsync" command is required on your local machine for
transferring volumes.

tarCmd := fmt.Sprintf("sudo tar --same-owner -czhpf %s -C /var/lib/docker/volumes %s", filename, v.Name)

tarExtractCmd := fmt.Sprintf("sudo tar --same-owner -xzpf %s -C /var/lib/docker/volumes", filename)

cmd = exec.Command("ssh", app.Server, "-tt", fmt.Sprintf("sudo rm -rf %s", filename))

Hmmmmm yes, that does like sound like a `sudo` interactive prompt hang? It is documented but is there actually instead a way to test this up front and bail out? I'm not sure. More CAPSLOCK in the sub-command docs and/or a warning output when running the command? I'm open to whatever people feel is proportional 😛 https://git.coopcloud.tech/toolshed/abra/src/commit/e04a1e15c4459cc7be5e91f0761c6edff33eb2c8/cli/app/move.go#L49-L51 https://git.coopcloud.tech/toolshed/abra/src/commit/e04a1e15c4459cc7be5e91f0761c6edff33eb2c8/cli/app/move.go#L158 https://git.coopcloud.tech/toolshed/abra/src/commit/e04a1e15c4459cc7be5e91f0761c6edff33eb2c8/cli/app/move.go#L177 https://git.coopcloud.tech/toolshed/abra/src/commit/e04a1e15c4459cc7be5e91f0761c6edff33eb2c8/cli/app/move.go#L191
decentral1se added the
bug
label 2026-03-24 06:48:26 +00:00
decentral1se added this to the Abra "next" project 2026-03-24 06:48:42 +00:00
Author
Owner

It is documented

If passwordless sudo is required (and it seems to be) then I would humbly say that should be added to the -h output, I have '"sudo" permissions' (from the existing -h) on both servers… but not passwordless.

> It is documented If passwordless sudo is required (and it seems to be) then I would humbly say that should be added to the `-h` output, I have '"sudo" permissions' (from the existing `-h`) on both servers… but not passwordless.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: toolshed/abra#801
No description provided.