-
Notifications
You must be signed in to change notification settings - Fork 70
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
Problems running #196
Comments
What are the fabric and paramiko versions? Something else you could try is |
Seems to go ok:
As for the fabric/paramiko versions:
So, permissions issues. I'll look at some env stuff with the ssh command … |
Hmm, sudo definitely seems to be working so I can't imagine what it might be unless the sudo stuff within littlechef isn't actually happening:
|
And with sudo? Looking closer at the stack trace, it happens when updating I'll mark this as a bug. |
That'll be it. Thanks a lot for helping me debug this, would you like me to raise a separate issue about the error handling? |
Ok, so I am no longer convinced this is permission related. I am still getting the problem with sensible permissions in that folder (and the parent directory). Also the error coming back from paramiko doesn't really marry with a permission error. Surely it would have more sensible error messages than "Channel closed." if it was some error with putting the information. It also doesn't really look like it gets very far in to the transport … |
Turns out the paramiko error was actually quite accurate:
I can definitely fix this now I know what it is … sorry to have taken up your time! |
I am not the only person who has had this problem: https://gist.github.com/bradmontgomery/3954511 |
So how did you solve it in the end? And what do you think we can do on LittleChef's side so that users see a more meaningful message that helps them know what kind of error it is? |
So you need to have a SFTP subsystem enabled which, annoyingly, the opscode openssh doesn't enable by default, so you need to add the following attribute (or update it manually if you've not yet cooked and there's no subsystem enabled):
Which only solves it for ubuntu. I am not sure how this can be made clearer what is happening in littlechef because the problem is quite a low level SSH problem that really is quite unrelated to littlechef. I think paramiko could do a better job at describing the circumstance that seems to be going wrong, but it could actually be that it cannot get access to why exactly its connection drops. Maybe just having this issue and it being searchable will be enough that if someone gets |
Also, just want to give some props to @bradmontgomery. Wouldn't have solved it as quickly as I did without his gist being on google. 👍 |
Great, thanks. I created an issue to implement the improved error handling. |
👍 Happy that gist helped! 😄 |
I've been trying to wrack my brains over this one for a while, it's only just started happening. It seems fine when doing every other action except for synchronising the cookbooks etc.
Tried it with both a private key and a password that should both be right and the user has sudo rights.
Anything else I can provide for the problem? (host is Ubuntu 12.04)
The text was updated successfully, but these errors were encountered: