[syslog-ng] [Bug 121] New: 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
Wed May 25 10:07:18 CEST 2011


           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 at balabit.hu
        ReportedBy: yong.zheng at 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 ?

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