Hi, Regarding 6: If you have lines longer than 65k characters this is normal. It can be fixed by recompiling nxlog with a larger buffer. Otherwise make sure your file has lines properly terminated with LF or CRLF.
Regarding the delay, I don't have an idea. If this is not an environment issue and is reproducible on a standard windows/linux box, then please file a bug in the sourceforge trac. I also recommend to debug the issue using the statistical counters with the im_file module to see how it reads messages (e.g. print the EPS every second). Here is a similar example: http://nxlog.org/nxlog-docs/en/nxlog-reference-manual.html#idp5586560 Regards, Botond On Thu, 13 Jun 2013 18:55:57 +0300 Maxim Nikolaev <[email protected]> wrote: > Hi > > I'm using nxlog 2.4. I need to read big log file and forward them to > logstash. I encountered following problem: > > 1. Nxlog is configured to read lines from log file with im_file module. > 2. It send to logstash with om_ssl output. > > 3. I see that logs on logstash arrives with large delay - up to 3 hours. > 4. i've checked nxlog with om_file module to write log locally and found that > it really read log with delay. Log lines that I get in file are in delay for > 1-3 hours. > > 5. Logs that i need to read are big - total about 6GB day. > > 6. Also I get following error in nxlog.log: ERROR line is over the limit of > 65000, will be truncated. > > Thanks. ------------------------------------------------------------------------------ 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
