file retrieval problems

Hi puppetiers,

recently I switched to using Mongrel webserver in effort to get rid of
those annoying "end of file reached" errors and increase performance. It
did the trick beautifully, but now a lot of my reports are plagued by
another error message:

---
 err: Could not call fileserver.describe: #<Errno::EPERM:
 Operation not permitted - connect(2)>
 
 //ns0/dns/File[/etc/namedb/master/db.example.com]/source (err):
 Could not describe /files/apps/named/ns0/master/db.example.com:
 Operation not permitted - connect(2)


 err: Could not call fileserver.list: #<Errno::EPERM:
 Operation not permitted - connect(2)>

 //ns0/dns/File[/etc/namedb/master/db.example.com] (err):
 Failed to generate additional resources during transaction:
 Operation not permitted - connect(2)
---

These particular examples are from a simple dns class that deploys around
40 master zone files (source a directory recursively) on FreeBSD
6.2-RELEASE and puppet 0.23.2 from source on both client and server.

Enabling the dns class on other machines results in the same behaviour.
Other classes also yeld this error, although much less frequently, but
they are also serving less files.

On ns0, the error appears around once a puppetd run (which is every 5
minutes). There are 12 servers managed in total with 2 puppetmasterd's.
Adding more puppetmasters seemed to do make no difference.

I inspected apache / proxy logs and tcpdump output, but could not find
any indication of failed connection attempts / connection resets. I read
the list discussion on fileserver scalability, but those guys are serving
way more files and there is no mention of the above problem anywhere in
sight.

I'd appreciate any pointers as to what could be causing this, anything
else to try etc, as right now Im quite baffled by this.


Thanks,

Jimbow

-- 
the neptune project
http://t-n-p.org