[syslog-ng]losing messages using syslog-ng-1.4.7 & libol-0.2.20

Balazs Scheidler [email protected]
Tue, 7 Nov 2000 14:10:00 +0100


I found out the problem with the test program you sent to the list. After
correcting the problem, all messages were received syslog-ng just fine.

You forgot to add an "\n" to the end of each message. Since TCP is used as
transport protocol, messages may be piggybacked. 

-     	int length = sprintf(message, "%d-%d %s", thread_number,(int)counter,buf);
+     	int length = sprintf(message, "%d-%d %s\n", thread_number,(int)counter,buf);

tudor:~/src/syslog-ng-1.4.8/src$ wc -l valami 
  36300 valami

with logconf.h:

#define REMOTE_SERVER "tudor"
#define REMOTE_PORT 2000
#define MESSAGE_SIZE 100
#define USECONDS_BETWEEN_MESSAGES 250000
#define SECONDS_TO_TRANSMIT 30
#define NUMBER_OF_THREADS 300

syslog-ng.conf:

options { gc_idle_threshold(30); gc_busy_threshold(3000); };

source src { tcp(localport(2000) max_connections(300)); };
source xxx { internal(); };
destination dst { file("valami" log_fifo_size(6000)); };

log { source(src); destination(dst); };



-- 
Bazsi
PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
     url: http://www.balabit.hu/pgpkey.txt