rsyslog
Jul 05, 2009 - 08:38 AM
Professional Support
Custom written rsyslog.conf? Maintenance Contract?

rsyslog professional services



Donate!
Satisfied with rsyslog?

Donate and help keep
the project alive!

Rainer's Blog

Login




 


 Log in Problems?
 New User? Sign Up!

Online
There are 15 unlogged users and 0 registered users online.

You can log-in or register for a user account here.

Changelog for 3.11.6

Version 3.11.6 (rgerhards), 2008-02-27
  • bugfix: gssapi libraries were still linked to rsyslog core, what should no longer be necessary. Applied fix by Michael Biebl to solve this.
  • enabled imgssapi to be loaded side-by-side with imtcp
  • added InputGSSServerPermitPlainTCP config directive
  • split imgssapi source code somewhat from imtcp
  • bugfix: queue cancel cleanup handler could be called with invalid pointer if dequeue failed
  • bugfix: rsyslogd segfaulted on second SIGHUP tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=38
  • improved stability of queue engine
  • bugfix: queue disk file were not properly persisted when immediately after closing an output file rsyslog was stopped or huped (the new output file open must NOT have happend at that point) - this lead to a sparse and invalid queue file which could cause several problems to the engine (unpredictable results). This situation should have happened only in very rare cases. tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=40
  • bugfix: during queue shutdown, an assert invalidly triggered when the primary queue's DA worker was terminated while the DA queue's regular worker was still executing. This could result in a segfault during shutdown. tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=41
  • bugfix: queue properties sizeOnDisk, bytesRead were persisted to disk with wrong data type (long instead of int64) - could cause problems on 32 bit machines
  • bugfix: queue aborted when it was shut down, DA-enabled, DA mode was just initiated but not fully initialized (a race condition)
  • bugfix: imfile could abort under extreme stress conditions (when it was terminated before it could open all of its to be monitored files)
  • applied patch from varmojfekoj to fix an issue with compatibility mode and default module directories (many thanks!): I've also noticed a bug in the compatibility code; the problem is that options are parsed before configuration file so options which need a module to be loaded will currently ignore any $moddir directive. This can be fixed by moving legacyOptsHook() after config file parsing. (see the attached patch) This goes against the logical order of processing, but the legacy options are only few and it doesn't seem to be a problem.
  • bugfix: object property deserializer did not handle negative numbers

Send this story to someone  Printer-friendly page (1469 Reads)  
 rsyslog Sponsors
 
Functionality looking for Sponsors
rsyslog sponsoring
Click here for more information


 Search
 
Google

 Last Forum Posts
 · Re: Rhel 5.3 x64
I don't know about the various distros, but I know that a couple ...
· Re: Rhel 5.3 x64
I was having the same problem...after poking around,Looks like rh ...
· Re: TLS stops sending messages
It should be sufficient to remove the gtls driver directive. Then ...
· Re: fromhost property is not resolved wi ...
I think this is currently not possible, at least not without code ...
· fromhost property is not resolved with r ...
Hi,we are currently using udp for sending logs from rsyslog clien ...
· TLS stops sending messages
Hi folks,After a period of time, rsyslog either stops receiving ( ...
· Re: Rhel 5.3 x64
This looks like the software got installed to the wrong pathes an ...
· Re: stop remote messages being written t ...
Hi, I am having the same issue. Here are the contents of /etc/rs ...

:: Syndication: ::
Page created in 0.0812909603119 seconds.