what I would do is tie a ruleset to imudp that writes the log to the file and then in the main ruleset write to the file and send the log. that way the logs follow a different path depending on how they arrive and there's no chance of a log arriving remotely getting sent out again.

David Lang

On Thu, 14 Apr 2022, Victor FROLOV (VMcS via rsyslog wrote:

Date: Thu, 14 Apr 2022 16:25:40 +0200
From: "Victor FROLOV (VMcS via rsyslog" <rsyslog@lists.adiscon.com>
To: rsyslog@lists.adiscon.com
Cc: "Victor FROLOV (VMcS" <rsyslog-...@vmcs.fr>
Subject: [rsyslog] Two servers logs synchronization by rsyslog

Hello,



I need your adwise.



Environment:

I have 2 freeradius servers united in one cluster. The radius databases are
synchronized and a client can send the request to any of the servers
following the client config. By default, radius write the logs locally and
during the troubleshooting I must look the logs on the both servers to found
the traces of client.

I would like to synchronize the logs on the servers, i.e. each server must
write the local radius messages and the messages received from adjacent
server in the local log, also send the local only message to the adjacent
server (not received by udp message - to avoid the loop).

For the radius messages I use the local4 facility.

Freeradius send the messages to the local rsyslog through the file socket
/dev/syslog, then rsyslog write the messages to the log file and also send
these messages to the adjacent server by udp/514.



By other words, I need the next behavior :

On each server

-              The messages local4.* received via udp from the adjacent
server must be writed in the local log

-              The messages local4.* received via file socket OR via udp
from from the localhost must be writed in the local log AND must be sent to
the adjacent server



Problem :

The problem is the looping the messages between the servers.

My configuration:

(SERVER1 and SERVER2 are the FQDN well resolved to IP adresses)



SERVER1 :

#==============================================================

module(load="imuxsock")

module(load="imudp")

input(type="imudp" port="514")



template(name="TMPL_Radius_Local_Log" type="string"

   string="/var/log/radiusd/radiusd-%$YEAR%-%$MONTH%-%$DAY%.log"

)



ruleset(name="RLS_Radius"){

   if $fromhost == "SERVER2" and prifilt("local4.*") then {

       action (type="omfile" dynafile="TMPL_Radius_Local_Log")

       stop

   } else {

          action (type="omfile" dynafile="TMPL_Radius_Local_Log")

          action (type="omfwd" target=" SERVER2" port="514" protocol="udp")

          stop

       }

}



local4.* {

       call RLS_Radius

}



auth,authpriv.*                 /var/log/auth.log

*.*;auth,authpriv.none          -/var/log/syslog

kern.*                          -/var/log/kern.log

mail.*                          -/var/log/mail.log

mail.err                        /var/log/mail.err

*.emerg                         :omusrmsg:*



SERVER2 :

#==============================================================

module(load="imuxsock")

module(load="imudp")

input(type="imudp" port="514")



template(name="TMPL_Radius_Local_Log" type="string"

   string="/var/log/radiusd/radiusd-%$YEAR%-%$MONTH%-%$DAY%.log"

)



ruleset(name="RLS_Radius"){

   if $fromhost == "SERVER1" and prifilt("local4.*") then {

       action (type="omfile" dynafile="TMPL_Radius_Local_Log")

       stop

   } else {

          action (type="omfile" dynafile="TMPL_Radius_Local_Log")

          action (type="omfwd" target=" SERVER1" port="514" protocol="udp")

          stop

       }

}



local4.* {

       call RLS_Radius

}



auth,authpriv.*                 /var/log/auth.log

*.*;auth,authpriv.none          -/var/log/syslog

kern.*                          -/var/log/kern.log

mail.*                          -/var/log/mail.log

mail.err                        /var/log/mail.err

*.emerg                         :omusrmsg:*



Why I have the looping between the servers? How to realize the mentioned
behavior?



WBR,

Victor

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

_______________________________________________
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