From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: location@lists.ipfire.org Subject: Re: "location lookup 4.231.239.118" results in "[Errno 2] No such file or directory" Date: Tue, 15 Aug 2023 10:37:59 +0100 Message-ID: <9E0A432C-13F7-4B79-AA06-87A6FF4449BE@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3939030726922564488==" List-Id: --===============3939030726922564488== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Peter, It looks like this network is indeed not part of the database: bird> show route for 4.231.239.119 Table master4: 4.224.0.0/12 unreachable [fw01 2023-07-20 from 172.28.1.1] * (100) [A= S8075i] bird> q root(a)location01:~# sudo -u postgres psql location could not change directory to "/root": Permission denied psql (15.3 (Debian 15.3-0+deb12u1)) Type "help" for help. location=3D# SELECT * FROM announcements WHERE network =3D '4.224.0.0/12'; network | autnum | first_seen_at | last_seen_at --------------+--------+---------------+---------------------------- 4.224.0.0/12 | 8075 | | 2023-08-15 04:14:58.550997 (1 row) location=3D# \q root(a)location01:~# location lookup 4.224.0.0/12 [Errno 2] No such file or directory root(a)location01:~# location lookup 4.224.0.0 [Errno 2] No such file or directory root(a)location01:~# location update Downloaded new database from Tue, 15 Aug 2023 05:25:16 GMT root(a)location01:~# location dump | grep 4.224.0.0 net: 14.224.0.0/11 net: 14.224.0.0/12 net: 14.224.0.0/16 net: 14.224.0.0/17 net: 24.224.0.0/19 net: 34.224.0.0/12 net: 44.224.0.0/11 net: 54.224.0.0/11 net: 54.224.0.0/14 net: 64.224.0.0/21 net: 74.224.0.0/14 net: 84.224.0.0/16 net: 94.224.0.0/14 net: 104.224.0.0/24 net: 114.224.0.0/12 net: 124.224.0.0/12 net: 134.224.0.0/17 net: 134.224.0.0/18 net: 144.224.0.0/15 net: 154.224.0.0/13 net: 154.224.0.0/15 net: 164.224.0.0/14 net: 164.224.0.0/15 net: 174.224.0.0/17 net: 194.224.0.0/16 net: 204.224.0.0/16 However, it is part of the routing table that we are receiving and it is bein= g imported into the PostgreSQL database. I currently don=E2=80=99t have any time to debug this any further, so I am ro= lling back the release on the server that is generating the database. Please put a bug report together on this so that we won=E2=80=99t forget to i= nvestigate this in the future. Best, -Michael > On 14 Aug 2023, at 21:06, Peter M=C3=BCller wr= ote: >=20 > Hello Michael, >=20 > just something I encountered today while checking on a bunch of IP addresse= s: > Trying to look up 4.231.239.118 results in "[Errno 2] No such file or direc= tory", > an error I didn't expect to surface at this point, and I'm not sure what to > make out of it. >=20 > Behavior on the system (IPFire running Core Update 177) is as follows: >=20 > [root(a)firewall ~]# location lookup 4.231.239.118 > [Errno 2] No such file or directory > [root(a)firewall ~]# location version > Mon, 14 Aug 2023 05:21:26 GMT > [root(a)firewall ~]# location --version > location 0.9.16 >=20 > However, it doesn't look like the entire location database is broken: >=20 > [root(a)firewall ~]# location lookup 8.8.8.8 > 8.8.8.8: > Network : 8.8.8.0/24 > Country : United States of America > Autonomous System : AS15169 - GOOGLE > Anycast : yes >=20 > So far, I have only encountered this behavior in conjunction with 4.231.239= .118; > another IPFire machine running the same Core Update and libloc version, but= having > the database generated on Thu, 10 Aug 2023 05:23:53 GMT also exhibits this = behavior. >=20 > Am I doing something wrong? Should this be filed as a bug? >=20 > Thanks, and best regards, > Peter M=C3=BCller --===============3939030726922564488==--