thanks serh. sometimes a knife searh node will hung without any CCR, while sometimes synchronrzing cookbooks hung when CCR. the depend clause in my cookbook metadata.rb does not contain version constaints.
if it is the dependency resolver issue, is it always happen when CCR? in my case it is not always, and after chef-server-ctl restart , it will not hung.
from my phone
Seth Falcon firstname.lastname@example.org编写：
the CPU and Mem looks normal on my chef-server
top - 13:08:29 up 4:12, 3 users, load average: 0.01, 0.02, 0.00
Tasks: 203 total, 1 running, 202 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si,
Mem: 8174384k total, 3595892k used, 4578492k free, 64628k buffers
Swap: 2096472k total, 0k used, 2096472k free, 1435928k cached
The strange thing is all my cookbook and roles are uploaded successfully,
but later on the erchef hungs. Not sure erchef hungs before or after my
chef-client tries to synchronizing cookbook.
Does the server hang at start without receiving chef-client run traffic
or only after nodes check-in and (attempt to) run?
At present, this sounds most like the known issue with the dependency
solver – especially when you describe that updates to cookbooks and
roles work, but CCRs fail.
This would not explain bookshelf hanging, however.
We’ve replaced the dependency solver – restoring the gecode based
solver that is faster and more robust (at the cost of the dependency on
gecode). You can experiment with it by installing a nightly build of