I've been operating the Overpass instance at overpass.kumi.systems
for a while now and just ran into a problem. I noticed that my
server is getting outdated and it seems that something is wrong with
my database index. Specifically, I get the following error message
I don't really know how to fix that issue. Do you have any ideas?
Email: [hidden email]
XMPP: [hidden email]
Mobile: +43 660 6340166
*** DISCLAIMER ***
This document is only intended for the person to whom it is
addressed. If you have received it, it was obviously addressed to you.
Therefore, you are free to read it, even if I didn't mean to send it to
you. However, if the contents of this email sound gibberish to you, you
were probably not the intended recipient - or you're just a mindless
cretin. If either is the case, you should immediately delete yourself
and destroy your computer. After doing this, please contact me
immediately. Well, obviously you can't use your computer for this, as
you have destroyed it. Also, you deleted yourself. Sorry, I digress...
In case I didn't send this email to you, I sincerely apologize. In
case of non-receipt of this email, I do not take any responsibility,
because it means that either you or your email provider or both use a
Microsoft Windows operating system. You know how glitchy that is, right?
Nor will I accept any liability, tacit or implied, for any damage
you may or may not incur as a result of receiving, or not, as the case
may be, from time to time, notwithstanding all liabilities implied or
otherwise and... erm... you know... whatever the case may be... IT
WASN'T ME. YOU'RE MEAN.
> /opt/osm-3s_v0.7.54/db/nodes.bin File_Blocks::read_block: Index
> I don't really know how to fix that issue. Do you have any ideas?
I came across such errors with an overpass instance.
To make a story short : You have to wipe out db files & re-import
But what is interesting is to understand what happened and try to reduce the
odds that it happens again.
In my case, the cause was an interrupted "update_database" process during diff
kernel log files or syslog might confirm the cause. In my case, that was an
"out of memory" condition in a OpenVZ container that killed the
update_database process leaving some db files in an inconsistent state.
Am 23.11.2017 um 11:51 schrieb sly (sylvain letuffe):
>> /opt/osm-3s_v0.7.54/db/nodes.bin File_Blocks::read_block: Index
>> I don't really know how to fix that issue. Do you have any ideas?
> I came across such errors with an overpass instance.
> To make a story short : You have to wipe out db files & re-import
I noticed that your db currently shows 2012-09-23T05:18:02Z as current
timestamp. Are you somehow trying to load all data since Sep 12 2012