Cronolog causing server failure

[Rob Brunskill <rbrunskill@xxxxxxx>]

I've got a server running over 200 virtual domains, logging to 
approximately 205 log files.

I started adding cronolog to some of the larger sites, in order to make log 
file management easier. It worked great for the first four domains. With 
the fifth domain, everything stopped working, producing a 403 error, and 
the following shows up in the error log:

(2)No such file or directory: file permissions deny server access:

Looking this up produced very limited results. It was typically people 
running into problems with their number of log files for their virtual 
domains.

However, I don't see why this error would be tied to changing a fifth log 
file over from normal logging to cronolog?

Has anyone had a similar problem and found a way around it?

Rob