drolbr/Overpass-API

File_Blocks_Index: Data file size does not match block size

Closed this issue · 1 comments

angoca commented

I run the following query once a day, and today I hit this error:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
  <meta http-equiv="content-type" content="text/html; charset=utf-8" lang="en"/>
  <title>OSM3S Response</title>
</head>
<body>

<p>The data included in this document is from www.openstreetmap.org. The data is made available under ODbL.</p>
<p><strong style="color:#FF0000">Error</strong>: runtime error: open64: 0 Success /opt/osm3s/db/ways.bin.idx File_Blocks_Index: Data file size does not match block size </p>

</body>
</html>

Error: runtime error: open64: 0 Success /opt/osm3s/db/ways.bin.idx File_Blocks_Index: Data file size does not match block size

The Overpass query is this (query.txt):

[out:json];
rel(14161553);
(._;>;);
out;

And I use this command to download it from command line:

wget -O "giro-14161553.json" --post-file="query.txt" "https://overpass-api.de/api/interpreter" >> "output.log" 2>&1

And it returned 0 as error code, with the following output:

--2023-02-07 03:47:17--  https://overpass-api.de/api/interpreter
Resolving overpass-api.de (overpass-api.de)... 178.63.48.217, 178.63.11.215
Connecting to overpass-api.de (overpass-api.de)|178.63.48.217|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘giro-14161553.json’

     0K                                                        44.1M=0s

2023-02-07 03:47:33 (44.1 MB/s) - ‘giro-14161553.json’ saved [660]

My local time is UTC-5.

For another relation (14161556), I got this:

--2023-02-07 03:48:22--  https://overpass-api.de/api/interpreter
Resolving overpass-api.de (overpass-api.de)... 178.63.48.217, 178.63.11.215
Connecting to overpass-api.de (overpass-api.de)|178.63.48.217|:443... connected.
HTTP request sent, awaiting response... 500 Internal Server Error
2023-02-07 03:48:38 ERROR 500: Internal Server Error.

Which returned a non-zero code.

What is the cause of this issue? was it related to a server issue? Should I check the HTTP error code, the 500?

drolbr commented

Thank you for reporting this. But I'm still unable to reproduce the problem. As some maintenance has happened at about the time I'm confident that this had been a temporary issue only.