Rapid: you may need to restable your games

[jK]

At the weekend again something went wrong in Apache and it ate too much memory, locking the system.
During this time the server's versions.gz was corrupted and needed to be reseted to a version from April 16th. This means any versions since that may be not available anymore.

So when you experience such issues please restable your game.

[Jools]

Ah, true xta:stable has gone from 9.739 to 9.738. How do you re-stable a version when there have been commits to the repo since then? There must be a better way that reverting all, committing a stable and then restore reverts from some backup.

Not directed specifically at jK, but at anyone who knows...

[knorke]

How do you re-stable a version when there have been commits to the repo since then? There must be a better way that reverting all, committing a stable and then restore reverts from some backup.

For currently-newest-playable version think easiest is just to make new commit:
for ex. for XTA: VERSION{9.74} instead of trying to restore the lost XTA 9.739

Or you mean for having the old mod-versions downloadable for replays etc?

[Jools]

Both. New version should be done anyway to get rid of easter stuff, but also in principle, what to do in these situation if that would not be there preferable option.

Versions are accessbible from springfiles, but at the moment people that will join from weblobby can't get the most recent version automatically.

[abma]

thats weird, the svn sync is only run when system load is below 4.

(todo: create backup it seems)

[abma]

for the curious:
any clue what caused the memory-leak?

also its possible that the upload webinterface to rapid broke the file as there exists no locking/atomic write, etc. which avoids a broken versions.gz.

[Silentwings]

I don't know what a "restable" requires. Info please?

[Jools]

I thought it was explained quite well. Something happened with rapid, causing the stable tag to be invalid. It was restored from backup, so new stable tag is one that was committed before April 16th. So you need to make a new stable version if that version is not acceptable.

[Silentwings]

My question (as it states) is how to restable the "lost" stable version & not how to commit a new stable version.

[knorke]

My question (as it states) is how to restable the "lost" stable version & not how to commit a new stable version.

After a test (see end of post) I am not sure of this post makes sense.
My idea was this:
1) Download http://packages.springrts.com/versions.gz
unzip, open with text editor.
This is the file that was "reseted to a version from April 16th" (?)

2) Look which versions of BA are in there or not.
The versions seem to be in bit random order, maybe because sometimes it is ba:revision:xxxx and sometimes ba:version:x.xx

line 610 ba:revision:2200,817ddd4eb34dc1e391ec74a6f7a7c299,,Balanced Annihilation V7.93

line 619 ba:revision:2217,7b6bab842cbe0f66aedd852537c5f6e4,,Balanced Annihilation V7.94

line 1087 ba:version:7.72,6fb305594ab58b0cdb56f3f0e9f3cb7a,,Balanced Annihilation V7.72

So anything not in there is "lost"?
Either way, (currently latest) BA 7.99 is appearently NOT there.

2b) Somehow figure out the rapid file-dust filename ( http://springrts.com/wiki/Rapid#an_index_archive:_.sdp )
Delete it, and see if lobby can re-download it or not.

3) http://packages.springrts.com/builds/ still has ba-V7.99.sdz
So all the files still exist - just rapid has forgotten where?
Download the missing versions as .sdz

4) Try to reupload the .sdz with original version/tag on http://packages.springrts.com/
Hope that it does not block that...?


----
Hm, while writing I found out that is appearently wrong?
In the versions.gz I can not find BA chicken defense 3.09, so I thought it should not be downloadable.
But springlobby just downloaded it...

Also in springlobby search, it finds BA 7.99 (see attachment)
But in versions.gz I can find no BA 7.99
Or is that a different download system? (plasma?)

[Jools]

Better to release a new stable.