Ohai chefs !
I'm currently running chef-server 11.0.11 for month.
I succesfully bootstrapped a server, and decided to stop the process after
the first run. I removed the newly created node and client from UI. I
deleted /etc/chef and /var/chef from the server OS.
Then I tried to rebootstrap again the server... and it fails
Now the client part seems not responding :
knife client create test
ERROR: internal server error
Response: internal service error
Bootstrapping Chef on myserver.mydomain.wtf
Starting Chef Client, version 11.10.4
Creating a new client identity for iprod-test-sa-03 using the validator key.
WARN: Failed to register new client, 4 tries remaining
WARN: Response: HTTP 500 - 500 "Internal Server Error"
[...]
Server Unavailable
The Chef Server is temporarily unavailable
Server Response:
502 Bad Gateway
[...]
knife node list is ok, and I still can converge my existing nodes.
I tried chef-server-ctl reindex & restart but I didn't help.
knife node create
test
[7dc567a]
ERROR: internal server error
Response: internal service error
It seems that any write access to chef causes error 
... What can I do ?
I have backups and can rebuild a chef server, but I don't like this kind of
wierd things happening.
Thanks !
--
Barthélemy Vessemont - bvessemont@gmail.com
On Wednesday, March 19, 2014 at 4:16 AM, Barthélemy Vessemont wrote:
Ohai chefs !
I'm currently running chef-server 11.0.11 for month.
I succesfully bootstrapped a server, and decided to stop the process after the first run. I removed the newly created node and client from UI. I deleted /etc/chef and /var/chef from the server OS.
Then I tried to rebootstrap again the server... and it fails
Now the client part seems not responding :
knife client create test
ERROR: internal server error
Response: internal service error
Bootstrapping Chef on myserver.mydomain.wtf
Starting Chef Client, version 11.10.4
Creating a new client identity for iprod-test-sa-03 using the validator key.
WARN: Failed to register new client, 4 tries remaining
WARN: Response: HTTP 500 - 500 "Internal Server Error"
[...]
Server Unavailable
The Chef Server is temporarily unavailable
Server Response:
502 Bad Gateway
[...]
knife node list is ok, and I still can converge my existing nodes.
I tried chef-server-ctl reindex & restart but I didn't help.
knife node create test [7dc567a]
ERROR: internal server error
Response: internal service error
It seems that any write access to chef causes error ... What can I do ?
I have backups and can rebuild a chef server, but I don't like this kind of wierd things happening.
Thanks !
--
Barthélemy Vessemont - bvessemont@gmail.com (mailto:bvessemont@gmail.com)
You might have borked the nginx config, or some services may not be running. What was the process by which you “rebootstrapped”? What does chef-server-ctl status show?
--
Daniel DeLeo
On Wednesday, March 19, 2014 at 7:33 AM, Daniel DeLeo wrote:
On Wednesday, March 19, 2014 at 4:16 AM, Barthélemy Vessemont wrote:
Ohai chefs !
I'm currently running chef-server 11.0.11 for month.
I succesfully bootstrapped a server, and decided to stop the process after the first run. I removed the newly created node and client from UI. I deleted /etc/chef and /var/chef from the server OS.
Then I tried to rebootstrap again the server... and it fails
Now the client part seems not responding :
knife client create test
ERROR: internal server error
Response: internal service error
Bootstrapping Chef on myserver.mydomain.wtf
Starting Chef Client, version 11.10.4
Creating a new client identity for iprod-test-sa-03 using the validator key.
WARN: Failed to register new client, 4 tries remaining
WARN: Response: HTTP 500 - 500 "Internal Server Error"
[...]
Server Unavailable
The Chef Server is temporarily unavailable
Server Response:
502 Bad Gateway
[...]
knife node list is ok, and I still can converge my existing nodes.
I tried chef-server-ctl reindex & restart but I didn't help.
knife node create test [7dc567a]
ERROR: internal server error
Response: internal service error
It seems that any write access to chef causes error ... What can I do ?
I have backups and can rebuild a chef server, but I don't like this kind of wierd things happening.
Thanks !
--
Barthélemy Vessemont - bvessemont@gmail.com (mailto:bvessemont@gmail.com)
You might have borked the nginx config, or some services may not be running. What was the process by which you “rebootstrapped”? What does chef-server-ctl status show?
--
Daniel DeLeo
Also, you can get full server logs by running chef-server-ctl tail, may reveal some important clues.
--
Daniel DeLeo