SourceForge Dec 2004 Upgrade Issue

SourceForge upgraded the hardware over the last weekend. I noticed that we have strange topic changes. The WebChanges shows topics changed, but if you look at a recently changed topic it is still at the previous version/author.

Example:

• UseModWiki is shown in WebChanges as 07 Dec 2004 - r1.3 - SamHasler
• It is shown in raw=debug as 1102431180 (07 Dec 2004) - r1.3 - SamHasler
• Its RCS Revision is shown as 04 Feb 2002 - r1.2 - 00:28 - LesOrchard

After some debug I found that the lock user has changed from nobody to nfsnobody which causes the trouble. Here are the details:

-bash-2.05b$ cd Sandbox/
-bash-2.05b$ la PetersTest.txt*
-rw-r--r--    1 nfsnobody nfsnobody     1795 Aug  5 13:53 PetersTest.txt
-r--r--r--    1 nfsnobody nfsnobody     4626 Aug  5 13:53 PetersTest.txt,v
-bash-2.05b$ head PetersTest.txt*
==> PetersTest.txt <==
This is a link to WebNotify and a BrandNewPageToo

        * test: <br />
         <img src="%ATTACHURLPATH%/logo.gif" alt="test"  width="46" height="50"  />

About !VxWorks

link to [[WebNotify][notify]]

==> PetersTest.txt,v <==
head    1.10;
access;
symbols;
locks
        nobody:1.10; strict;
comment @# @;


1.10
date    2004.08.05.20.52.06;    author PeterThoeny;     state Exp;
-bash-2.05b$
-bash-2.05b$ # after edit/save with one additional line
-bash-2.05b$
-bash-2.05b$ la PetersTest.txt*
-rw-r--r--    1 nfsnobody nfsnobody     1810 Dec  8  2004 PetersTest.txt
-r--r--r--    1 nfsnobody nfsnobody     4629 Dec  8  2004 PetersTest.txt,v
-bash-2.05b$ head PetersTest.txt*
==> PetersTest.txt <==
This is a link to WebNotify and a BrandNewPageToo

        * test: <br />
         <img src="%ATTACHURLPATH%/logo.gif" alt="test"  width="46" height="50"  />

About !VxWorks

link to [[WebNotify][notify]]

==> PetersTest.txt,v <==
head    1.10;
access;
symbols;
locks
        nfsnobody:1.10; strict;
comment @# @;


1.10
date    2004.08.05.20.52.06;    author PeterThoeny;     state Exp;
-bash-2.05b$
-bash-2.05b$ # after one more save (no additional change)
-bash-2.05b$
-bash-2.05b$ la PetersTest.txt*
-rw-r--r--    1 nfsnobody nfsnobody     1810 Dec  8  2004 PetersTest.txt
-r--r--r--    1 nfsnobody nfsnobody     4650 Dec  8  2004 PetersTest.txt,v
-bash-2.05b$ head PetersTest.txt*
==> PetersTest.txt <==
This is a link to WebNotify and a BrandNewPageToo

        * test: <br />
         <img src="%ATTACHURLPATH%/logo.gif" alt="test"  width="46" height="50"  />

About !VxWorks

link to [[WebNotify][notify]]

==> PetersTest.txt,v <==
head    1.10;
access;
symbols;
locks
        nfsnobody:1.10; strict;
comment @# @;


1.10
date    2004.08.05.20.53.06;    author PeterThoeny;     state Exp;

This is bad since:

• After the first save, topic text (and META:TOPICINFO) is at latest change, but RCS is at previous revision
• After second change both are in sync, but at the previous timestamp and revision! (This probably only happens because I saved again within one hour and I was the editor of the previous version)

For now: Please save your changes two times to work around this issue!

I will file a SF support request.

-- PeterThoeny - 09 Dec 2004

How about just re-locking the topics to 'nfsnobody', or is it more complex than that?

-- RichardDonkin - 09 Dec 2004

Yes, that is the idea. However we can't do that since we do not have root. This needs to be done for data and pub in all TWiki installations on TWiki.org. I just finished a backup and filed a support request, http://sourceforge.net/tracker/index.php?func=detail&aid=1081970&group_id=1&atid=200001

-- PeterThoeny - 09 Dec 2004

ummm, couldn't the recently deprecated manage?action=relockrcs be used? It doesn't need root.

-- MattWilkie - 09 Dec 2004

OOPS! I meant to just suggest using relockrcs, and put it in as a full URL. Then I wondered if I needed to nop it. So I clicked on it, expecting to get a "you must be an admin" message. I didn't. As I write, 1,150 topics in Codev have been relocked already. We shall soon see the results I suppose.

