osm2pgsql immediately crashes

[majesticpdx]

Hello,

I have spent the several hours trying to troubleshoot this crash, I'm not sure if this is a bug or something I am doing wrong:

osm2pgsql -c -d Dev -U XXXXX -H XXXXX -W -O Flex -S "C:\osm2pgsql-latest-x64\osm2pgsql-bin\flex-config\simple.lua" "C:\GIS\Workspace\osm-raw\puerto-rico-latest.osm.pbf"

osm2pgsql: 2.1.1 Database version: 17.4 PostGIS version: 3.5
Windows 11 Pro Version 24H2
13th Gen Intel(R) Core(TM) i7-13700HX 2.10 GHz
64.0 GB (63.7 GB usable)
C Drive: 1TB (677 GB Available) / D Drive: 4TB (3.69 TB Available)

This occurs will all lua files and different variations and syntax. I've also attempted on multiple DBs, including newly created, with POSTGIS installed, with and without HSTORE installed. I've also attempted this form both C and D drives just to rule out any storage issues.

One workaround that does work, is using version 1.5 and below and a .style file, however, it a better idea to use Flex and Lua.

The only logs that are showing any information:

2025-05-02 06:09:29  osm2pgsql version 2.1.1
2025-05-02 06:09:29  [00] SQL: (C0) SELECT pg_backend_pid()
2025-05-02 06:09:29  [00] SQL: (C0) New database connection (context=check, backend_pid=9268)
2025-05-02 06:09:29  [00] SQL: (C0) SET synchronous_commit = off
2025-05-02 06:09:29  [00] SQL: (C0) SELECT name, setting FROM pg_catalog.pg_settings
2025-05-02 06:09:29  [00] SQL: (C0) SELECT current_catalog
2025-05-02 06:09:29  [00] SQL: (C0) SELECT regexp_split_to_table(extversion, '\.') FROM pg_catalog.pg_extension WHERE extname='postgis'
2025-05-02 06:09:29  [00] Database version: 17.4
2025-05-02 06:09:29  [00] PostGIS version: 3.5
2025-05-02 06:09:29  [00] SQL: (C0) SELECT extname FROM pg_catalog.pg_extension WHERE true
2025-05-02 06:09:29  [00] SQL: (C0) SELECT nspname FROM pg_catalog.pg_namespace WHERE nspname !~ '^pg_' AND nspname <> 'information_schema'
2025-05-02 06:09:29  [00] SQL: (C0) SELECT spcname FROM pg_catalog.pg_tablespace WHERE spcname != 'pg_global'
2025-05-02 06:09:29  [00] SQL: (C0) SELECT amname FROM pg_catalog.pg_am WHERE amtype = 'i'
2025-05-02 06:09:29  [00] SQL: (C0) SELECT schemaname || '.' || tablename FROM pg_catalog.pg_tables WHERE schemaname NOT IN ('pg_catalog', 'information_schema')
2025-05-02 06:09:29  [00] Found properties table 'osm2pgsql_properties': false.
2025-05-02 06:09:29  [00] Reading file: C:\GIS\Workspace\osm-raw\puerto-rico-latest.osm.pbf
2025-05-02 06:09:29  [00] Started pool with 4 threads.

Thanks again for your help.

[mboeringa]

It is probably unrelated to the crash, but I do notice one issue in your command line, you specify -O Flex with uppercase f, while it should be -O flex with lowercase according to the manual: https://osm2pgsql.org/doc/manual.html#the-flex-output

[majesticpdx]

Thank you, I will keep in mind moving forward.

[majesticpdx]

Thank you for noting this, for this issue, it didn't matter. Still thanks, most of the time it is something really simple.

[joto]

This looks like some library incompatibility or so to me.

[pnorman]

This is the most likely cause. Windows packaging is a headache at the best of times.

Where did you download osm2pgsql from?

[majesticpdx]

Agreed. Windows can be a pain, may have to jump over Ubuntu. Downloaded via https://osm2pgsql.org/download/windows/.

[mboeringa]

For what it is worth, I successfully ran the latest osm2pgsql v2.1.1 as downloaded from the official https://osm2pgsql.org/doc/install/windows.html link in Windows 10 22H2, build 19045.5737 with the Geofabrik 'Denmark' extract as input file using the same custom osm2pgsql flex style I use on Ubuntu 24.04 to import Planet.

Of course, the OP uses Windows 11, not 10.

[lonvia]

Our builds are created on Windows 2022, which corresponds to Windows 10, it seems. Never heard of any compatibility issues between Windows versions before but, who knows, things might have changed. I've done a test build with artifacts for all three Windows versions, we test for. Can you test, if the Windows-2025 one works for you? The artifacts are here: https://github.com/lonvia/osm2pgsql/actions/runs/14833260369

[majesticpdx]

Thank you, I will check this in the next couple of days and let you know either way. If this doesn't work, I will also trouble shoot with previous versions as a process of elimination.

[majesticpdx]

Thank you so much. I was finally able to get this working by using flex/lua from the updated artifacts. After hours of trouble shooting, it's a relief, I'm sure you know the feeling. Thank you again.

[lonvia]

Good to hear. Now the interesting question is if that means we need to bundle two versions.

@mboeringa Do you mind testing if the Windows-2025 build from that link works with your Windows 10 installation?

[majesticpdx]

One possibility is to due a beta version with the new to see if it is breaking with other versions of Windows.

[mboeringa]

@lonvia . The 'osm2pgsql-win64-windows-2025' version seems to run fine on my fully updated Windows 10 22H2, build 19045.5737. I can't vouch for older versions of Windows 10 of course. My postgresql database runs on a local network Windows Hyper-V virtual machine with Ubuntu 24.04 as the guest operating system where postgresql is installed, but that all shouldn't matter.