-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running osrm-routed getting error #3749
Comments
@billystalnaker could you give more information about your system and osrm configuration. there were some related regressions in boost 1.54 |
uname -a As far as osrm configuration I'm not sure what you want. We are using the car.lua profile. Hope that helps |
for osrm configuration i mean output of cmake with an empty cache: EDIT: The configuration is needed to cut off possible bugs in libraries. The exception must be handled at osrm-backend/include/server/server.hpp Lines 76 to 77 in cd1a73d
Don't know how reliable osrm server must be, because it is just a demo? |
Does that |
No it will just generate the Makefile and related files again. You can also use https://hub.docker.com/r/osrm/osrm-backend/tags/ and try if you have the same issues with it. @oxidase |
@billystalnaker the most important is the boost version . if boost libraries are installed as deb packages and used from the system than output of @daniel-j-h basically thread loop must contain try/catch around |
@daniel-j-h what do you mean by osrm-touted being a dev server? I was under the impression that this is the command to serve all requests to the osrm package.. I will take a look into the boost library on Monday |
No, |
In the quick start maybe it should say something like "If you're using this in production, then use node-osrm."? I was under the impression that we were good to go with just the |
Please bare with me on this. But I've installed |
You can do https://github.com/Project-OSRM/node-osrm/blob/master/example/server.js |
Hi, I ran osrm-routed on a north-america file and received this output:
I'm not sure how to handle this error. exact command:
osrm-routed -p 80 north-america-latest.osrm
The text was updated successfully, but these errors were encountered: