[syslog-ng] About lost of messages after syslog-ng stop
Frank Abel Cancio Bello
frankabel at tesla.cujae.edu.cu
Wed Nov 14 23:15:15 CET 2007
Thanks a lot!
I was using syslog-ng 2.0.0, the version that come with the last stable
ubuntu server box (Gusty).
http://www.balabit.com/network-security/syslog-ng/opensource-logging-system/upgrades/changelogs/NEWS_syslog-ng_2.0.txt and in version 2.0.3 the “1024 byte limitation of internally generated messages” and “support for remembering the last posistion of file sources across restarts” issues are solved.
Now I will install the binary packages of the next ubuntu server box
(Hardy), that fortunately seem that can be installed in Gusty without
any other changes.
On Wed, 2007-11-14 at 08:42 +0100, Balazs Scheidler wrote:
> On Tue, 2007-11-13 at 14:18 -0500, Frank Abel Cancio Bello wrote:
> > Hi all!
> > What can I do to avoid that when I stop my syslog-ng client and apache
> > server still logging to its files not lost all those messages? I mean,
> > in the time that the syslog-ng client was not running, the apache
> > continue working and logging data, but when I start the syslog client it
> > don't send to the syslog-ng server the messages that apache logging when
> > it was stopped.
> > Here is part of what I think relevant of my configuration file:
> You did not include your syslog-ng version. 2.0.5 can remember the last
> position of the file accross restarts.
Participe en Universidad 2008.
11 al 15 de febrero del 2008.
Palacio de las Convenciones, Ciudad de la Habana, Cuba
More information about the syslog-ng