SSH error "expected scheme ssh, got 'unix'" is not very helpful #411

Closed
opened 2023-02-13 07:06:47 +00:00 by codegod100 · 2 comments
Member

currently output looks like below, I know you're trying to help me, the problem is it's not very helpful

vera@vultr:~/.abra/recipes/agora$ abra app deploy agora.cloud.vera.pink --debug
DEBU[0000] collecting metadata from 1 servers: cloud.vera.pink  caller="/drone/src/pkg/config/app.go:200 LoadAppFiles"
DEBU[0000] read map[DOMAIN:agora.cloud.vera.pink LETS_ENCRYPT_ENV:production TYPE:agora] from /home/vera/.abra/servers/cloud.vera.pink/agora.cloud.vera.pink.env  caller="/drone/src/pkg/config/env.go:50 ReadEnv"
DEBU[0000] read env map[DOMAIN:agora.cloud.vera.pink LETS_ENCRYPT_ENV:production TYPE:agora] from /home/vera/.abra/servers/cloud.vera.pink/agora.cloud.vera.pink.env  caller="/drone/src/pkg/config/app.go:154 readAppEnvFile"
DEBU[0000] retrieved {agora.cloud.vera.pink agora agora.cloud.vera.pink map[DOMAIN:agora.cloud.vera.pink LETS_ENCRYPT_ENV:production TYPE:agora] cloud.vera.pink /home/vera/.abra/servers/cloud.vera.pink/agora.cloud.vera.pink.env} for agora.cloud.vera.pink  caller="/drone/src/pkg/app/app.go:26 Get"
FATA[0000] expected scheme ssh, got "unix"               caller="/drone/src/cli/internal/validate.go:142 ValidateApp" stack="/drone/src/cli/internal/validate.go:142                  ValidateApp\n/drone/src/cli/internal/deploy.go:26                     DeployAction\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:524     HandleAction\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:173 Command.Run\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:405     (*App).RunAsSubcommand\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:378 Command.startApp\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:102 Command.Run\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:277     (*App).Run\n/drone/src/cli/cli.go:199                                RunApp\n/drone/src/cmd/abra/main.go:22                           main\n/usr/local/go/src/runtime/proc.go:250                    main\n/usr/local/go/src/runtime/asm_amd64.s:1594               goexit"
currently output looks like below, I know you're trying to help me, the problem is it's not very helpful ``` vera@vultr:~/.abra/recipes/agora$ abra app deploy agora.cloud.vera.pink --debug DEBU[0000] collecting metadata from 1 servers: cloud.vera.pink caller="/drone/src/pkg/config/app.go:200 LoadAppFiles" DEBU[0000] read map[DOMAIN:agora.cloud.vera.pink LETS_ENCRYPT_ENV:production TYPE:agora] from /home/vera/.abra/servers/cloud.vera.pink/agora.cloud.vera.pink.env caller="/drone/src/pkg/config/env.go:50 ReadEnv" DEBU[0000] read env map[DOMAIN:agora.cloud.vera.pink LETS_ENCRYPT_ENV:production TYPE:agora] from /home/vera/.abra/servers/cloud.vera.pink/agora.cloud.vera.pink.env caller="/drone/src/pkg/config/app.go:154 readAppEnvFile" DEBU[0000] retrieved {agora.cloud.vera.pink agora agora.cloud.vera.pink map[DOMAIN:agora.cloud.vera.pink LETS_ENCRYPT_ENV:production TYPE:agora] cloud.vera.pink /home/vera/.abra/servers/cloud.vera.pink/agora.cloud.vera.pink.env} for agora.cloud.vera.pink caller="/drone/src/pkg/app/app.go:26 Get" FATA[0000] expected scheme ssh, got "unix" caller="/drone/src/cli/internal/validate.go:142 ValidateApp" stack="/drone/src/cli/internal/validate.go:142 ValidateApp\n/drone/src/cli/internal/deploy.go:26 DeployAction\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:524 HandleAction\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:173 Command.Run\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:405 (*App).RunAsSubcommand\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:378 Command.startApp\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/command.go:102 Command.Run\n/go/pkg/mod/github.com/urfave/cli@v1.22.9/app.go:277 (*App).Run\n/drone/src/cli/cli.go:199 RunApp\n/drone/src/cmd/abra/main.go:22 main\n/usr/local/go/src/runtime/proc.go:250 main\n/usr/local/go/src/runtime/asm_amd64.s:1594 goexit" ```
codegod100 added the
enhancement
label 2023-02-13 07:06:47 +00:00
Owner

abra is sometimes invoking a Docker CLI command but often not. So, we can't always point to a command that is being invoked. This does remind me of #219 though.

expected scheme ssh, got "unix" is in the error message which relates to the very buggy host key checking implementation that we had in 0.6.0-beta but has been largely removed in the 0.7.x series, you may be able to work around this by running abra upgrade --rc but you also may run into new bugs 🙃

If this is still a --local environment deployment then yeh, I can see why we might have several bugs. I am not sure folks are actively running stuff in this mode, so we don't so many bug reports against it?

Thanks for the patience & the reports!

`abra` is sometimes invoking a Docker CLI command but often not. So, we can't always point to a command that is being invoked. This does remind me of https://git.coopcloud.tech/coop-cloud/organising/issues/219 though. `expected scheme ssh, got "unix"` is in the error message which relates to the very buggy host key checking implementation that we had in `0.6.0-beta` but has been largely removed in the `0.7.x` series, you may be able to work around this by running `abra upgrade --rc` but you also may run into new bugs 🙃 If this is still a `--local` environment deployment then yeh, I can see why we might have several bugs. I am not sure folks are actively running stuff in this mode, so we don't so many bug reports against it? Thanks for the patience & the reports!
decentral1se changed title from better output on what the command abra is running on cli so I can manually reproduce to SSH error "expected scheme ssh, got 'unix'" is not very helpful 2023-02-14 07:20:24 +00:00
decentral1se added the
abra
label 2023-02-14 07:22:53 +00:00
Owner

Optimistically closing this with a "the new release candidate / upcoming release solves the bad error message" and the related ticket would be best to work out how to document what commands are being run, in general?

Optimistically closing this with a "the new release candidate / upcoming release solves the bad error message" and the related ticket would be best to work out how to document what commands are being run, in general?
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coop-cloud/organising#411
No description provided.