Hi Trevor, Not sure whether this is related, but your SYSLOG_LOGFILE is being rotated by an external script without letting om_file know about it, so this is definitely not what you should be doing. There is reopen() procedure provided by om_file, though I'd recommend doing the log rotation internally.
Let me know if you have made progress tracing down the leak. Regards, Botond On Tue, 25 Jun 2013 10:14:51 +0200 Botond Botyanszki <[email protected]> wrote: > Hi, > > I recommend to run it under valgrind, that should help us find the cause > faster. > For this you will need to install the -dbg package so that > debug info is available (or use a non stripped build), add "NoFreeOnExit > TRUE" to your nxlog.conf and run it via the following command: > valgrind --log-file=vg.log --tool=massif --pages-as-heap=yes nxlog -f > After it is stopped, a file called massif.out.xxx is created. Run > "ms_print massif.out.xxx >massif.txt" then please send me vg.log and > massif.txt. > > Regards, > Botond > > On Mon, 24 Jun 2013 16:26:06 +0000 (GMT) > Trevor <[email protected]> wrote: > > > Greetings- > > > > I'm experiencing a significant memory leak (multiple GB after a few days), > > and I'm wondering if my configuration is at fault. I'm running 2.4.1054 > > under Linux. > > > > My configuration is made up of ~20 included configuration files like the > > one below, each representing a separate log source, _with unique input > > ports, output ports and output files_. For each source (UDP, TCP), I > > write the log to disk and forward (TCP) to another log collector. > > > > Is anyone else running a config like this and experiencing memory leaks? > > Or is there something incorrect in my configuration? > > > > Regards, > > > > Trevor > > > > # > > # 514-syslog.conf > > # > > define SYSLOG_LOGFILE "/var/log/syslog.log" > > define SYSLOG_ROTATE %SYSLOG_ROTATE_TIME% > > define ROTATE_SYSLOG "/usr/local/bin/log_rotate.sh" > > > > define SYSLOG_IN_PORT 514 > > define SYSLOG_OUT_TCP_HOST %FORWARD_LOG_COLLECTOR% > > define SYSLOG_OUT_TCP_PORT 514 > > > > # > > # UDP, TCP inputs > > # > > <Input syslog_in_udp> > > Module im_udp > > Host 0.0.0.0 > > Port %SYSLOG_IN_PORT% > > </Input> > > > > <Input syslog_in_tcp> > > Module im_tcp > > Host 0.0.0.0 > > Port %SYSLOG_IN_PORT% > > </Input> > > > > # > > # file, TCP outputs > > # > > <Output syslog_out_file> > > Module om_file > > File %SYSLOG_LOGFILE% > > </Output> > > > > <Output syslog_out_tcp> > > Module om_tcp > > Host %SYSLOG_OUT_TCP_HOST% > > Port %SYSLOG_OUT_TCP_PORT% > > </Output> > > > > <Route syslog_route_file> > > Path syslog_in_udp, syslog_in_tcp => syslog_out_file > > </Route> > > > > <Processor syslog_net_buffer> > > Module pm_buffer > > Type Disk > > MaxSize %NET_BUFFER_SIZE_MAX% > > WarnLimit %NET_BUFFER_SIZE_WARN% > > Directory %NET_BUFFER_DIR% > > </Processor> > > > > <Route syslog_route_net> > > Path syslog_in_udp, syslog_in_tcp => syslog_net_buffer => > > syslog_out_tcp > > </Route> > > > > # > > # log rotation > > # > > <Extension syslog_rotate> > > Module xm_exec > > <Schedule> > > Every %SYSLOG_ROTATE% > > Exec exec_async(%ROTATE_SYSLOG%, %SYSLOG_LOGFILE%); > > </Schedule> > > </Extension> > > ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ nxlog-ce-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
