[Tile-serving] [osm2pgsql] OSM2PGSQL Crashes on Windows Server 2008 (#117)

[jeffjanes]

"unexpected EOF on client connection with an open transaction. could not receive data from client"  means that postgres lost contact with the client (osm2pgsql), mostly likely because osm2pgsql died unexpectedly.  The further comment "No connection could be made because the target machine actively refused it." sounds bogus to me as there is no way for postgresql to be actively trying to (re)establish a connection.  I suspect that the facility to expand an errno to an errstring (which is in the domain of neither postgresql nor osm2pgsql--it is probably in glibc or analogous library) is doing something bad on Windows.  In other words, ignore the "actively refused" part, it is not useful to your debugging efforts.

---
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/osm2pgsql/issues/117#issuecomment-33416105
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tile-serving/attachments/20140127/68e36704/attachment.html>