"Export process died" - but it didn't. #2163
Comments
|
hmmm, not seen this before. What does: apt-cache policy libmapnikGive? I worry you may have a conflicting mapnik version coming from: https://github.com/stevage/tilemill-server/blob/9027d8b147e72c0db91f74f42dba0fdd20b0510b/install-postgis.sh#L31 |
Do you have any suggested changes to my script? Happy to try them out... |
|
Hi Dane, I'm still getting this same issue, new servers with the latest version of my build scripts (which have no more kakrueger): https://github.com/stevage/saltymill Any ideas? No one else reports this? Again nothing suspicious in /var/log/tilemill.log: |
|
I presume given the exports are actually working fine there is some communication problem between the client and server. Perhaps it is just a delay of some sort that is triggering this.... |
|
Could you try putting a |
|
Thanks Dane. (Please ignore the 'check' and 'done' in the following |
|
thanks. can you also share the logs? and are you testing one export at a time or sending multiple? |
|
Sorry, that server's been rebuilt now so I can't immediately grab that output, but I just noticed something interesting while doing a command line export (which I didn't know existed): ... So, the export seems to crash right at the very end. |
|
thanks a lot for the further details. It looks like this is a symptom of mapnik/node-mapnik#251. So basically yes, the crash is during the exit and should not be happening. It has seemed like a minor problem but this case underlines why its not minor. |
|
Just mentioning that this is still happening on newly built servers (using apt-get install). Do you still want those logs? |
|
The most useful thing would be to test with the latest node v0.10.x version and see if it still occurs and if it does then try to document the simplest and most reliable way to replicate it. |
|
Ok, I've upgraded to NodeJS v0.10.29 and it still occurs with TileMill v0.10.1-293-g697c86c. Now, this is interesting. I set up a clean (Ubuntu Trusty) server and installed TileMill manually, rather than through my automatic deployment system (http://github.com/stevage/saltymill). The export failure doesn't happen. So that gives us something to work with. Most likely some kind of clash with salt, nginx, PostGIS, OSM2PGSQL or OSRM. I should be able to narrow it down further. |
|
If you are installing tilemill master (like I see you are doing here: https://github.com/stevage/saltymill/blob/master/tilemill/tilemillinstall.sls#L89), you don't anymore need to install an external mapnik because node-mapnik is shipped with standalone binaries. So, you should be able to remove all mapnik ppas and apt-get installs. |
|
FYI, I'm just installing the APT version, like so: |
|
sure, when installing the apt version its safer to do: But, I'm confused: the APT version is the one that has the problem but tilemill master with |
|
Narrowing it down even further, this configuration also produces the export failure: That is - the tile server is exposed directly to the world on port 5008, but the interface goes through HTTP auth from 5002 to 20009. I was really hoping this would work, because that's a configuration that would work for me. So...I think my question now becomes, "How can I make HTTP auth and map exports work at the same time?"
Everything I've reported in the last few days is from APT installs. My scripts for installing dev builds broke when I switched to using Trusty, so I haven't been able to test that. |
Good job narrowing it down. However this seems like something that will be tricky to debug and not something I feel like I have time to pursue right now. |
|
Understood. Do you happen to know if anyone else has made this work? How else do people run TileMill server-side without giving the whole internet access to their projects? |
No I don't.
The primary usecase of TileMill on servers is only for command line/batch rendering and not exports through the UI. So I think this bug has likely always exited and few if no others have run into it. |
|
SOLVED! :D Ok, it turns out that part of the problem was my misunderstanding of this line in /etc/tilemill/tilemill.config: I thought it had to be a publicly accessible URL (ie, presented to the browser), but I guess it's used for some internal facing services. So the simple solution for me is to leave TileMill running on 20009 locally, port forwarded through nginx on port 80 with HTTP auth, and to leave the config line as 20009: So I don't know if it's even a bug at this point, but just a kind of limitation: "coreUrl must be a locally accessible IP address and port combination that does not require any authentication". Thanks very much for your help in figuring it out. |
ghost
mentioned this issue
On some freshly built servers, all exports are failing with "Export process died":
Meanwhile, some of these exports have actually succeeded:
I don't see anything abnormal in the log:
The biggest problem here is there no download link for the exported image, so I need to actually SSH in to the server to get it.
Happy to provide more information if needed. Tilemill "Version 0.10.1 (v0.10.1)" installed using http://github.com/stevage/tilemill-server.
The text was updated successfully, but these errors were encountered: