push-jobs-cookbook
push-jobs-cookbook copied to clipboard
No messages being received on command port in 4s. Possible encryption problem
Cookbook version
3.2.2
Chef-client version
12.13.37
Chef-server version
2.1.0
Platform Details
Both Push Client and Server on Centos 6.5
Scenario:
After i uploaded cookbook to my chef-server, and use chef-client command to configure push job client on my machine, but the node status by searching from the server always shows unavailable, here is the log from /var/log/chef-push-jobs-client/current:
2016-09-29_08:57:36.73327 INFO: [delta.chef.client2] Starting reconfigure thread. Will reconfigure / reload keys after 3600 seconds, less up to splay 0.1. 2016-09-29_08:57:36.73332 INFO: [delta.chef.client2] Starting heartbeat / offline detection thread on interval 10.0 ... 2016-09-29_08:57:40.75176 ERROR: [delta.chef.client2] No messages being received on command port in 4s. Possible encryption problem? 2016-09-29_08:57:40.75203 INFO: [delta.chef.client2] Reconfiguring client / reloading keys ... 2016-09-29_08:57:40.75220 INFO: [delta.chef.client2] Retrieving configuration from https://delta.chef.server/organizations/delta//pushy/config/delta.chef.client2: ... 2016-09-29_08:57:41.75311 INFO: [delta.chef.client2] Stopping command / server heartbeat receive thread and destroying sockets ... 2016-09-29_08:57:41.87677 INFO: [delta.chef.client2] Resolved delta.chef.server to '172.22.27.61' and 2 others
Here is the detail of log: https://gist.github.com/yanxinyuan/91677e9b85eb43c381123f0b05453fa8
Steps to Reproduce:
- First, upload cookbook in server by command: knife cookbook upload push-jobs --force
- Second, configure push-job client by command in client machine: chef-client
Expected Result:
When execute 'knife node status' command, the node status is available.
Actual Result:
When execute 'knife node client' command, i can view the node.
When execute 'knife node status' command, i can't view the node.
When execute 'knife node status