[Bug 9961] New: Syslog remote logging fails if network not available on first attempt

bugzilla at busybox.net bugzilla at busybox.net
Fri Jun 16 14:08:00 UTC 2017


            Bug ID: 9961
           Summary: Syslog remote logging fails if network not available
                    on first attempt
           Product: Busybox
           Version: 1.23.x
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: critical
          Priority: P5
         Component: Other
          Assignee: unassigned at busybox.net
          Reporter: ocagdas at yahoo.com
                CC: busybox-cvs at busybox.net
  Target Milestone: ---

Busybox 1.23.2 still seems to be suffering from the issue discussed on
http://lists.busybox.net/pipermail/busybox/2010-August/073028.html and claimed
to have been fixed by

I see the changes introduced by this commit in the source code but still, if
syslog is started with the remote server address being a url, before the
network is up and running, it never will attempt sending any data out. I waited
longer than set 2 minutes period, even 10-15 minutes on each try, and verified
the no transmission by running tcpdump on the hardware platform.

However, if busybox is restarted with the exact same parameters once the
networking is running, I can see the udp traffic and verify the contents.

You are receiving this mail because:
You are on the CC list for the bug.

More information about the busybox-cvs mailing list