Search Results for: queue

Version 5.3.4 [DEVEL] (rgerhards), 2009-11-04

• added the ability to create custom message parsers
• added $RulesetParser config directive that permits to bind specific parsers to specific rulesets
• added omruleset output module, which provides great flexibility in action processing. THIS IS A VERY IMPORTANT ADDITION, see its doc for why.
• added the capability to have ruleset-specific main message queues
  This offers considerable additional flexibility AND superior performance (in cases where multiple inputs now can avoid lock contention)

• bugfix: correct default for escape (‘#’) character restored
  This was accidently changed to ‘\\’, thanks to David Lang for reporting

• bugfix(testbench): testcase did not properly wait for rsyslogd shutdown thus some unpredictable behavior and a false negative test result could occur.
  

Version 5.3.3 [DEVEL] (rgerhards), 2009-10-27

• simplified and thus speeded up the queue engine, also fixed some potential race conditions (in very unusual shutdown conditions) along the way. The threading model has seriously changes, so there may be some regressions.
• enhanced test environment (inlcuding testbench): support for enhancing probability of memory addressing failure by using non-NULL default value for malloced memory (optional, only if requested by configure option). This helps to track down some otherwise undetected issues within the testbench.
• bugfix: potential abort if inputname property was not set primarily a problem of imdiag
• bugfix: message processing states were not set correctly in all cases however, this had no negative effect, as the message processing state was not evaluated when a batch was deleted, and that was the only case where the state could be wrong.
  

Version 5.3.2 [DEVEL] (rgerhards), 2009-10-21

• enhanced omfile to support transactional interface. This will increase performance in many cases.
• added multi-ruleset support to imudp
• re-enabled input thread termination handling that does avoid thread cancellation where possible. This provides a more reliable mode of rsyslogd termination (canceling threads my result in not properly freed resouces and potential later hangs, even though we perform proper cancel handling in our code). This is part of an effort to reduce thread cancellation as much as possible in rsyslog.
  NOTE: the code previously written code for this functionality had a subtle race condition. The new code solves that.

• enhanced immark to support non-cancel input module termination
• improved imudp so that epoll can be used in more environments, fixed potential compile time problem if EPOLL_CLOEXEC is not available.
• some cleanup/slight improvement:
  • changed imuxsock to no longer use deprecated submitAndParseMsg() IF
  • changed submitAndParseMsg() interface to be a wrapper around the new way of message creation/submission. This enables older plugins to be used together with the new interface. The removal also enables us to drop a lot of duplicate code, reducing complexity and increasing maintainability.
• bugfix: segfault when starting up with an invalid .qi file for a disk queue
  Failed for both pure disk as well as DA queues. Now, we emit an error message and disable disk queueing facility.

• bugfix: potential segfault on messages with empty MSG part. This was a recently introduced regression.
• bugfix: debug string larger than 1K were improperly displayed. Max size is now 32K, and if a string is even longer it is meaningfully truncated.
  

Version 5.1.3 [DEVEL] (rgerhards), 2009-07-28

• architecture change: queue now always has at least one worker thread if not running in direct mode. Previous versions could run without any active workers. This simplifies the code at a very small expense. See v5 compatibility note document for more in-depth discussion.
• enhance: UDP spoofing supported via new output module omudpspoof. See the omudpspoof documentation for details and samples
• bugfix: message could be truncated after TAG, often when forwarding. This was a result of an internal processing error if maximum field sizes had been specified in the property replacer.
• bugfix: minor static memory leak while reading configuration did NOT leak based on message volume
• internal: added ability to terminate input modules not via pthread_cancel but an alternate approach via pthread_kill. This is somewhat safer as we do not need to think about the cancel-safeness of all libraries we use. However, not all inputs can easily supported, so this now is a feature that can be requested by the input module (the most important ones request it).
  

Version 4.5.1 [DEVEL] (rgerhards), 2009-07-15

• CONFIG CHANGE: $HUPisRestart default is now “off”. We are doing this to support removal of restart-type HUP in v5.
• bugfix: fromhost-ip was sometimes truncated
• bugfix: potential segfault when zip-compressed syslog records were received (double free)
• bugfix: properties inputname, fromhost, fromhost-ip, msg were lost when working with disk queues
• performance enhancement: much faster, up to twice as fast (depending on configuration)
• bugfix: abort condition when RecvFrom was not set and message reduction was on. Happend e.g. with imuxsock.
• added $klogConsoleLogLevel directive which permits to set a new console log level while rsyslog is active
• bugfix: message could be truncated after TAG, often when forwarding This was a result of an internal processing error if maximum field sizes had been specified in the property replacer.
• added ability for the TCP output action to “rebind” its send socket after sending n messages (actually, it re-opens the connection, the name is used because this is a concept very similiar to $ActionUDPRebindInterval). New config directive actionSendTCPRebindInterval added for the purpose. By default, rebinding is disabled. This is considered useful for load balancers.
• testbench improvements

Version 5.1.2 [DEVEL] (rgerhards), 2009-07-08

• bugfix: properties inputname, fromhost, fromhost-ip, msg were lost when working with disk queues
• some performance enhancements
• bugfix: abort condition when RecvFrom was not set and message reduction was on. Happend e.g. with imuxsock.
• added $klogConsoleLogLevel directive which permits to set a new console log level while rsyslog is active
• some internal code cleanup

Version 5.1.1 [DEVEL] (rgerhards), 2009-07-03

• bugfix: huge memory leak in queue engine (made rsyslogd unusable in production). Occured if at least one queue was in direct mode (the default for action queues)
• imported many performance optimizations from v4-devel (4.5.0)
• bugfix: subtle (and usually irrelevant) issue in timout processing timeout could be one second too early if nanoseconds wrapped
• set a more sensible timeout for shutdow, now 1.5 seconds to complete processing (this also removes those cases where the shutdown message was not written because the termination happened before it)
• numerous enhancements and fixes imported from the v4 branch
  

Version 4.5.0 [DEVEL] (rgerhards), 2009-07-02

• activation order of inputs changed, they are now activated only after privileges are dropped. Thanks to Michael Terry for the patch.
• greatly improved performance
• greatly reduced memory requirements of msg object to around half of the previous demand. This means that more messages can be stored in core! Due to fewer cache misses, this also means some performance improvement.
• improved config error messages: now contain a copy of the config line that (most likely) caused the error
• reduced max value for $DynaFileCacheSize to 1,000 (the former maximum of 10,000 really made no sense, even 1,000 is very high, but we like to keep the user in control ;)).
• added capability to fsync() queue disk files for enhanced reliability (also add’s speed, because you do no longer need to run the whole file system in sync mode)
• more strict parsing of the hostname in rfc3164 mode, hopefully removes false positives (but may cause some trouble with hostname parsing). For details, see this bug tracker: http://bugzilla.adiscon.com/show_bug.cgi?id=126
• added configuration commands (see doc for explanations)
  * $OMFileZipLevel
  * $OMFileIOBufferSize
  * $OMFileFlushOnTXEnd
  * $MainMsgQueueSyncQueueFiles
  * $ActionQueueSyncQueueFiles

• done some memory accesses explicitely atomic
• bugfix: subtle (and usually irrelevant) issue in timout processing timeout could be one second too early if nanoseconds wrapped
• set a more sensible timeout for shutdow, now 1.5 seconds to complete processing (this also removes those cases where the shutdown message was not written because the termination happened before it)
• internal bugfix: object pointer was only reset to NULL when an object was actually destructed. This most likely had no effect to existing code, but it may also have caused trouble in remote cases. Similarly, the fix may also cause trouble…