[syslog-ng] [Bug 121] After service syslog-ng reload, the first log don' t transfer to remote servicer via TLS

bugzilla at bugzilla.balabit.com bugzilla at bugzilla.balabit.com
Sun Oct 23 09:29:54 CEST 2011


https://bugzilla.balabit.com/show_bug.cgi?id=121





--- Comment #3 from Balazs Scheidler <bazsi at balabit.hu>  2011-10-23 09:29:53 ---
(In reply to comment #2)
> Thank you for your feedback.
> I am confuse that:
> If I don't write the second log, it seems like the first log will not be uploaded to server forever, even I wait about ten minutes.

the progress on the TLS handshake doesn't depend on time, it depends on messages being delivered to the target host.

> According your comments, how many minutes do the TLS negotiation need ? or, the TLS negotiation need a certain event to trigger ?

not minutes, but 2-3 messages to be delivered when the connection is broken.

> How to screen the bug ?

One way to solve this is to enable MARK messages to be regularly posted, which will generate some activity even if no messages are to be delivered.
(e.g. if you set mark_freq() to 60, then in 3 minutes the SSL handshake will be finished.


-- 
Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.


More information about the syslog-ng mailing list