Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

always "The server is too busy at the moment." - why? #5306

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments
Closed

always "The server is too busy at the moment." - why? #5306

openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments

Comments

@openstreetmap-trac
Copy link

Reporter: aseerel4c26
[Submitted to the original trac issue database at 9.40am, Thursday, 16th April 2015]

(this was triggered by https://help.openstreetmap.org/questions/42332/server-busy-error-when-its-really-not )

... we could not find a time when the server was not busy. I re-tried (small, not densely-mapped areas to PDF or JPG) last night after 0 UTC which was a very quiet period on http://munin.openstreetmap.org/openstreetmap/yevaud.openstreetmap/load.html

Questions:

  1. Is yevaud still the server which does the exports? If not, which server? Munin link?
  2. Is 25 still the correct load limit for export availability?

I think it would be okay to say that we just do not have the capacity to do export, but always (if it never works) saying "wait a few minutes" is not really helpful.

Thank you!

@openstreetmap-trac
Copy link
Author

Author: TomH
[Added to the original trac issue at 1.54pm, Thursday, 16th April 2015]

Is this really still an issue? We replaced the load limit by a CPU idle time limit last week and as far as I know it should be fine now other than in the very busiest periods.

@openstreetmap-trac
Copy link
Author

Author: TomH
[Added to the original trac issue at 1.55pm, Thursday, 16th April 2015]

BTW as far I as I know the load limit was never 25.

@openstreetmap-trac
Copy link
Author

Author: TomH
[Added to the original trac issue at 1.59pm, Thursday, 16th April 2015]

Looks like there was an error in the new text - fixed in [changeset:372c2f7/chef].

@openstreetmap-trac
Copy link
Author

Author: aseerel4c26
[Added to the original trac issue at 7.39pm, Thursday, 16th April 2015]

Replying to [comment:3 TomH]:

Looks like there was an error in the new text - fixed in [changeset:372c2f7/chef].

Nice, thank you very much, Tom! Seems to work even during "busy" daytimes (tried twice with one hour in-between).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant