Comment 11 for bug 789174

Ryan, the pipermail link above is to upstream discussion about this. Unless there is something upstream newer than that 2 year old information, your options are:
a.) run rsyslog as root by removing the $PrivDropToUser and $PrivDropToGroup options, or possibly overriding them in /etc/resolv.conf.d/ files (i'm not sure if this is possible or not).
b.) use the 'Sleep' work around suggested on the thread (git commit [1]).
c.) listen on a port > 1024
d.) pay upstream for 2 weeks work to get the fix done correctly.

[1] http://git.adiscon.com/?p=rsyslog.git;a=commitdiff;h=d19806431653e6575a002ab4