search

chef-boneyard / opscode-pushy-server

Chef Push Jobs Server
https://docs.chef.io/push_jobs.html
Apache License 2.0
16 stars 10 forks source link

chef push jobs not wokring #212

Closed AnamikaN closed 4 years ago

AnamikaN commented 4 years ago

I am trying to configure chef push jobs. Setup from my side is done. When I am trying knife node status nodename , it is showing unavailable.

Our architecture- We have our chef clients in Data Centers. We have our chef server in aws.

from DC host, i can telnet to aws server on port 10000 and 10002.

Any thoughts on this issue?

below are the logs from client node-

INFO: [host_name] Setting reconfigure deadline to 2020-02-27 17:47:38 -0800 ERROR: [host_name] No messages being received on command port in 4s. Possible encryption problem? INFO: [host_name] Reconfiguring client / reloading keys ... INFO: [host_name] Retrieving configuration from https://chef.messagehub.rd.em.io/organizations/mh//pushy/config/host_name: ... INFO: [host_name] Stopping command / server heartbeat receive thread and destroying sockets ... INFO: [host_name] Resolved em-chef-s-chefpjel-1hsxx5wqxjnsd-826791513.us-west-2.elb.amazonaws.com to '35.164.90.15' and 1 others INFO: [host_name] Starting ZMQ version {:major=>4, :minor=>0, :patch=>7} INFO: [host_name] Listening for server heartbeat at tcp://em-chef-s-chefpjel-1hsxx5wqxjnsd-826791513.us-west-2.elb.amazonaws.com:10000 INFO: [host_name] Connecting to command channel at tcp://em-chef-s-chefpjel-1hsxx5wqxjnsd-826791513.us-west-2.elb.amazonaws.com:10002 INFO: [host_name] Stopping heartbeat / offline detection thread ... INFO: [host_name] Starting command / server heartbeat receive thread ... INFO: [host_name] Considering server online, and starting to heartbeat INFO: [host_name] Stopping reconfigure thread ... INFO: [host_name] Starting heartbeat / offline detection thread on interval 10.0 ... INFO: [host_name] Reconfigured client. INFO: [host_name] Forced GC; Stat count changed 1 INFO: [host_name] Starting reconfigure thread. Will reconfigure / reload keys after 3600 seconds, less up to splay 0.1. INFO: [host_name] Setting reconfigure deadline to 2020-02-27 17:45:24 -0800 ERROR: [host_name] No messages being received on command port in 4s. Possible encryption problem? INFO: [host_name] Reconfiguring client / reloading keys ... INFO: [host_name] Retrieving configuration from https://chef.messagehub.rd.em.io/organizations/mh//pushy/config/host_name: ... INFO: [host_name] Stopping command / server heartbeat receive thread and destroying sockets ... INFO: [host_name] Resolved em-chef-s-chefpjel-1hsxx5wqxjnsd-826791513.us-west-2.elb.amazonaws.com to '35.164.90.15' and 1 others INFO: [host_name] Starting ZMQ version {:major=>4, :minor=>0, :patch=>7} INFO: [host_name] Listening for server heartbeat at tcp://em-chef-s-chefpjel-1hsxx5wqxjnsd-826791513.us-west-2.elb.amazonaws.com:10000 INFO: [host_name] Connecting to command channel at tcp://em-chef-s-chefpjel-1hsxx5wqxjnsd-826791513.us-west-2.elb.amazonaws.com:10002 INFO: [host_name] Stopping heartbeat / offline detection thread ... INFO: [host_name] Starting command / server heartbeat receive thread ... INFO: [host_name] Considering server online, and starting to heartbeat INFO: [host_name] Stopping reconfigure thread ... INFO: [host_name] Starting heartbeat / offline detection thread on interval 10.0 ... INFO: [host_name] Reconfigured client. INFO: [host_name] Starting reconfigure thread. Will reconfigure / reload keys after 3600 seconds, less up to splay 0.1. INFO: [host_name] Forced GC; Stat count changed 1 INFO: [host_name] Setting reconfigure deadline to 2020-02-27 17:47:17 -0800

AnamikaN commented 4 years ago

My push job was trying to connect to Load balancer, i changed it to bootstrap id and it worked.