Skip to Content.
Sympa Menu

overpass - Re: [overpass] transaction log: read_aborted()

Subject: Overpass API developpement

List archive

Re: [overpass] transaction log: read_aborted()

Chronological Thread 
  • From: Roland Olbricht <>
  • To:
  • Subject: Re: [overpass] transaction log: read_aborted()
  • Date: Fri, 6 Sep 2019 21:22:56 +0200


Is there a way to diagnose why the query was aborted? i.e. did it cross some
query time to run threshold setting.

A quer is aborted if ot has been killed by something externally. There
are some but rather uncommon cases where this has been triggered by
ulimit. By contrast, it is most likely that the web server has killed

If the request has missed the quota then it leaves a message 'Oversized'
or 'timed out' respectively in the log files.

I found purge_setting initialised to 900. But I couldn't figure out how it was
being used.

I have never heard so far the term 'purge_setting'. Is this really from
Overpass or from somewhere in the web server or OS stack?

Also, there doesn't seem to be an http response. I don't see anything in the
nginx logs either.

Sounds even more like something external. Oversized and timed out are
designed to return an error message as part of their payload body.
Essentially because once the process has started to write payload, it
cannot rollback and declare an error.

Best regards,


Archive powered by MHonArc 2.6.19+.

Top of Page