oswaldlabs / chef-rundeck

Integrates Chef with RunDeck, we are referring users to https://github.com/atheiman/better-chef-rundeck as this repository is inactive at this time.
Apache License 2.0
97 stars 85 forks source link

Net::HTTPServerException - 401 "Unauthorized #41

Closed ColOfAbRiX closed 10 years ago

ColOfAbRiX commented 10 years ago

Hi, I'm trying chef-rundeck for the first time and I get this error. I launch chef-rundeck with chef-rundeck -k /etc/chef/client.pem -c /etc/chef/client.rb -w https://vmchef

I have tried many different things, like permission changes, different keys and users, even reinstalling chef, ruby and rundeck but I cannot understand what the real problem is.

This is the error I see in the web console: Cannot get nodes from [URLResourceModelSource{URL='http://localhost:9980'}]: Error requesting URL Resource Model Source: http://localhost:9980: com.dtolabs.rundeck.core.common.FileUpdaterException: Unable to retrieve content: result code: 500 Internal Server Error

And this is the log: Writing to /var/run/chef-rundeck-9980.pid Puma 1.6.3 starting...

josephholsten commented 10 years ago

looks like your chef server doesn't like your client key for the node name you're using. Can you verify that they match?

ColOfAbRiX commented 10 years ago

The key that I use is generated through knife bootstrap and the client works perfectly. I have also tested different keys like a user key. I forgot to say that I am using SuSE Linux 11 SP3 and chef-rundeck is running on a client. Should it run in the server?

bscott commented 10 years ago

@ColOfAbRiX Try running it on the server

What version of ruby are you using?

bscott commented 10 years ago

@ColOfAbRiX Try latest that's in master

ColOfAbRiX commented 10 years ago

I have partially solved the problem. I found that I need to specify the user as the default one is wrong, now it connects.

chef-rundeck -u "$(hostname -f)" -k "/etc/chef/client.pem" -c "/etc/chef/client.rb" -w "https://vmchef"

But there is a new issue that I'll post now.