|
heyho while osm2pgsql I received the following error:
Is it possible that the error appeared because of a n error on my external HDD where I store my *.osm files or does this look like another reason? It might be possible, that the external HDD got disconnected but I don't know if the error-message was there before. |
|
Short answer - yes. Longer answer - something spat "error reading blob content Segmentation fault" over the top of the normal output from osm2pgsql. A web search shows the first part of that message in the PBF reader called by osm2pgsql, so yes, for some reason your external HDD became inaccessible and that caused the problem. Someone on IRC has just mentioned another cause of this - a downloaded extract had somehow become truncated, which meant that osm2pgsql failed to understand the data, resulting in this same "error reading blob content" message. If you're downloading extracts from somewhere like Geofabrik, there'll usually be a .md5 file available that you can compare the file you've downloaded against using "md5sum", to check that it hasn't got corrupted during the download process.
(25 May '14, 23:21)
SomeoneElse ♦
|
