From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: 'iptables 1.8.3' => 'collectd' needs updated lib Date: Wed, 11 Sep 2019 16:27:59 +0100 Message-ID: In-Reply-To: <4a0b6ef1-8ac9-4abb-f334-c0b290e24f20@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7186170705596499183==" List-Id: --===============7186170705596499183== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, As far as I am aware Core Update 136 is still open and hopefully Arne will me= rge these before it closes. Best, -Michael > On 11 Sep 2019, at 16:25, Matthias Fischer = wrote: >=20 > On 11.09.2019 17:08, Michael Tremer wrote: >> Hi, >>=20 >> We would normally add a link to the rootfile of collectd so that the whole= package is being shipped again. That is the easiest option and usually does = not waste a lot of space. >=20 > Ok. >=20 > Besides: > I built the last updates on Core 135 to test them here as quickly as > possible. >=20 > To make things look better, I'll send new patches for 'iptables 1.8.3' / > 'collectd' and 'iproute 5.2.0'- based on 'next'. >=20 > Best, > Matthias >=20 >> Best, >> -Michael >>=20 >>> On 10 Sep 2019, at 19:33, Matthias Fischer wrote: >>>=20 >>> Hi, >>>=20 >>> during testing of 'iptables 1.8.3' - see >>> https://patchwork.ipfire.org/patch/2401/ I found that the graphs for >>> "firewallhits" in "Network (other)" stayed emtpy with "-nan Bps". >>>=20 >>> During restart 'makegraphs' complained about a missing lib for 'iptables': >>>=20 >>> root(a)ipfire: /var # /etc/init.d/collectd restart >>> Stopping Collection daemon... [ OK ] >>> Mounting RRD ramdisk... [ OK ] >>> Starting Collection daemon... >>> lt_dlopen ("/usr/lib/collectd/iptables.so") failed: file not found. The >>> most common cause for this problem are missing dependencies. Use ldd(1) >>> to check the dependencies of the plugin / shared object. >>> Unable to load plugin iptables. [ OK ] >>>=20 >>> 'ldd' showed 'not found', because during updating 'iptables' the >>> 'libip4tc' and 'libip6tc'-symlinks were changed, but >>> '/usr/lib/collectd/iptables.so' wasn't updated: >>>=20 >>> root(a)ipfire: /usr/lib/collectd # ldd /usr/lib/collectd/iptables.so >>> linux-gate.so.1 (0xb7f42000) >>> libiptc.so.0 =3D> /lib/libiptc.so.0 (0xb7f2b000) >>> libip4tc.so.0 =3D> not found >>> libip6tc.so.0 =3D> not found >>> libc.so.6 =3D> /lib/libc.so.6 (0xb7d61000) >>> libip4tc.so.2 =3D> /lib/libip4tc.so.2 (0xb7d58000) >>> libip6tc.so.2 =3D> /lib/libip6tc.so.2 (0xb7d4f000) >>> /lib/ld-linux.so.2 (0xb7f44000) >>>=20 >>> After updating '/usr/lib/collectd/iptables.so' to the current build it >>> didn't complain anymore: >>>=20 >>> root(a)ipfire: /usr/lib/collectd # ldd iptables.so >>> linux-gate.so.1 (0xb7f8a000) >>> libiptc.so.0 =3D> /lib/libiptc.so.0 (0xb7f72000) >>> libip4tc.so.2 =3D> /lib/libip4tc.so.2 (0xb7f69000) >>> libip6tc.so.2 =3D> /lib/libip6tc.so.2 (0xb7f60000) >>> libc.so.6 =3D> /lib/libc.so.6 (0xb7d96000) >>> /lib/ld-linux.so.2 (0xb7f8c000) >>>=20 >>> 'makegraphs' restarted without errors and "firewallhits graph" are >>> showing numbers again. So far, so good. >>>=20 >>> But: how do we ship this update for 'collectd' the best way? >>>=20 >>> Should we update ALL libs for 'collectd'? >>>=20 >>> I checked the other libs, and besides 'iptables.so', 'ldd' showed no >>> more 'not found'-errors. >>>=20 >>> Any hints? >>>=20 >>> Best, >>> Matthias >>=20 >>=20 >=20 --===============7186170705596499183==--