Re: Incorrect control files load technique causes "include files are nested too deeply" error

[Martin Pala]

Hello,

the limit prevents endless-loop include files configuration - it defines limit 
on the total number of included files rather then the nesting level (will fix 
the error message). The limit can be removed, but i think it is better to keep 
it to make sure that monit will detect the problem in the case of some 
configuration problem, which will create virtually  endless number of include 
files (for example if the include files are generated by some template system 
and the template system will become crazy).

If you need to rise the limit, you can modify the MAX_STACK_DEPTH in the 
src/l.l file and recompile Monit.

Regards,
Martin


On Aug 6, 2012, at 5:38 PM, Moshe Elisha <address@hidden> wrote:

> Hey,
> 
> I have a Monit with a main control file that contains the line:
> 
> include /opt/systems/sys_*/monitrc
> 
> Under /opt/systems I have a lot of "sys_XXX" directories - each containing a 
> simple monitrc file with a few processes but no further include.
> So basically, there are only two levels of control files - the main one and 
> all the sys_XXX files are under it.
> 
> When reaching 512 (MAX_STACK_DEPTH) "sys_XXX" directories, Monit fails to 
> load due to "include files are nested too deeply" error.
> Apparently, the sys_XXX control files are opened in recursion instead of one 
> by one as they are independent and they all have only one parent control file.
> 
> If, instead of the include sys* - I will add a line for each sys in the main 
> control file it will be OK but than I will have to manage the main control 
> file - instead of adding/deleting a directory.
> 
> This issue is very urgent for us as we counted and developed by this 
> structure and now, just before launch, we see that it does not work as we 
> expected.
> 
> Thanks.
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general