Re: [rsyslog] Log messages held when using FQDN as omrelp target and (/etc/hosts entry not present or 'After=network.target' not present in Unit file)

2017-07-10 Thread deoren
On 7/8/17 10:19 PM, deoren wrote: Running the same command on the SSD copy of that VM I see about 220ms startup time. I'm also new to systemd, so I might be misinterpreting the values, but it appears that the slower load time for rsyslog is giving the system sufficient time to load all require

Re: [rsyslog] Log messages held when using FQDN as omrelp target and (/etc/hosts entry not present or 'After=network.target' not present in Unit file)

2017-07-08 Thread deoren
On 7/8/17 9:23 PM, David Lang wrote: On Sat, 8 Jul 2017, deoren wrote: Looking around I learned of these two directives: $DebugLevel 2 $DebugFile /var/log/rsyslog-debug.log I added those, rebooted the VM and quickly had lots of debug info to work with. In the file I found these entries: 56

Re: [rsyslog] Log messages held when using FQDN as omrelp target and (/etc/hosts entry not present or 'After=network.target' not present in Unit file)

2017-07-08 Thread David Lang
On Sat, 8 Jul 2017, deoren wrote: Looking around I learned of these two directives: $DebugLevel 2 $DebugFile /var/log/rsyslog-debug.log I added those, rebooted the VM and quickly had lots of debug info to work with. In the file I found these entries: 5676.682567045:sendToLogserver queue:Reg

Re: [rsyslog] Log messages held when using FQDN as omrelp target and (/etc/hosts entry not present or 'After=network.target' not present in Unit file)

2017-07-08 Thread deoren
On 7/7/17 2:28 AM, deoren wrote: First of all, thank you for reading this and thanks to the devs for rsyslog. Admittedly, my configuration is likely at fault as I'm still learning how to configure a rsyslog client installation for reliable remote logging. Environment (client & server): * Ub

[rsyslog] Log messages held when using FQDN as omrelp target and (/etc/hosts entry not present or 'After=network.target' not present in Unit file)

2017-07-07 Thread deoren
First of all, thank you for reading this and thanks to the devs for rsyslog. Admittedly, my configuration is likely at fault as I'm still learning how to configure a rsyslog client installation for reliable remote logging. Environment (client & server): * Ubuntu 16.04 (client, server) * rsysl