Rsyslog imtcp issue

[Jorge Niedbalski]

Hello,

I am the maintainer of the rsyslog/forwarder charms. While i was
working implementing an option to expose the protocol/port used by
rsyslogd I noticed that
enabling TCP on rsyslogd using imtcp ($InputTCPServerRun 514) was not
possible on any machine deployed by Juju.

The root cause is that /etc/rsyslog.d/26-juju-unit-primary-0.conf
declares a DefaultNetStreamDriver to use gTLS, and apparently both
plain && tls sockets cannot live together on rsyslogd.

After changing the $DefaultNetstreamDriver from gtls to ptcp it worked
correctly, for both actions collecting logs via TCP 514 and forwarding
logs to 10.0.3.1:6514;LongTagForwardFormat.

I know is not an option to abandon the usage of gTLS, but ideally,
Juju should have a separated service and configuration path that
doesn't interrupts any other rsyslogd process running on the host. I
think we can workaround/fix this by running 2 different rsyslogd
services with different configurations (maybe a default path different
for juju /etc/rsyslog.d/juju/ ?),

Please any observation would be appreciated

Cheers.

-- 
Jorge Niedbalski R.
Software Sustaining Engineer @ Canonical
Canonical Technical Services Engineering Team
# Email: jorge.niedbalski at canonical.com (GPG:0x3DA28544)