Michael, it seems to be cf-agent's output, so you couldn't catch it just inspecting processes. Perhaps, it's wise to check and probably increase ulimits for user which runs cf-agent in terms of maximum open files. The global file descriptors limits also may require increasing.
2010/9/17 Michael Potter <mega...@gmail.com>: > Hi > Recently noticed this error crop up on one of our production servers. Never > seen it happen anywhere else, including other test and production machines: > File descriptor 27 of child 28560 higher than MAX_FD, check for defunct > children > File descriptor 27 of child higher than MAX_FD, check for defunct children > File descriptor 22 of child 28562 higher than MAX_FD, check for defunct > children > File descriptor 22 of child higher than MAX_FD, check for defunct children > File descriptor 22 of child 28563 higher than MAX_FD, check for defunct > children > File descriptor 22 of child higher than MAX_FD, check for defunct children > File descriptor 22 of child 28564 higher than MAX_FD, check for defunct > children > File descriptor 22 of child higher than MAX_FD, check for defunct children > Using 3.0.5p1 on Solaris10/SPARC. > There does not appear to be any defunct processes attached to cf-execd: > $ ps -ef | grep cf- > root 9727 591 0 Sep 14 ? 0:33 > /export/rt/cfengine/bin/cf-serverd > root 9897 591 0 Sep 14 ? 0:49 > /export/rt/cfengine/bin/cf-execd > $ ptree 9897 > 591 zsched > 9897 /export/rt/cfengine/bin/cf-execd > Anyone come across anything like this before? > Cheers > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine > > -- SY, Seva Gluschenko. _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
