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
Error 500 when downloading relations for a way #1354
Comments
|
I wasn't able to reproduce this, but conditions on the server may be different now than they were an hour ago. Transcribing the error image:
Looks from this Rails issue like the problem might be that the database connection is not cleaned up properly after hitting a timeout? |
|
I reproduce this bug easily: by clicking on the link above, and then refreshing the page. Error message: ActiveRecord::StatementInvalid: PG::DuplicatePstatement: ERROR: prepared statement "a4" already exists |
|
I didn't say that the bug could not be reproduced, nor that you weren't able to reproduce it - only that I wasn't able to reproduce it. I've tried again today, and I'm still not able to reproduce it. Previously, I was using Did you hit a timeout the first time the page loads, or did it load okay? |
|
It's okay, I don't doubt it is hard to reproduce this issue. |
Just for the record, I ran into similar http 500 issues today with some relations while accessed from overpass turbo via the links displayed in the result window. The behaviour seems inconsistent, sometimes it fails, sometimes it doesn't. I did notice the significant lag in showing the relation too. E.g. when I try opening this URL which points to the relation of the Canary Islands archipelago, I initially got a consistent 500 error: However, now I am able to open it, but it is slow. Of course, this is not entirely unsurprising given the size of the objects involved in the relation and the number of them, so it may just be a time-out thing... |
Are you getting the same error message about a prepared statement? |
|
@pnorman , this was following a link from the overpass turbo result page showing the map result in the right pane of the tool. It normally simply opens up the OpenStreetMap website with the relation selected, as you can see from the link. However, this time, instead of opening up the page, I got an OpenStreetMap website error page with logo and a statement about "contacting the OpenStreetMap community" about this http 500 error. As said, the first few times I tried it failed, but now I can open it and see the relation result on the OpenStreetMap website. |
Probably unrelated to this issue then. |
|
Has anyone seen this error since #1381 was merged (2nd Dec 2016)? I'm trying to figure out if that might have been the same error, but I didn't explicitly link in this ticked from the PR at the time. And now I've forgotten whether they were related... |
|
@zerebubuth , I haven't used the OpenStreetMap website's options for showing relations and other map data enough lately to say something definitive. However, when I just tried to open the Canary Island's relation that I linked in one of the previous posts, I had no trouble doing so in both Firefox and Edge browser. The relations opened fine in both browsers (albeit a bit sluggish, but that is unsurprising giving the data). EDIT: |
|
I don't get that error on the link from the opening message. Maybe I'm not patient enough: it takes several minutes to get the result. |
Yes, it's unrelated since you are talking about a different server running different software operated by different people giving a different error. This issue is about an error which mentions prepared statements, not a general timeout The way to show this is fixed is to get an earlier version of the code, trigger the error (probably by forcing a timeout somehow), and then that the new version doesn't trigger that. I don't see that happening and don't think it's worth the effort. I recommend closing as some combination of fixed and cannot reproduce anymore, and it can be reopened if prepared statement errors reoccur. |
http://api.openstreetmap.org/api/0.6/way/120036484/relations
First time works, but after subsequent calls (Cmd+R, Cmd+R etc) it displays an error.
The text was updated successfully, but these errors were encountered: