Hi Puppeteers! I''ve been using puppet for a little over a half year, and I''m very pleased with it. Until recently, I couldn''t get reporting to work, but after finding the culprit, it works just fine. Every day Puppet reports lines like the following: Tue Jul 31 04:37:49 +0200 2007 //debian_base_sarge/ boone.gehlarchitects.local/adm/admin_soa/usertype::adminuser[soa]/ remotefile[/home/soa/.ssh/authorized_keys]/File[/home/soa/.ssh/ authorized_keys]/source (err): Could not describe /dist/sshkeys/ soa.pub: end of file reached It''s different hosts, and on different times of the day and it''s kinda driving me crazy. Because I have "only" 32 hosts under the control of Puppet! And pupppetmaster runs on "mighty fine hardware" (Xeon 2.8Ghz based HP Blade server), so I don''t suspect that''s the culprit. But then, what is it? I was under the impression that Puppet ran on much larger installations than mine, and I plan to scale to at least ten times more. So I''m a bit surprised to see that 32 hosts is generating so many end-of-file-reached errors as they do. Anyone else out there experiencing the same problems? Do I really have to cut my puppetmaster in two halfs, one serving the config and the other the distfiles? Or will I be better off using Mongrel+Apache as frontend? -- Best regards/Med venlig hilsen Juri Rischel Jensen Fab:IT ApS Vesterbrogade 50 DK-1620 København Tlf: 70 202 407 / Fax: 33 313 640 www.fab-it.dk / juri@fab-it.dk
On Jul 31, 2007, at 4:42 AM, Juri Rischel Jensen wrote:> > Anyone else out there experiencing the same problems? Do I really > have to cut my puppetmaster in two halfs, one serving the config and > the other the distfiles? Or will I be better off using Mongrel+Apache > as frontend?I''ve seen that a few times, but I''ve mostly heard about it for reporting, rather than file serving. I would switch to mongrel, as it seems to have a much, much higher threshold for concurrent clients (~30 vs. ~7, from what I can tell). I think we''re pretty close to declaring that mongrel should be used for production and webrick only used for testing. I''m starting the switch from xmlrpc to rest today, which will hopefully make a big difference in performance, but we won''t know until I''m done. -- Football is a mistake. It combines the two worst elements of American life. Violence and committee meetings. -- George F. Will --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com
Luke Kanies <luke@madstop.com> writes:> On Jul 31, 2007, at 4:42 AM, Juri Rischel Jensen wrote:>> Anyone else out there experiencing the same problems? Do I really have >> to cut my puppetmaster in two halfs, one serving the config and the >> other the distfiles? Or will I be better off using Mongrel+Apache as >> frontend?> I''ve seen that a few times, but I''ve mostly heard about it for > reporting, rather than file serving.We get ten to twenty of these a day.> I would switch to mongrel, as it seems to have a much, much higher > threshold for concurrent clients (~30 vs. ~7, from what I can tell). I > think we''re pretty close to declaring that mongrel should be used for > production and webrick only used for testing.Yup, that''s the direction that we''re planning on going. -- Russ Allbery (rra@stanford.edu) <http://www.eyrie.org/~eagle/>