Hi, Can you try lowering a the file count i.e. test with 8000, 7000, 6000, etc until it starts properly. Then check the memory usage of the process to get an idea about the limit.
Regards, Botond On Wed, 05 Feb 2014 14:58:42 +0100 flor...@peterschmitt.fr wrote: > I've tried with the latest libapr-1.5.0 but no different behavior. > > Le 2014-02-05 11:12, flor...@peterschmitt.fr a écrit : > > I just test with the very latest version. > > > > I've created 10000 files with 1000 lines each. > > > > > > With the default MALLOCOPTIONS, the agent crashes with: > > > > ERROR [alloc.c:18/abort_func()] memory pool allocation error;Not enough > > space > > > > But with an export MALLOCOPTIONS=pool:1024M: > > > > ERROR [alloc.c:18/abort_func()] memory pool allocation error;Not enough > > space > > ERROR [im_file.c:976/im_file_check_new()] > > -;[im_file.c:908/im_file_glob_dir()] -;[alloc.c:18/abort_func()] memory > > pool allocation error;Not enough space > > > > The agent doesn't stop but is looping with these messages: > > > > 2014-02-05 10:47:59 DEBUG [out_logstash] no poll events, pollset_poll > > timed out > > 2014-02-05 10:47:59 DEBUG nx_event_to_jobqueue: POLL (out_logstash) > > 2014-02-05 10:47:59 DEBUG event added to jobqueue > > 2014-02-05 10:47:59 DEBUG worker 2 processing event 0x2023ccc0 > > 2014-02-05 10:47:59 DEBUG PROCESS_EVENT: POLL (out_logstash) > > 2014-02-05 10:47:59 DEBUG nx_module_pollset_poll: out_logstash > > 2014-02-05 10:47:59 DEBUG worker 1 got signal for new job > > 2014-02-05 10:47:59 DEBUG worker 1 got no event to process > > 2014-02-05 10:47:59 DEBUG worker 1 waiting for new event > > 2014-02-05 10:47:59 DEBUG no events or no future events, event thread > > sleeping in condwait > > > > Well, just see what gives GDB without the MALLOC tuning: > > > > 2014-02-05 11:00:24 DEBUG opening /appli01/devidw/log/747.log > > memory pool allocation error > > Not enough space > > checking '7470.log' against wildcard '*.log': > > '7470.log' matches wildcard '*.log' > > adding file: /appli01/devidw/log/7470.log > > [New Thread 258] > > [New Thread 515] > > [New Thread 772] > > [New Thread 1029] > > > > Program received signal SIGSEGV, Segmentation fault. > > [Switching to Thread 1] > > 0x00000000 in ?? () > > > > I guess this is no more helpful, I'm searching to build nxlog with > > debug > > symbols, but is there anything you can see from that? > > ------------------------------------------------------------------------------ > Managing the Performance of Cloud-Based Applications > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. > Read the Whitepaper. > http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk > _______________________________________________ > nxlog-ce-users mailing list > nxlog-ce-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk _______________________________________________ nxlog-ce-users mailing list nxlog-ce-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
