No messages being received on command port in 4s. Possible encryption problem

[yanxinyuan]

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:

1. First, upload cookbook in server by command: knife cookbook upload push-jobs --force
2. 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 ', it shows unavailable.
When execute 'chef-client' in client machine, the result shows https://gist.github.com/yanxinyuan/5545ead689a20151443e70ac55498a4a

[laxmanrapolu]

What is the solution for this issue. I have been facing the same issue for last 2 days.

[iennae]

Was this a new install or an upgrade of Push Server and Push Client?

[dmore]

I have the same problem. I think is due to having chef on a different path to the default one.

[rajeshpodipati]

I am still facing this issue. Could anyone give the solution to fix this.

ERROR: [OSPatchMgmt] No messages being received on command port in 4s. Possible encryption problem?

INFO: [OSPatchMgmt] Connecting to command channel at tcp://ip-10-10-2-14.ec2.internal:10002
INFO: [OSPatchMgmt] Stopping heartbeat / offline detection thread ...
INFO: [OSPatchMgmt] Considering server online, and starting to heartbeat
INFO: [OSPatchMgmt] Stopping reconfigure thread ...
INFO: [OSPatchMgmt] Reconfigured client.
INFO: [OSPatchMgmt] Starting reconfigure thread. Will reconfigure / reload keys after 3600 seconds, less up to splay 0.1.
INFO: [OSPatchMgmt] Starting heartbeat / offline detection thread on interval 10.0 ...
INFO: [OSPatchMgmt] Starting command / server heartbeat receive thread ...
INFO: [OSPatchMgmt] Forced GC; Stat count changed 1
INFO: [OSPatchMgmt] Setting reconfigure deadline to 2018-05-07 03:01:06 +0000
ERROR: [OSPatchMgmt] No messages being received on command port in 4s. Possible encryption problem?
INFO: [OSPatchMgmt] Reconfiguring client / reloading keys ...
INFO: [OSPatchMgmt] Retrieving configuration from https://10.10.2.14/organizations/devops//pushy/config/OSPatchMgmt: ...
INFO: [OSPatchMgmt] Stopping command / server heartbeat receive thread and destroying sockets ...
INFO: [OSPatchMgmt] Resolved ip-10-10-2-14.ec2.internal to '10.10.2.14' and 0 others
INFO: [OSPatchMgmt] Starting ZMQ version {:major=>4, :minor=>0, :patch=>7}
INFO: [OSPatchMgmt] Listening for server heartbeat at tcp://ip-10-10-2-14.ec2.internal:10000
INFO: [OSPatchMgmt] Connecting to command channel at tcp://ip-10-10-2-14.ec2.internal:10002
INFO: [OSPatchMgmt] Stopping heartbeat / offline detection thread ...
INFO: [OSPatchMgmt] Considering server online, and starting to heartbeat
INFO: [OSPatchMgmt] Stopping reconfigure thread ...
INFO: [OSPatchMgmt] Reconfigured client.
INFO: [OSPatchMgmt] Forced GC; Stat count changed 1
INFO: [OSPatchMgmt] Starting reconfigure thread. Will reconfigure / reload keys after 3600 seconds, less up to splay 0.1.
INFO: [OSPatchMgmt] Starting command / server heartbeat receive thread ...
INFO: [OSPatchMgmt] Starting heartbeat / offline detection thread on interval 10.0 ...
INFO: [OSPatchMgmt] Setting reconfigure deadline to 2018-05-07 03:01:41 +0000
ERROR: [OSPatchMgmt] No messages being received on command port in 4s. Possible encryption problem?
INFO: [OSPatchMgmt] Reconfiguring client / reloading keys ...
@chef-supermarket @master-chef @dmore @iennae @yanxinyuan @laxmanrapolu @chefsalim

[AnamikaN]

is this issue resolved? what is the solution?

[AnamikaN]

Was this a new install or an upgrade of Push Server and Push Client?

For me, its a new install.

[raghureddy45]

any update on this?