On 11/7/2017 10:31 AM, matthew.gaetano wrote:
With the exception of the relation to storage, yes, for the most part. We
encountered the issue on a physical server using SCSI/SATA drives. Our
secondary tester were in vmware.
I initially emphasized the boot speed from running the Ubuntu 16.04 VM
on a SSD, but I believe the problem is mainly to do with the startup
ordering of rsyslog and network support. I ended up working around the
issue of rsyslog starting before network support was available by
modifying the systemd unit with a conf fragment:
# /etc/systemd/system/rsyslog.service.d/10-wait-on-network.conf
[Unit]
After=network.target
It mostly works for us and appears to be what stock CentOS 7 is doing
with their rsyslog package.
It appears someone else has posted a similar issue already as well @
https://github.com/rsyslog/rsyslog/issues/1694
Thanks for linking to that GitHub issue. Their issue appears to be with
omfwd while mine was with omrelp. Presumably the issue is "lower" down
the stack than either module as David Lang indicated here:
https://github.com/rsyslog/rsyslog/issues/1694#issuecomment-319674827
_______________________________________________
rsyslog mailing list
http://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of
sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE
THAT.
