Bug 9961 - Syslog remote logging fails if network not available on first attempt
Summary: Syslog remote logging fails if network not available on first attempt
Status: NEW
Alias: None
Product: Busybox
Classification: Unclassified
Component: Other (show other bugs)
Version: 1.23.x
Hardware: All Linux
: P5 critical
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-16 14:08 UTC by Oz
Modified: 2017-06-16 14:08 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Oz 2017-06-16 14:08:00 UTC 
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 https://git.busybox.net/busybox/commit/?id=e74d79866c6d125527e3ba69245a087a28fd19ce.

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.