Bug #2208
puppet/puppetd do not work with the server option provided on the comand line
| Status: | Needs more information | Start: | 04/28/2009 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Affected version: | 0.24.7 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
puppetd —server puppet.example.com fails to connect to puppet.example.com
rpm -q puppet
puppet-0.24.7-1
strace -o /tmp/log puppet —noop —debug —trace —server puppet.directi.com is attached.
Facter:
facter
architecture => x86_64 domain => mailhostingserver.com facterversion => 1.3.8 fqdn => mailbox-us-s-10.mailhostingserver.com hardwareisa => x86_64 hardwaremodel => x86_64 hostname => mailbox-us-s-10 id => root ipaddress => 74.53.139.50 ipaddress_eth0 => 74.53.139.50 kernel => Linux kernelrelease => 2.6.9-67.0.4.ELsmp lsbdistcodename => NahantUpdate6 lsbdistdescription => Red Hat Enterprise Linux ES release 4 (Nahant Update 6) lsbdistid => RedHatEnterpriseES lsbdistrelease => 4 lsbrelease => :core-3.0-amd64:core-3.0-noarch:graphics-3.0-amd64:graphics-3.0-noarch macaddress => 00:19:B9:C4:6C:8D macaddress_eth0 => 00:19:B9:C4:6C:8D memoryfree => 970.09 MB memorysize => 1.96 GB operatingsystem => RedHat operatingsystemrelease => 4 processor0 => Intel® Xeon® CPU 5130 @ 2.00GHz processor1 => Intel® Xeon® CPU 5130 @ 2.00GHz processor2 => Intel® Xeon® CPU 5130 @ 2.00GHz processor3 => Intel® Xeon® CPU 5130 @ 2.00GHz processorcount => 4 ps => ps -ef puppetversion => 0.24.7 rubysitedir => /usr/lib/ruby/site_ruby/1.8 rubyversion => 1.8.6 sshdsakey => AAAAB3NzaC1kc3MAAACBAKTeeybjq/0hRLvM3tJ/1LY5x6Llo+Foez9QJ+5bCy/1mqafPW9nSuQ8X3WglbUq9ejtVBkuvKRljR5qmxQfock/5DXCkO3Ot44ye+Nt6jH9b3318127krn4X6mP2Tpli0QkI09Tq7r5HhWtgFZMUPBxXKgC2fn3IyWeD//6u60rAAAAFQDQ0YkgMD8EH4drP5oCHD1PyzFYnQAAAIAgt6Td0p/MJjnDbdlXv5XoRNPLiXD5iflkdErzPNx+UWYAsjoFbCC4P1HYT/oc8jqJotr+ac3hBAmcW4ZjSxp6HGgoKNBlUKwTdvYKgrlBtNRmVe9clC+YwPBoJlPpfh1LPKx4N87hgYECAxUXFop3XFDTOxY62R3uWwYeHeJgOQAAAIEAhKMzvqbwEpbVOinMieJjatViGNpcTJqIHQBV6z2z1L18R7QFaF7oEkIeVb6dic/pDpbuVc/h1ZC5LcNIRtFAIQJpW3vqBZiX4Om61649YkU0mmvXlIJc4LUF5M8lVjzIKTbFVUcbyQjd6iw203YVRJpEw43zUPnBH+ZXg22HRek= sshrsakey => AAAAB3NzaC1yc2EAAAABIwAAAIEAy1PbcyhRx+VZ4+Db+2wS568++JK/dsTDWl0U/Ez+ZAx8hd6ukESsKlgPeOHDdI7btEIbngv873V2zQDxzMNINlNE9/zpWmPwr7KtDaDAmVgLajMqRR/x2ks3BTrgbrXFjIZ3OB5TeNBW3jAwkjdmImsf5rNdWpEyrbVJW2DpWUc= swapfree => 1.92 GB swapsize => 1.95 GB uniqueid => 354a328b
History
Updated by Luke Kanies over 1 year ago
- Status changed from Unreviewed to Needs more information
I’m highly skeptical that this isn’t working – I use it constantly.
I don’t see anything in the log about where the server is being contacted. Can you include just the log snippet that shows the server being contacted?
Updated by devdas - over 1 year ago
I have no idea about why it does not connect (or try to). This behaviour is fairly random as well, so I have no idea of a specific configuration to be able to reproduce it. If it affects a machine, it is consistent for the machine though.