[ossec-list] Re: Monthly Summart Report for Ossec

2009-06-02 Thread ddp
Looks like you have too many logs on a machine that isn't quite big enough. reportd (recent ossec snapshot) is working on OpenBSD 4.5 (recent snapshot), and an old Centos box for me. How big is your log directory? How much ram does the server have? dan On Tue, Jun 2, 2009 at 8:34 AM, Derek J. Mo

[ossec-list] Re: Monthly Summart Report for Ossec

2009-06-02 Thread Derek J. Morris
server has 1.5gb of physical RAM, log directory is: 190MB. -Derek > > Looks like you have too many logs on a machine that isn't quite big enough. > reportd (recent ossec snapshot) is working on OpenBSD 4.5 (recent snapshot), > and an old Centos box for me. > > How big is your log directory? How

[ossec-list] Re: Monthly Summart Report for Ossec

2009-06-02 Thread ddp
Does the user account being used to run the reports have any limits on the amount of ram it can use? "ulimit -a" should provide that answer if you're using bash (or similar shell). Can you try a smaller subset of logs to see if that works? I just tried to run a report for 230MB and got the same er

[ossec-list] Re: Monthly Summart Report for Ossec

2009-06-02 Thread Derek J. Morris
Ran it on an old chunk only 15MB and worked. So I guess there is a limit on this reporting then huh? My ulimit -a output is: ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f)