Opened 12 years ago

Closed 12 years ago

#447 closed defect (fixed)

frequent 500 internal server error messages

Reported by: frederik@… Owned by: steve@…
Priority: major Milestone:
Component: api Version:
Keywords: 500 internal server error Cc:

Description

When uploading changes from JOSM, on average one in 200 calls fails with "500 internal server error". Immediate retry is then successful.

At one time, I had two parallel uploads running with JOSM, and they both failed at exactly the same time - it may just have been coincidence but may also be a sign of some inter-process or inter-thread problem at the server?

Change History (2)

comment:1 Changed 12 years ago by writetodan@…

this ticket on server restarts is probably relevant: #434

as might be this info from Steve on ML:

HTTPISE 500's. The server is running lighthttpd on top of fcgi using  
the script/process scripts. These are running with 3 threads with a  
restart time of 2 seconds. The threads commit suicide after some  
number of requests (which I will increase in a sec) to either the map  
or gpx call. When that happens, lightttpd and fcgi are supposed to  
pause the queue of requests (which may or may not be api requests).  
My suspicion is that the queue is getting killed (and thus a bunch of  
500's) instead.

Looking through the logs the rails stuff itself is not producing the  
500s, its somwthing to do with the threads killing themselves.

comment:2 Changed 12 years ago by Tom Hughes

Resolution: fixed
Status: newclosed

The server no longer needs to restart all the time as the memory leaks have been dealt with.

Note: See TracTickets for help on using tickets.