If I were to guess I’d say the RHEL systems were sending plain text to a 
listener expecting SSL encryption, but without seeing the full rsyslog 
configurations on both sender and receiver it is impossible to say for sure.

Regards,


> On Aug 22, 2025, at 13:57, Jayesh H Kamdar via rsyslog 
> <[email protected]> wrote:
> 
> I just setup a rsyslog server on ubuntu 2204. I have configured few clients 
> (RHEL8 and Ubuntu 2004) to send logs to this rsyslog server. Logs from ubuntu 
> clients are coming fine but from the RHEL8 machines, all I see are files 
> starts with quotes and rest of file name is made up of numbers and hash sign 
> (#). And some files are binary files and others are made up of #, digits and 
> hash sign. I won't able to upload config file (rsyslog.conf) as I am an air 
> gapped lab.
> 
> Here is the example of files names received on my rsyslog server:
> #026#003#001#000.log
> #010#005#005#003#010#006#006#002.log
> 
> Name of the log files received for both RHEL8 clients are exactly same but 
> none of these files have any system logs. My rsyslog.conf on the client has 
> this config: *.* @@<log-server-ip>:514 I have compared rsyslog.conf with 
> other working hosts and all looks normal.
> 
> Anyone has come across this kind of issue?
> 

_______________________________________________
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.

Reply via email to