Hi Brett, Well, our cases are really quite different. For the shell commands that I happen to run, I have always had ">/dev/null 2>&1" on the command line even though I have not visited the link you mentioned, because I have encountered problems some time last year when I first experimented with cfengine without the redirection. That was when I was still running v2.2.1 and certainly the current set of configuration has been good for all the 2.2.1 and 2.2.2 hosts running for many months now. It was just recently that a teammate was required to set up a few new servers from scratch and he put 2.2.6 on them and we started to see all of these errors coming up not knowing why.
Even though our site setup is a bit complex with servers installed at different parts of the world thus necessitating two levels of cfservd for geographical locality concern, I think the configuration is pretty simple and straightforward overall with mostly copy (that was the primary reason I wanted to use cfengine in the first place). Well, to re-confirm I restarted cfexecd on one of the servers running 2.2.7 that showed MAXFD errors this afternoon. And right now, before I am going to bed, defunct children are seen again and the first MAXFD log appeared again about 4 hours after I did the restart. Weird? Regards, Bernard Chan. Brett Delle Grazie 提到: > Hi Mark & Bernard, > > I had a similar issue when I upgraded to 2.2.7 however in my case this was > due to: > (a) The RPM packager definitions leaked file descriptors: > Initially (leaks descriptors for some reason): > RPMInstallCommand = ( "/usr/bin/yum -y install %s" ) > RPMRemoveCommand = ( "/usr/bin/yum -t -y remove %s" ) > > Final (doesn't leak): > RPMInstallCommand = ( "/usr/bin/yum -d 0 -e 0 -y install %s 2<&-" ) > RPMRemoveCommand = ( "/usr/bin/yum -d 0 -e 0 -y remove %s 2<&-" ) > > (b) Shellcommands and process restarts: > I followed the advice of > http://www.cfwiki.org/cfwiki/index.php/Hung_Shell_Command > > and this resolved my issues. > > In my case, all of my file descriptors were due to the Yum command. > > I'm using RHEL 5.2 on AMD64 > > Thanks, > > Best regards, > > Brett > > -----Original Message----- > From: Bernard Chan [mailto:[EMAIL PROTECTED] > Sent: Monday, June 16, 2008 3:21 AM > To: Mark Burgess > Cc: help-cfengine; bug-cfengine > Subject: Re: Version 2.2.7 of cfengine released > > > Dear Mark and everybody on the list, > > I have upgraded our v2.2.6 systems to v2.2.7 but still got the MAXFD errors. > Would anyone help? > > I found these in /var/log/messages. > > Jun 16 00:30:47 asterisk102-32bit cfexecd[3361]: Couldn't open pipe to > command /var/cfengine/bin/cfagent -Dfrom_cfexecd:scheduled_run Jun 16 > 00:30:47 asterisk102-32bit cfexecd[3361]: cfpopen: Illegal seek Jun 16 > 01:00:47 asterisk102-32bit cfexecd[3361]: File descriptor 145 of child 30069 > higher than MAXFD, check for defunct children Jun 16 01:00:47 > asterisk102-32bit cfexecd[3361]: Couldn't open pipe to command > /var/cfengine/bin/cfagent -Dfrom_cfexecd:scheduled_run Jun 16 01:00:47 > asterisk102-32bit cfexecd[3361]: cfpopen: Illegal seek Jun 16 01:30:48 > asterisk102-32bit cfexecd[3361]: File descriptor 146 of child 31065 higher > than MAXFD, check for defunct children Jun 16 01:30:48 asterisk102-32bit > cfexecd[3361]: Couldn't open pipe to command /var/cfengine/bin/cfagent > -Dfrom_cfexecd:scheduled_run Jun 16 01:30:48 asterisk102-32bit cfexecd[3361]: > cfpopen: Illegal seek Jun 16 02:00:48 asterisk102-32bit cfexecd[3361]: File > descriptor 147 of child 31994 higher than MAXFD, check for defunct children > Jun 16 02:00:48 asterisk102-32bit cfexecd[3361]: Couldn't open pipe to > command /var/cfengine/bin/cfagent -Dfrom_cfexecd:scheduled_run Jun 16 > 02:00:48 asterisk102-32bit cfexecd[3361]: cfpopen: Illegal seek > > and found the defunct children in ps -efww. > > The system being deployed is Linux i686. > > Regards, > Bernard Chan. > > 於 三，2008-06-11 於 18:55 +0200，Mark Burgess 提到： > >> This is a minor bugfix release with no new features. It corrects a >> threading error in cfexecd which caused hanging file descriptors. >> >> MD5 (cfengine-2.2.7.tar.gz)= 8ee6d6d58ba6eca649c199c6c7074a67 >> SHA1(cfengine-2.2.7.tar.gz)= c96fd0c824a1b25fc1fd4720663cb1da89ad6025 >> >> The aim is that this version should remain stable for the foreseeable >> future. Hopefully the next release will be 3.0.0 >> >> > > > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > _______________________________________________ Bug-cfengine mailing list [email protected] https://cfengine.org/mailman/listinfo/bug-cfengine
