Bug: TopicSaveError2

After using the TWiki without problems for a couple of weeks, I got this error message:

---

Topic save error

During save of file Unix.WebHome an error was found by the version control system. Please notify your TWiki administrator.

/usr/bin/ci -l -q -mnone -t-none -d'2003/02/20 15:45:00' -w'AndreasRother' /usr/local/httpd/twiki/data/Unix/WebHome.txt /usr/local/httpd/twiki/data/Unix/WebHome.txt,v 2>&1
ci: RCS file /usr/local/httpd/twiki/data/Unix/WebHome.txt,v is in use

Go back in your browser and save your changes locally.

---

I checked with lsof, but the mentioned file was not used by any process. However, I can reproduce this message, when I switched to user wwwrun and manually run the command above. Another strange thing is that some of the "*.txt,v" files do not have write perms for the owner wwwrun. I fixed it manually by running chmod u+w * in the directory. The are no file starting with , as mentioned in the other TopicSaveError Bugreport.

---

/var/log/httpd/error_log:

Thu Mar 13 12:55:50 2003] [error] [client 192.168.135.212] File does not exist: /usr/local/httpd/htdocs/urlpath/to/twiki/bin/oops/TWiki/TWikiRegistration

---

/var/log/httpd/access_log

192.168.135.212 - AndreasRother [13/Mar/2003:12:55:50 +0100] "POST /twiki/bin/save/Unix/WebHome HTTP/1.1" 302 5
192.168.135.212 - - [13/Mar/2003:12:55:51 +0100] "GET /twiki/bin/oops/Unix/WebHome?template=oopssaveerr&param1=/usr/bin/ci%20-l%20-q%20-mnone%20-t-none%20-d'2003/02/20%2015:45:00'%20-w'AndreasRother'%20/usr/local/httpd/twiki/data/Unix/WebHome.txt%20/usr/local/httpd/twiki/data/Unix/WebHome.txt,v%202%3E%261%3Cbr%20%3Eci:%20RCS%20file%20/usr/local/httpd/twiki/data/Unix/WebHome.txt,v%20is%20in%20use%3Cbr%20%3E HTTP/1.1" 200 1742

---

Test case

Environment

TWiki version:	01-Feb-2003
TWiki plugins:	no additional plugins enabled
Server OS:	SuSE Linux 8.0
Web server:	Apache 1.3.23
Perl version:	5.6.1
Client OS:	SuSE Linux 7.3 (sparc)
Web Browser:	Mozilla 1.2.1

-- AndreasRother - 13 Mar 2003

Follow up

This can happen when the permissions on the file being written to are wrong, and the locks get screwed as a result. If the installation procedures are followed carefully, it doesn't happen. I can't reproduce it either, and it's been sitting here for over a year now so I'm rejecting it.

-- CrawfordCurrie - 20 Jul 2004

Fix record