Turf server(s) stop responding when new round starts

This issue was originally reported as related to Critical Turf Server or API Issue.
Status
closed
Resolution
fixed
Reported by
Kingslayer
Date submitted
2014-04-07 15:54
Issue ID
#1244

Steps to reproduce

Try access Turf just when a new round has started.

Description

When a new round starts at 12:00 CET first Sunday of the month the turf server(s) stop responding for at least ten, sometimes up to 40 minutes (this last Sunday, about 30 minutes). Frequently the time after server(s) become available the system is very slow and unresponsive for a number of additional hours. I suggest that each round ends an hour earlier - at 11:00 CET and that any active users are disconnected at that time. This will allow you to, in an orderly fashion 1. Run the script that updates the fairy 2. Run the script that resets all zones 3. Apply whatever fixes and updates you may want to apply. 4. Reboot the servers 5. Open up the new round for users at 12:00

Attachments

No attachments.

Related issues

No related issues.

Responses

TBIT

Intresting idea!

KPD
  • Also affected
  • Thinks it is important
kaninmage
  • Also affected
  • Thinks it is important
Tessiz89
  • Also affected
  • Thinks it is important
bobyork
  • Also affected
  • Thinks it is important

If you take a zone during sunday it sometimes gets green for you, but will not be blocked, the revisit time is only 20h and others see another owner of the zone. (Above is something that might help to track down the cause, or it isn't. I add it anyway) I think Kingslayers idea is interesting and maybe something to at least test at the end of this round?

Iceeman
  • Also affected
  • Thinks it is important
mortuus
  • Also affected
  • Thinks it is important

This is a very serious issue that has been known for a long time, its the number of users that are crash the servers and scripts probably.

TBIT

Fixed by Simon :-)

Add comment or attachment

Comments or attachments cannot be added to this issue. If you think that this issue is not solved properly, please submit a new issue.