Arnau, Please don't be offended by my response, as you requested we not be offended by your post.
I've watched a lot of your posts to the list, and the behavior I'm observing is when you run into errors, you don't seem to step back and try to take the time to understand them. Instead, it appears you do the following: 1) Immediately post a message to the list. 2) Freak out because nobody responded within 5 minutes. 3) Flail around trying things, seemingly at random, until something *seems* to work because it makes the specific error change/go away. 4) Repeat. So, if I were to offer you some ideas for how to proceed, they would be: 1) Set all the stuff you've made to this point aside. Keep it around to use as reference. 3) Pick 3 machines to use as an environment for learning puppet. 4) Ensure that Puppet is *completely* removed from these machines. It would be optimal if they were totally clean machines. * Puppet is still pre-1.0 software. The upgrade path hasn't been perfectly clean and, to complicate things, packaging has been fairly inconsistent. There are some artifacts that are in older versions which will utterly break newer versions in disorienting ways. 5) Install the latest stable version of Puppet (0.24.7 as I write). Choose one machine to act as puppetmaster, and (if it is a separate package for your environment) install puppetmaster on that machine. 6) Pick one service. Create a module for it. 7) When you encounter a problem, stop. Walk away entirely for ten minutes. Come back to it and see if you can figure out what the root cause of the problem is. Some basic troubleshooting steps for Puppet: * Re-start your puppetmaster and watch the logs. Often a syntax error in your manifests will cause the puppetmaster to ignore them and use the old cached configurations. When you restart, if you are watching the logs, you'll catch the syntax error and you can fix it. * Utilize --debug --no-daemonize on both client and server -- this is one of your biggest complaints, and it is entirely caused by having used old versions and leaving old broken config files around. You should not have a 'puppetd.conf' or a 'puppetmasterd.conf', you should be using 'puppet.conf' * Try out --parse-only * Comment out the sections of your manifest that you added since things ran perfectly. Uncomment one resource at a time. I think if you step back and start from a reasonably clean slate you will have a more positive experience. Regards, Paul Lathrop On Wed, Feb 11, 2009 at 10:25 AM, Arnau Bria <arnaub...@pic.es> wrote: > > Hi all, > > I'm facing many problems for last days with my puppet server/client. > Those who read mail list may know that. > > > I'm not sure if it's just my and my poor knowledge on puppet (I must > say in my defense that I have read many wiki docs and I have bough the > book, ok, it's not enough, if I'm a bad sysadmin I can read a complete > library and know anything...) but seems that every doc describes one > behave and puppet does an other. Please, don't feel offended > after/before reading this mail. I really appreciate the developers > effort, and all the help I got from this list, but I'm getting crazy > with puppet. > > > I started with a simple scenario, a couple of nodes with a server, and > few classes, all worked fine... But one day I faced first problem: > > err: Could not retrieve catalog: Could not parse for environment production > > after reading a lot, checking my conf one time and other, and other, > and other I realized that I removed puppetmasterd link > from /etc/puppet/ (puppetmaster complained about having two files with > same conf) and the solution was creating it again, ignoring the log > error... > > After that, I upgraded to a newer version, not latest, where I found a > installation bug about creating $vardir directory... I could solve it > by creating it by hand, but I faced some other problems like that > version was not able to run puppetmasterd in debug mode and not sending > the process to background... So, I have to upgrade again, cause I think > this feature is basic for debugging... OH! and I found that each > section of puppetd needs its own variables... $vardir was default value > for puppetmasterd if I did not specify them explicity. > > So, now I'm at version 0.24.7, from epel, and all seemed to work fine > again (complete puppetview report, many classses with deps, etc...) > > until when? until I tried to configure mongrel (ok, it's mongrel, not > puppet itself), but balancing did not work, at least in my case > (it did balance, but was not able to server catalog to hosts). I tried > to reinstall 40 host at once and I saw puppetmasterd being not able > to support that... 100 apache processes...) and it's only 40 nodes (ok, > someone is managing lots of nodes, someone told me that they have more > than 100), my question is: did you do it with "regular" versions? did > you find many problems/bugs? did you do at once? > I thought, balancing is not working, maybe is a proxy/mongrel > missconfig, I'll go to mongrel list and ask them... but when I ran > puppetca w puppet/mongrel I cannot clean certs, so puppetca does not > work, I must locate certs and remove them by hand... > > So I had to reisntall nodes from 10 to 10, and worked fine... until > when? until today, yes, I faced an old known problem: > > Could not retrieve catalog: Could not parse for environment production: No > file(s) found for import of > > *this time the link did not solve the problem... > > Ok, you'll say: "you have changed many things..." but no, > I haven't! I have all my code under subversion, I go back to a > "valid" (yesterday's) revision, I check my changes and I have only > added a couple of packages types... but, anyway, I go back there, and > what happens now? > > [r...@gridinstall tmp]# /usr/bin/ruby /usr/sbin/puppetmasterd > --manifest=/etc/puppet/manifests/site.pp --no-daemonize --debug > [r...@gridinstall tmp]# !ps > ps -ef|grep puppet > puppet 14551 1 0 19:05 ? 00:00:00 /usr/bin/ruby > /usr/sbin/puppetmasterd --manifest=/etc/puppet/manifests/site.pp > --no-daemonize --debug > root 14555 2750 0 19:06 pts/0 00:00:00 grep puppet > > --no-daeemonize is not working again!!! > > So, do you understand what am I felling? I mean, it's only me? am I > alone eith many problems? > I've checked reductivelabs prizes for support & implementation > services, maybe this is the solution, maybe not... I'll ask my boss for > money to attend belgium's training course... I don't know what else > do... but now I feel that I was using a good & easy software that I was > able to learn and deploy in my work place fast, but when I tried to do > some complex conf, I faced so many problems that I'm afraid of its > behaviour... > > > Anyway, again, thanks to developer and people who helped me in list, > and thanks to those who are still reading this post :-) > I just wanted to share my recent experience with puppet... I hope in > future all my problems will disappear. > > Cheers, > Arnau > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
