Tried to start rsyslog 8.1904 in chrooted environment, but got the systemd
service timeout error.
The sd_notify in rsyslog 8.1901 version from Debian repositories is working
fine with just bind mounting host /run/systemd/notify into the chroot under
the same path.
The root cause seems to be the rsyslog 8.1904 in OBS Debian9 repository is
not built with systemd support for some reason.
~# /usr/sbin/rsyslogd -vvv
rsyslogd 8.1904.0 (aka 2019.04) compiled with:
PLATFORM: x86_64-pc-linux-gnu
PLATFORM (lsb_release -d):
FEATURE_REGEXP: Yes
GSSAPI Kerberos 5 support: No
FEATURE_DEBUG (debug build, slow code): No
32bit Atomic operations supported: Yes
64bit Atomic operations supported: Yes
memory allocator: system default
Runtime Instrumentation (slow code): No
uuid support: Yes
systemd support: No
Config file: /etc/rsyslog.conf
PID file: /var/run/rsyslogd.pid
Number of Bits in RainerScript integers: 64
Peter
_______________________________________________
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.
