Problem while processing updates

[GoogleCodeExporter]

Hi,
I'm having problems while the program is processing updates (at the planet 
update section). It always stops at "41588 bytes written", and shows several 
error messages. I don't know why is this happening now, a few days ago this 
task was completed without any problems, but this week I started it from 
scratch (erased everything, even planet file), and can't get past this. The 
config file is the same than before (with the same -J-Xmx value that worked the 
last time).

Thanks

Original issue reported on code.google.com by raulgarf...@gmail.com on 20 Jul 2013 at 3:48

• Blocked on: #113

Attachments:

• report.log
• messages.log

[GoogleCodeExporter]

Dear user,

thank you for your interest in the program.

According to the uploaded logs, your problem is most probably caused by the 
external program Osmosis running out of disk space. Osmosis is storing it's 
temporary data in the system temporary directory. If there is not enough space 
in the temporary volume, you can run Osm2garmin with the startup parameter

-Djava.io.tmpdir=/dir/to/osm/tmp

to force creation of temporary files in the volume with enough space available.

Original comment by mantl...@gmail.com on 20 Jul 2013 at 4:59

[GoogleCodeExporter]

I don't know what's the problem. I added that startup parameter, but as soon as 
it starts processing the updates it shows those same error messages. This time 
the error  messages appear at "Processing updates - 25220 bytes written", so it 
happens almost at the beginning. I have plenty of disk space (more than 500 gb).

Thanks

Original comment by raulgarf...@gmail.com on 24 Jul 2013 at 4:48

Attachments:

• messages.log
• report.log

[GoogleCodeExporter]

Dear user,

the log shows that you are trying to process more than 300 update files (named 
updatexxx.osc.gz). Because each update file represents 24 hours period, it 
means that your Planet file is nearly 1 year old. Current version of the 
software does not expect such age of the Planet file needing update and you are 
most probably running into problems caused by too many file descriptors open or 
similar issue.

This is a defect in the Osm2garmin which should be solved as soon as possible, 
but currently the only possible solution is to start from scratch with a new 
planet file.

If your Planet file is not as old, the problem could be caused by missing or 
incorrect state.txt file in the osmosiswork directory. Please check whether 
your state.txt file corresponds to the age of your planet file. If not, 
download proper xxx.state.txt file from 
http://planet.openstreetmap.org/replication/hour subdirectories which is older 
than your planet file (but not too much older), put it into your osmosiswork 
directory and rename it state.txt. Delete state_old.txt if exists. Finally 
re-run the software.

Original comment by mantl...@gmail.com on 24 Jul 2013 at 8:39

[GoogleCodeExporter]

Original comment by mantl...@gmail.com on 24 Jul 2013 at 8:56

• Now blocked on: #113

[GoogleCodeExporter]

Dear user, the version containing r265 is available for download. Possibly it 
could solve your problem. Uninstall your version and install the new version, 
it will not affect your data. Delete all update*.osc.gz files from your working 
directory before starting processing. Please report here whether your problem 
was fixed.

Original comment by mantl...@gmail.com on 25 Jul 2013 at 9:57

[GoogleCodeExporter]

My planet file was the most recent one, but for some reason the program 
downloaded and tried to process all the update files (more than 300). I 
downloaded a xxx.state.txt as you suggested and that did the trick.
I'm having one last problem, though. The program finishes and all files are 
correctly generated, but the western europe gmapsupp file is too large (my 
Garmin gps only supports fat32, and that gmapsupp is larger than 4 Gb). All 
other files from other regions are ok. Is there a way that you can split the 
western europe region into two separate regions? Maybe western europe should be 
split by default on your program, so fat32 users won't have this problem. BTW, 
your program is great. Thanks!

Original comment by raulgarf...@gmail.com on 3 Aug 2013 at 6:46

[GoogleCodeExporter]

Dear user, thank you for your feedback. Unfortunately, the !OpenStreetMap data 
are growing very fast and the Western Europe region as defined in the 
pre-defined regions set has grown above the 4Gb limit recently. You can make 
the overlap with the Central Europe region smaller or redefine European regions 
other way according to your needs.

Of course, you can skip planet update (but check "Update regions using current 
Planet file", of course) and check for processing the defect region only in 
order to re-process it as fast as possible.

Please refer to the Issue 114 if you want to know how and when the predefined 
Western Europe region will be changed in the future release, nevertheless it 
will not affect regions in existing installations.

Original comment by mantl...@gmail.com on 3 Aug 2013 at 8:47

• Changed state: Fixed

[GoogleCodeExporter]

Thanks, but is there any way I can fix this now? I don't know how to do the 
things you suggested (make the overlap with central europe smaller or redefine 
european regions). I can start from scratch if needed, but if the program 
downloads the most recent planet file I don't know how I can make that european 
region smaller. Tnanks again.

Original comment by raulgarf...@gmail.com on 3 Aug 2013 at 10:33

[GoogleCodeExporter]

Follow these steps to re-process the Western Europe region:

1. Go to Tools - Options, select card Regions and uncheck Enabled box for each 
region but Western Europe.
2. Change Western Europe bounding box coordinates. Currently 35.0 -24.0 72.0 
9.0 should be sufficient (eastern border shift from 10E to 9E, i.e. cca 70 km 
to the West). To edit the coordinate cell, click on it, press F2 to enter the 
cell and ENTER when finished. You can check bounding box of the region pressing 
"Display" button when the region is selected (blue).
3.Select Processing parameters card. Check "Skip planet update" and "Update 
regions using current Planet file".
4. Press OK to close Options window and save all settings.
5. Press Start. New definition of the Western Europe region will be extracted 
from the Planet and processed.

If you would like to update your Planet file in the future and re-process all 
regions, don't forget to uncheck the "Skip planet update" box and check 
"Enabled" for all regions before starting update.

Original comment by mantl...@gmail.com on 3 Aug 2013 at 11:48