Push job client can't connect to push job service successfully


#1

When i use chef-client command to configure push-job-client to my machine, the result is always
" - execute the ruby block wait for chef-push-jobs-client service socket",

And I can see my node by using “knife client list” command , but can’t see it by using “knife node status” command which i event can’t see the node name.

And here is the log in chef-client machine:
INFO: [delta.chef.client2] Listening for server heartbeat at tcp://delta.chef.server:10000
INFO: [delta.chef.client2] Listening for server heartbeat at tcp://delta.chef.server:10000
INFO: [delta.chef.client2] Connecting to command channel at tcp://delta.chef.server:10002
INFO: [delta.chef.client2] Connecting to command channel at tcp://delta.chef.server:10002
INFO: [delta.chef.client2] Considering server online, and starting to heartbeat
INFO: [delta.chef.client2] Considering server online, and starting to heartbeat
INFO: [delta.chef.client2] Starting command / server heartbeat receive thread …
INFO: [delta.chef.client2] Started client.
INFO: [delta.chef.client2] Started client.
INFO: [delta.chef.client2] Starting reconfigure thread. Will reconfigure / reload keys after 3600 seconds, less up to splay 0.1.
INFO: [delta.chef.client2] Starting reconfigure thread. Will reconfigure / reload keys after 3600 seconds, less up to splay 0.1.
INFO: [delta.chef.client2] Starting heartbeat / offline detection thread on interval 10.0 …
INFO: [delta.chef.client2] Starting command / server heartbeat receive thread …
INFO: [delta.chef.client2] Starting heartbeat / offline detection thread on interval 10.0 …
DEBUG: [delta.chef.client2] Sending heartbeat (sequence #1)
DEBUG: [delta.chef.client2] Sending heartbeat (sequence #1)
INFO: [delta.chef.client2] Sending heartbeat 1 (logging first 3)
INFO: [delta.chef.client2] Sending heartbeat 1 (logging first 3)
ERROR: [delta.chef.client2] No messages being received on command port in 4s. Possible encryption problem?
ERROR: [delta.chef.client2] No messages being received on command port in 4s. Possible encryption problem?
INFO: [delta.chef.client2] Reconfiguring client / reloading keys …
INFO: [delta.chef.client2] Reconfiguring client / reloading keys …
INFO: [delta.chef.client2] Retrieving configuration from https://delta.chef.server/organizations/delta//pushy/config/delta.chef.client2:
INFO: [delta.chef.client2] Retrieving configuration from https://delta.chef.server/organizations/delta//pushy/config/delta.chef.client2:


#2

@coderanger sorry for disturb, I have seen your answer in this question, it seems they are the same issue, can you explain more?

You answer:
http://stackoverflow.com/questions/25987894/why-does-knife-node-status-always-gives-unavailable-everytime

Here is the detail information i added in the github, but there was no response.
https://github.com/chef-cookbooks/push-jobs/issues/101

Hope you can answer, thank you!