Skip to content
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

The OSRM server returned an error: #60

Closed
alfdbe opened this issue Jun 10, 2020 · 10 comments
Closed

The OSRM server returned an error: #60

alfdbe opened this issue Jun 10, 2020 · 10 comments

Comments

@alfdbe
Copy link

alfdbe commented Jun 10, 2020

I have been trying to re-run a script which ran great a few weeks ago, but now when I call osrmIsochrone() it returns

The OSRM server returned an error: Error: lexical error: invalid char in json text. <!DOCTYPE HTML PUBLIC "-//IETF/ (right here) ------^

I also noticed that the web app hosted at https://www.r-bloggers.com/shiny-app-drive-time-isochrones/ no longer works either? Any ideas would be great.

@rCarto
Copy link
Member

rCarto commented Jun 11, 2020

I can confirm the issue with the demo server. Not with my own instance.
It may have something to do with Project-OSRM/osrm-backend#5655

@rCarto
Copy link
Member

rCarto commented Jun 11, 2020

That's it. osrmIsochrone() relies on a heavy use of the table service from OSRM. Owners of the demo server have probably added a limit on table queries. The dev version of the package should fix the issue.
Can you please test the dev version (remotes::install_github("rCarto/osrm")) and report if the problem is fixed.

@alfdbe
Copy link
Author

alfdbe commented Jun 11, 2020

Yep that fixed it. Works perfectly now. Thanks for your help!

@alfdbe alfdbe closed this as completed Jun 11, 2020
@rCarto
Copy link
Member

rCarto commented Jun 12, 2020

Thank you for your feedback. I'll release an updated version as soon as possible.

@shriv
Copy link

shriv commented Jun 23, 2020

Hi there,
I installed osrm from github and still run into this issue. I've tried a 5s ping and still get this error. Any ideas when / if the server will be able to take on more load?

Thanks!

@rCarto
Copy link
Member

rCarto commented Jun 23, 2020

That's right. The OSRM demo server is a new one and may be more, or less robust than the previous one. I've added a way for the package to repeat the request till the demo server respond with the results. It should work again.
Note that the demo server is a demo server, it should not be intensively used. If your work relies heavily on OSRM I would suggest to use your own instance via docker containers.

@rCarto rCarto reopened this Jun 23, 2020
@rCarto rCarto closed this as completed in f4c8552 Jun 23, 2020
@jlopezper
Copy link

I still have this issue, even after installing the dev version.

Thanks!

@rCarto rCarto reopened this Jul 1, 2020
@rCarto
Copy link
Member

rCarto commented Jul 2, 2020

Hum...
I don't see that, neither with the demo server, nor with a local OSRM server, nor with my remote OSRM server...

@jlopezper
Copy link

I'm sorry, I'm not able to reproduce the error. It just works now.
Thanks and apologies

@rCarto
Copy link
Member

rCarto commented Jul 3, 2020

No problem, it's not bad news :-)

@rCarto rCarto closed this as completed Jul 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

4 participants