-- MattWilkie - 09 Dec 2004

okay, all of Codev is done, however it stopped a shortways into Main - only 350 topics processed. I have the list of finished topics if anybody wants it.

-- MattWilkie - 09 Dec 2004

3300 Codev, 64 Core, 119 Know, and 350 Main topics processed

-- MattWilkie - 09 Dec 2004

Matt, there was no need for that because SF support already did that this morning. Please check the SF support ticket. Tail on time stamp in Main web is Dec  9 05:42, so that command executed OK.

Hmm, the manage?action=relockrcs is very bad. I did not know that there was no security . I commented out the code.

It looks like we have an rcs corruption issues, see SimplerMailNotification, last editor is now nfsnobody.

-- PeterThoeny - 09 Dec 2004

The SimplerMailNotification.txt,v starts with this:

head    1.14;
access;
symbols;
locks
        nfsnobody:1.14; strict;
comment @# @;


1.14
date    2004.12.09.21.12.06;    author nfsnobody;       state Exp;

You can see that author is incorrectly set to nfsnobody

-- PeterThoeny - 09 Dec 2004

oh, my bad. I have a tendency to ignore timestamps because of time zone confusions.

As far as the last author corruption. I see the same thing on a lot of the docs in the TWiki web on my site. I had assumed it was something to do with UpgradeTWiki. Maybe not. Now that I look more closely, I see there is a discrepancy in versions on some pages too. At http://yukongis.ca/bin/view/TWiki/CommentsTmpl the top of the page says "TWiki.CommentsTmpl r1.3 - 04 Oct 2004 - 23:24 - Main.nobody" while the bottom says "Revisions: | r1.1 |".

the version history for that page starts like:

head -30 CommentsTmpl.txt,v
head    1.3;
access;
symbols;
locks
        nobody:1.3; strict;
comment @# @;


1.3
date    2004.10.05.06.24.09;    author nobody;  state Exp;
branches;
next    1.2;

1.2
date    2004.09.10.05.00.05;    author nobody;  state Exp;
branches;
next    1.1;

1.1
date    2004.08.08.03.02.49;    author PeterThoeny;     state Exp;
branches;
next    ;

head -3 CommentsTmpl.txt:

%<nop>META:TOPICINFO{author="PeterThoeny" date="1091934169" format="1.0" version="1.1"}%
%<nop>META:TOPICPARENT{name="CommentPlugin"}%

There are also a growing number of pages in the Support web about broken diffs.

-- MattWilkie - 10 Dec 2004

There is something bad with the manage?action=relockrcs code. I could verify that the backup I did yesterday had the correct author TomWhite for TikiWiki (1.19 date    2004.02.10.15.16.18;    author TomWhite;        state Exp;), now it is nfsnobody (1.20 date    2004.12.09.21.10.47;    author nfsnobody;       state Exp;)

These are the topics with broken RCS author, only topics in Codev are affected: DifferentSecurityLevelsInSameTWikiInstallation, EncodeURLsWithUTF8, ExampleLogoutPage, FileAttachmentsBugWithOnlyTwoVersions, GoIsSearch, IncludeHttpIsVerySlow, InternationalisationIssues, LocationLocationLocation, LoginNamesShouldNotBeWikiNames, ObfuscateEmailAddresses, PluginsCompileTimes, PostCairoDevelopmentModel, RecognisedButUnregisteredUsers, RegisterCgiScriptRewrite, ShorterURLs, SimplerMailNotification, StarOffice, SubmitTopicByBloggerApi, SubversionChangesFromCVS, SubversionReadme, SushiWiki, TheBrainVsTwiki, TikiWiki, TrashButton, TWikiDevelopmentStartingKit, TWikiDotOrgIsATerribleAdvert, TWikiKernel, TWikiPublicityAtFreshmeat, TWikiSecurityAlertProcess, TWikiVsWorld, TWikiVsXWiki, UltimateBulletinBoard, UltimateBulletinBoardVsTWiki, UseModWiki, ViewRawTopic, WebStatistics, WiiskiWiki, WikiClonesDirectory, WikiUserTypes

-- PeterThoeny - 10 Dec 2004

curious, why only those topics? why not all of them?

-- MattWilkie - 10 Dec 2004

Probably those topics that changed recently since the SourceForge hardware upgrade.

-- PeterThoeny - 10 Dec 2004

Moved follow-up on relockrcs to RelockingRCSFiles.

-- MattWilkie - 10 Dec 2004