Skip to content
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

Can't --copy #493

Closed
iomari opened this issue Nov 22, 2022 · 2 comments · Fixed by #504
Closed

Can't --copy #493

iomari opened this issue Nov 22, 2022 · 2 comments · Fixed by #504
Assignees
Labels
Milestone

Comments

@iomari
Copy link

iomari commented Nov 22, 2022

If I run: clush -b -w 'root@enode[01-04,06-10,12-20]' uptime I get the proper results.
But If I run: clush -w 'root@enode[01-04,06-10,12-20]' --copy /temp/x1234 --dest /temp/
I get:

root@enode01: ssh: Could not resolve hostname enode01]: Name or service not known
root@enode01: lost connection
root@enode02: ssh: Could not resolve hostname enode02]: Name or service not known
root@enode02: lost connection
root@enode03: ssh: Could not resolve hostname enode03]: Name or service not known
root@enode03: lost connection
root@enode04: ssh: Could not resolve hostname enode04]: Name or service not known
root@enode04: lost connection
root@enode06: ssh: Could not resolve hostname enode06]: Name or service not known
root@enode06: lost connection
root@enode07: ssh: Could not resolve hostname enode07]: Name or service not known
root@enode07: lost connection
root@enode08: ssh: Could not resolve hostname enode08]: Name or service not known
root@enode08: lost connection
root@enode09: ssh: Could not resolve hostname enode09]: Name or service not known
root@enode09: lost connection
root@enode10: ssh: Could not resolve hostname enode10]: Name or service not known
root@enode10: lost connection
root@enode12: ssh: Could not resolve hostname enode12]: Name or service not known
root@enode12: lost connection
root@enode13: ssh: Could not resolve hostname enode13]: Name or service not known
root@enode13: lost connection
root@enode14: ssh: Could not resolve hostname enode14]: Name or service not known
root@enode14: lost connection
root@enode15: ssh: Could not resolve hostname enode15]: Name or service not known
root@enode15: lost connection
root@enode16: ssh: Could not resolve hostname enode16]: Name or service not known
root@enode16: lost connection
root@enode17: ssh: Could not resolve hostname enode17]: Name or service not known
root@enode17: lost connection
root@enode18: ssh: Could not resolve hostname enode18]: Name or service not known
root@enode18: lost connection
root@enode19: ssh: Could not resolve hostname enode19]: Name or service not known
root@enode19: lost connection
clush: root@enode01: exited with exit code 1
clush: root@enode02: exited with exit code 1
clush: root@enode03: exited with exit code 1
clush: root@enode04: exited with exit code 1
clush: root@enode06: exited with exit code 1
clush: root@enode07: exited with exit code 1
clush: root@enode08: exited with exit code 1
clush: root@enode09: exited with exit code 1
clush: root@enode10: exited with exit code 1
clush: root@enode12: exited with exit code 1
clush: root@enode13: exited with exit code 1
clush: root@enode14: exited with exit code 1
clush: root@enode15: exited with exit code 1
clush: root@enode16: exited with exit code 1
clush: root@enode17: exited with exit code 1
clush: root@enode18: exited with exit code 1
clush: root@enode19: exited with exit code 1
root@enode20: ssh: Could not resolve hostname enode20]: Name or service not known
root@enode20: lost connection
clush: root@enode20: exited with exit code 1

I'm running kubuntu 21.10 with zsh as my shell

@thiell
Copy link
Collaborator

thiell commented Nov 22, 2022

Hey @iomari,
The recommended usage is rather --user root -w 'enode[01-04,06-10,12-20]'
We can make that more clear in the documentation.

If you add the debug flag -d you will see that clush launches scp by adding brackets around the host. This is for ipv6 support (brackets are required by scp in that case), but it breaks your example.

@iomari
Copy link
Author

iomari commented Nov 22, 2022

thanks. it worked.

@thiell thiell added this to the 1.9 milestone Nov 23, 2022
@thiell thiell self-assigned this Nov 23, 2022
@thiell thiell added the Doc label Nov 23, 2022
thiell added a commit to thiell/clustershell that referenced this issue Nov 27, 2022
@thiell thiell mentioned this issue Nov 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants