[Bug 121] New: After service syslog-ng reload, the first log don' t transfer to remote servicer via TLS
https://bugzilla.balabit.com/show_bug.cgi?id=121 Summary: After service syslog-ng reload, the first log don't transfer to remote servicer via TLS Product: syslog-ng Version: 3.0.x Platform: PC OS/Version: Linux Status: NEW Severity: critical Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: yong.zheng@nsn.com Type of the Report: bug Estimated Hours: 0.0 The version:syslog-ng 3.0.5 options { flush_lines (0); time_reopen (10); log_fifo_size (1000); long_hostnames (off); use_dns (yes); use_fqdn (no); create_dirs (no); keep_hostname (yes); stats_freq (3600); }; I will upload the logs to remote syslog-ng server via TLS, I encounter a issue, On client: after reload the configure via below command: #service syslog-ng reload. I write a log: #logger -p local1.info "this is test" but I don't see the log to transfer to server immediately, I wait many minutes, still don't see. I must write the second log to triger that client send the 2 logs to server #logger -p local1.info "this is test 2" the 2 logs have transfered to server immediately successfully, I can see the 2 logs on server. It is 100% reproduced. Is this a known issue, or not ? Thanks. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=121 --- Comment #1 from Balazs Scheidler <bazsi@balabit.hu> 2011-05-25 12:05:14 --- It's probably caused by TLS negotiation, which is being driven with messages as they are sent on the channel. The handshake takes 2-3 roundtrips and each message finishes one. So it takes 2-3 messages for the handshake to finish, then all are sent in an instant. It'd be possible to wait for the negotiation to finish first though, so I think it is a bug, but not very easy to solve. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=121 Yong Zheng <yong.zheng@nsn.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yong.zheng@nsn.com --- Comment #2 from Yong Zheng <yong.zheng@nsn.com> 2011-05-26 04:19:09 --- 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. According your comments, how many minutes do the TLS negotiation need ? or, the TLS negotiation need a certain event to trigger ? How to screen the bug ? Appreciate your feedback in advance. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=121 --- Comment #3 from Balazs Scheidler <bazsi@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.
https://bugzilla.balabit.com/show_bug.cgi?id=121 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |3.4.1 CC| |algernon@balabit.hu AssignedTo|bazsi@balabit.hu |algernon@balabit.hu --- Comment #4 from Gergely Nagy <algernon@balabit.hu> 2012-11-10 16:49:13 --- There's a fix for this in PE core somewhere, we should pick that over. I'll set 3.4.1 as the target milestone now, but will likely backport to 3.3 aswell, when I get around to find the fix in PE. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=121 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=121 Gergely Nagy <algernon@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|3.4.1 |3.4.2 -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
participants (1)
-
bugzilla＠bugzilla.balabit.com