search

wetshark / eventlog-to-syslog

Automatically exported from code.google.com/p/eventlog-to-syslog
0 stars 0 forks source link

Problems in the TCP protocol by using for. #65

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Changed the protocol to TCP over UDP on regedit.
Parameter EnableTCP = 1

What is the expected output? What do you see instead?
Messages are collected together, not separated individually.

What version of the product are you using? On what operating system?
Eventlog to Syslog 4.4.3 (64-Bit)
Windows7 64x
WiindowsServer2008R2 

Please provide any additional information below.
Actually all the above. If you use the UDP protocol, all normal.
See the example on the attached picture.

Original issue reported on code.google.com by aleksee...@gmail.com on 15 Aug 2012 at 1:13

GoogleCodeExporter commented 8 years ago 
What syslog server are you using?

Original comment by sherwin....@gmail.com on 16 Aug 2012 at 2:16

GoogleCodeExporter commented 8 years ago 
Hey. Are using syslog-ng 3.1.3

Original comment by aleksee...@gmail.com on 16 Aug 2012 at 5:23

Attachments:

GoogleCodeExporter commented 8 years ago 
Exact same problem here, when I switch to tcp, everything gets messed up.

I'm using rsylogd 7.4.4:

rsyslogd 7.4.4, compiled with:
    FEATURE_REGEXP:             Yes
    FEATURE_LARGEFILE:          No
    GSSAPI Kerberos 5 support:      Yes
    FEATURE_DEBUG (debug build, slow code): No
    32bit Atomic operations supported:  Yes
    64bit Atomic operations supported:  Yes
    Runtime Instrumentation (slow code):    No
    uuid support:               Yes

Original comment by buhaj...@gmail.com on 24 Oct 2014 at 8:54

GoogleCodeExporter commented 8 years ago 
Hi all!
I have problem with 4.5.1 x64. I edit registry EnableTcp =1 and service dont 
start. If i use udp - problem does not exist, all work correctly.

Original comment by oshelest...@gmail.com on 31 Oct 2014 at 6:09

Attachments: