Hello, shorewall configuration files /etc/shorewall/shorewall.conf and /etc/shorewall6/shorewall6.conf has this line: > LOGFILE=/var/log/messages this file is not existing in Mageia anymore. From the configuration https://shorewall.org/manpages/shorewall.conf.html, it should be: > LOGFILE=systemd (I wasn't able yet to log anything...)
Thank you for the report. It is curious that this has not surfaced before. My system certainly does not have /var/log/messages, but I do not have shorewall running. LOGFILE=[pathname|systemd] This parameter tells the /sbin/shorewall program where to look for Shorewall messages when processing the dump, logwatch, show log, and hits commands. *If not assigned or if assigned an empty value, /var/log/messages is assumed.* For further information, see shorewall-logging(8). Beginning with Shorewall 5.0.10.1, you may specify systemd to use journelctl -r to read the log. Note that you *may* specify systemd, it is not obligatory. /var/log/messages is legitimate if it exists. Should shorewall installation create it if necessary? Could shorewall itself use the equivalent of >> to append to that file, which I recall creates it if it does not exist? /var/log/messages does not seem to exist for *any* of our current packages. "this file is not existing in Mageia anymore" indeed. BTAIM This looks like a packaging problem. Assigning this globally, needs some discussion about what to do.
Source RPM: shorewall => shorewall-5.2.8-4.mga9.src.rpmAssignee: bugsquad => pkg-bugsSummary: wrong logging mechanism => Shorewall configs have wrong LOGFILE parameter: /var/log/messages does not exist