Page 1 of 1

JoomlaCode: attempt to write to readonly database

Posted: Sun Nov 15, 2009 5:30 pm
by slabbi
Hi,

I get this error when I try to commit files? When I browse my projects using the web interface they seem to be empty?!?

Regards,
slabbi
--
uddeIM HQ

Re: JoomlaCode: attempt to write to readonly database

Posted: Mon Nov 16, 2009 8:08 am
by spauldingsmails
Yeah just started to get the exact same problem. Would be good to get some information on whether this issue is being addressed.

Re: JoomlaCode: attempt to write to readonly database

Posted: Mon Nov 16, 2009 8:28 am
by brad
I've asked Sam to take a look at this for you.

Thanks for your patience.

Re: JoomlaCode: attempt to write to readonly database

Posted: Mon Nov 16, 2009 9:30 am
by julienV
same problem on joomleague svn: http://joomlacode.org/svn/joomleague/

Re: JoomlaCode: attempt to write to readonly database

Posted: Mon Nov 16, 2009 10:09 am
by NiGHtyWolf
Same problem on show component http://joomlacode.org/gf/project/show/

Re: JoomlaCode: attempt to write to readonly database

Posted: Mon Nov 16, 2009 10:38 am
by Polski
Any sort of official word on this? A rough timeline as to when we have might have access again to the repos and of course confirmation that the repos are all still really there...

Re: JoomlaCode: attempt to write to readonly database

Posted: Mon Nov 16, 2009 1:04 pm
by pasamio
JoomlaLeague looks fine to me, its reporting revision 4223 via that URL that you post. However I see that the ViewVC must be broken for some reason and is reporting incorrectly. In fact its reporting completely fictitious looking results instead of returning something sane like an error message. Not sure what the go is there but I'll have a look. I wouldn't be worried, just ViewVC is broken, all of the data is still there. It looks suspiciously like its not getting past the first revision for what ever reason. Version 1.1.2 also seems to exhibit the same behaviour so its rather weird.

Additionally, there is a bug in Subversion that is being regularly hit by JoomlaCode two an hour and there is nothing much I can do to fix that beyond shifting back to Subversion 1.2; this results in a periodic forbidden error. JoomlaCode regenerates its access control information on the 14th and 44th minutes of the hour, so if you try to avoid those periods approximately.

Re: JoomlaCode: attempt to write to readonly database

Posted: Mon Nov 16, 2009 2:36 pm
by julienV
what is weird about joomleague issue is that checking out the code works fine, it's just committing that fails... (well, the reported problem is readonly database, so not so surprising after all)

EDIT: it works now... thanks !

Re: JoomlaCode: attempt to write to readonly database

Posted: Mon Nov 16, 2009 3:54 pm
by spauldingsmails
Yep, working for me too. Thanks for the quick resolution.

Re: JoomlaCode: attempt to write to readonly database

Posted: Tue Nov 17, 2009 9:04 am
by NiGHtyWolf
Nice, it works fine now. Thanks for your good job. Hope that the online ViewVC gonna be resolved also.

Keep going :)

All for Joomla, Joomla for all!

Re: JoomlaCode: attempt to write to readonly database

Posted: Thu Nov 19, 2009 7:30 pm
by slabbi
Well, commits and checkouts work now but the web interface is still broken. I do only see

http://joomlacode.org/gf/project/com_ud ... e&path=%2F

Code: Select all

File 	Rev. 	Age 	Author 	Last log entry
branches/ 	 1 	 4 days 	 root 	 Initial Repository Skeleton
tags/ 	 1 	 4 days 	 root 	 Initial Repository Skeleton
trunk/ 	 1 	 4 days 	 root 	 Initial Repository Skeleton
:(

Re: JoomlaCode: attempt to write to readonly database

Posted: Fri Nov 20, 2009 5:09 am
by pasamio
As noted above, ViewVC is broken. Not sure why, but it is. The latest version of ViewVC is also broken, again, not sure why. Takes a lot of time to debug code that isn't your own when you aren't sure what you are looking for. In this case I have the distinct feeling ViewVC wrote their own parser code which is choking on something.

It is also noted here: http://community.joomla.org/blogs/commu ... nance.html

When I get some time to work out what is wrong - which in the grand scheme of things is relatively small, most write services are in tact and only a few read services are impacted.