Hello, I suggest to start from eliminating journald from the equation.
In your case it means: - Make sure that you are sending logs from your nodes to the rsyslog server through udp or tcp (check documentation for imtcp and imudp) - Make sure that rsyslog writes them to the file you configured in its config (say, not /var/log/messages but some other less common name configured by you in rsyslog configuration) Then you will be able to validate that the problem you observe is not relevant to journald. Den tis 15 dec. 2020 kl 20:44 skrev supertwisters via rsyslog < [email protected]>: > > Hi. > Thanks for the answer. Here is the current status in my server. What should > i do now? I'm pretty new to rsyslog, So i'm not sure what should i do now. > > netstat -a | grep /dev/log > unix 26 [ ] DGRAM 8143 /dev/log > > cat /etc/rsyslog.d/listen.conf > $SystemLogSocketName /run/systemd/journal/syslog -- WBR & WBW, Vitaly _______________________________________________ rsyslog mailing list https://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.
