Bug #3482
closed
All nodes reports No Answer
Added by Dennis Cabooter over 11 years ago.
Updated over 11 years ago.
Description
All nodes reports say "No Answer". I think this is after upgrading Rudder to 2.5.1release. I'm not sure if this is the cause since I also migrated the server to a new host.
Some hosts are accepted in Rudder and then they are "forgotten" again. In the logs on that nodes I see "rudder-agent could not get an updated configuration from the policy server". But they are just accepted a few minutes before.
In other words; my whole Rudder Server installation is broken and I have no idea what to do. In the webapp logs I see a lot of "ERROR non-compliant-reports" messages.
I forgot to mention that, in the web interface, I see logs in Node Management > Node Details > Technical Logs, while all reports are in "No Answer" state.
Something is wrong with the keys as well:
Apr 17 15:16:19 rudderclient01 cf-serverd13349: Accepting connection from "1.2.3.4"
Apr 17 15:16:19 rudderclient01 cf-serverd13349: No public/private key pair exists, create one with cf-key
Apr 17 15:16:19 rudderclient01 cf-serverd13349: REFUSAL of request from connecting host: (SAUTH y 256 37 c)
Apr 17 15:16:00 rudderclient02 rudder901: BAD: Unspecified server refusal (see verbose server output)
Apr 17 15:16:00 rudderclient02 rudder901: !! Authentication dialogue with rudder.wintershall.nl failed
Ha. I'm afraid you've been hit by this bug http://www.rudder-project.org/redmine/issues/3462
Did you upgrade from 2.4 to 2.5.1 ?
If so, you have invalid data in your ldap directory, and the promises generated are invalid
Upgrading to 2.5.2 (which will be released soon) will solve this issue
If you didn't upgrade from 2.4.x to 2.5.1, we'll need more information to debug
Something is wrong with the keys as well:
Apr 17 15:16:19 rudderclient01 cf-serverd[13349]: Accepting connection from "1.2.3.4"
Apr 17 15:16:19 rudderclient01 cf-serverd[13349]: No public/private key pair exists, create one with cf-key
Apr 17 15:16:19 rudderclient01 cf-serverd[13349]: REFUSAL of request from connecting host: (SAUTH y 256 37 c)
Apr 17 15:16:00 rudderclient02 rudder[901]: BAD: Unspecified server refusal (see verbose server output)
Apr 17 15:16:00 rudderclient02 rudder[901]: !! Authentication dialogue with rudder.wintershall.nl failed
Dennis, maybe you could join us on IRC #rudder on freenode so that we can help you debug this problem ?
Thanks for your help. Upgrading to Rudder 2.5.2-release fixes the "no answer" problem totally. \0/
- Status changed from New to Rejected
It was a problem du to the upgrade. Upgrading to latest version solved it, so I'm rejecting this bug
Thank you Dennis !
Also available in: Atom
PDF
Updated by 
Updated by