|
From: Erich T. <eri...@th...> - 2026-01-18 22:57:42
|
Hi Boris
Am 18.01.2026 um 20:44 schrieb Boris via leaf-user:
> Hej Erich,
...
>>
>> So maybe it is enough to just comment it out and the message is just a
>> warning.
>
> I can add the information, that the mentioned line is not present on
> both boxes here. Might be some forensic work to find out where the line
> is from and what the file belongs to....
>
OK.. that is rather easy.
I checked the releases from 7.0.0 to 7.5.0. On every release the plugin
is present in ulogd.conf, at least in repo/ulogd. The I checked
buildtool.mk
commit f1a24e44c786f1f8b9d16e2b7299756c2bc07ad9
<File>
Source = usr/lib/ulogd/ulogd_inppkt_ULOG.so
Filename = usr/lib/ulogd/ulogd_inppkt_ULOG.so
Type = binary
Permissions = 755
</File>
commit 5068d91c042768709ae647d4a1b4efca485a0fc5
Author: kapeka <ka...@us...>
Date: Sat Jun 14 15:03:44 2025 +0200
ulogd: update to upstream version 2.0.9
fix linking ulogd_inppkt_NFLOG.so with libmnl - without ulogd fails
to start
Here the incriminating plugin goes amiss, but is also removed from
ulogd.conf. This makes me believe that it is not needed for ulogd to run.
ulogd.conf is a configuration file which may have been taken over from
an earlier release which still had the plugin. So I commented it out and
restarted ulogd without the plugin. It appears that shorewall is still
logging even without this plugin being present in ulogd.conf. I guess
this proves that the plugin is not necessary for the operation of ulogd
in our environment but it also shows that such a missing plugin can
hamper ulogd.
So I guess we can forget this issue and just call it a heads-up should
anyone face a problem starting ulogd.
cheers
ET
--
„Wer von seinem Tag nicht zwei Drittel für sich hat, ist ein Sklave.“
―Friedrich Nietzsche
|