Builder rsyslog-solaris10-i386 Build #1834

Results:

Failed

SourceStamp:

BuildSlave:

Reason:

The SingleBranchScheduler scheduler named 'schedule-rsyslog-solaris10-i386' triggered this build

Steps and Logfiles:

1. git updating ( 1 mins, 3 secs )
   1. stdio
2. shell  
   1. - no logs -
3. shell_1  
   1. - no logs -
4. shell_2  
   1. - no logs -
5. shell_3  
   1. - no logs -

Build Properties:

Forced Build Properties:

Responsible Users:

1. Rainer Gerhards

   rgerhardsohnoyoudont@adiscon.com

Timing:

All Changes:

:

1. Change #205069

   Category	rsyslog
   Changed by	Rainer Gerhards <rgerhardsohnoyoudont@adiscon.com>
   Changed at	Mon 19 Aug 2024 08:54:31
   Repository	https://github.com/rsyslog/rsyslog.git
   Project	rsyslog
   Branch	master
   Revision	1c0f9bba505d32af8a0421b495027f726cb0aa4c

   Comments

   omfwd: implement native load balancing - phase 1
   This patch implements a simple round-robin load balancer
   for omfwd. It provides equal distribution of load to a pool
   of target servers.
   
   The code currently has no different modes and no special tuning
   for the load balancer. However, it works very well in the most
   common use cases. Furthermore, it provides a solid base on which
   more elaborate functionality can be build if there is need to.
   
   The new functionality is fully backwards compatible with previous
   configuration settings.
   
   New action() config params:
   * pool.resumeinterval
   
   New/"changed" rstats counters
   Each target receives its own set of pstats counters. Most
   importantly this is the case for byte counts. That counter retains
   the same naming, but there may now be multiple of these counters,
   one for each target ip, port tuple.
   
   New pstats message count to target
   Among others, this can be used for checking that the load balancer
   works as intended. The so-far byte count emitted does not provide
   a clear indication of how many messages the targets had actually
   processed.
   
   For obvious reasons, this message count makes most sense in
   advanced load balancing scenarios, but also provides additional
   insight into round-robin. Non-matches indicate that targets
   went offline, and we can now evaluate the impact this had
   on processing.
   
   - re-design rebind functionality
   
   This now works at the transaction level. It causes a rebind of all
   pool members. Previous code did not work 100% correct since for a
   couple of years now (after output batching integration).
   
   As cleanup, rebindInterval support has been removed from tcpClt,
   because omfwd is the only user. This permits a cleaner code path.
   
   We also noticed a bug with rebindInterval:  it caused some mild
   message duplication for quite some time. This went unnoticed.
   To address that efficiently, rebindInterval in the future will
   be considered once per batch. That means up to (maxBatchSize - 1)
   messages may be transmitted more than the rebindinterval is.
   That's the cleanest mode of operation and should not make any
   difference for real deployments.
   
   Some additional work done in this commit:
   
   netstream: harden component against upper-layer logic errors
   
   network subsystem: better handle API errors and provide more info
   
   omfwd: add new parameter "iobuffer.maxsize"
   
   add new global parameter debug.abortoninternalerror and use it
   
   This parameter permits to make test runs fail when an internal error
   is detected and gracefully handled by rsyslog. While it is great to
   have it gracefully handled in practice, we should not accept this
   during testing. The new parameter permits to abort in this case and
   emits the related error message beforehand. It is turned on by
   default in our regular tests.
   
   add dedicated error code for "hard" program errors
   
   omfwd: some cleanup + error message fix + new debug level messages
   
   imptcp: improve error messages
   
   add omfwd option to NOT do extended connection check
   
   also output wrkr id in some omfwd messages (primarily debugging aid)
   
   better debug info via LogMsg() interface
   
   improve messages regarding imptcp and omfwd suspension / thread IDs
   
   refactor and enchance minitcpsrvr for mimicing died servers
   
   new global (debugging) option, correction of an informational msg
   
   add global option allmessagestostderr
   
   add new tests

   Changed files

   • action.c
   • plugins/imptcp/imptcp.c
   • runtime/glbl.c
   • runtime/glbl.h
   • runtime/netstrm.c
   • runtime/nsd_ptcp.c
   • runtime/rsconf.c
   • runtime/rsconf.h
   • runtime/rsyslog.h
   • runtime/tcpclt.c
   • runtime/tcpclt.h
   • runtime/wtp.c
   • tests/Makefile.am
   • tests/diag.sh
   • tests/minitcpsrvr.c
   • tests/omfwd-lb-1target-retry-1_byte_buf-TargetFail.sh
   • tests/omfwd-lb-1target-retry-1_byte_buf.sh
   • tests/omfwd-lb-1target-retry-full_buf.sh
   • tests/omfwd-lb-1target-retry-test_skeleton-TargetFail.sh
   • tests/omfwd-lb-1target-retry-test_skeleton.sh
   • tests/omfwd-lb-2target-basic.sh
   • tests/omfwd-lb-2target-impstats.sh
   • tests/omfwd-lb-2target-one_fail.sh
   • tests/omfwd-lb-2target-retry.sh
   • tests/omfwd-lb-susp.sh
   • tests/omfwd_impstats-tcp.sh
   • tests/rcvr_fail_restore.sh
   • tests/sndrcv_tls_anon_rebind.sh
   • tools/omfwd.c
   • tools/rsyslogd.c

2. Change #205071

   Category	rsyslog
   Changed by	Rainer Gerhards <rgerhardsohnoyoudont@adiscon.com>
   Changed at	Mon 19 Aug 2024 10:39:55
   Repository	https://github.com/rsyslog/rsyslog.git
   Project	rsyslog
   Branch	master
   Revision	d5e75a527b915da8f95e10dbd073278520efd72f

   Comments

   Merge pull request #5369 from rgerhards/omfwd-loadbalance-s1
   omfwd: implement native load balancing - phase 1

   Changed files

   • no files