You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Rainer Sokoll <R....@intershop.de> on 2007/08/10 14:43:02 UTC
Re: "connection closed unexpectedly" and/or "not authorized to
open root of edit operation"
On Fri, Aug 10, 2007 at 07:26:50AM -0700, Jason Huck wrote:
> Whenever I try to connect to the repository now, even just to get a
> list of commits, whether from the command line, SVNX, Subclipse,
> Subversive, or TortoiseSVN, I get a string of messages like this:
>
> svn: Network connection closed unexpectedly
> svn: Malformed network data
> svn: Network connection closed unexpectedly
> svn: Network connection closed unexpectedly
> svn: Network connection closed unexpectedly
> svn: Network connection closed unexpectedly
> svn: Network connection closed unexpectedly
> svn: Connection reset
> svn: Authorization failed
Can you sniff the traffic with e.g. wireshark to see if this is a
network related problem?
You could also test from localhost - does it work without problems?
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: "connection closed unexpectedly" and/or "not authorized to open
root of edit operation"
Posted by Vlad Georgescu <vg...@gmail.com>.
Jason Huck wrote:
>
> Rainer Sokoll wrote:
>> On Fri, Aug 10, 2007 at 07:57:01AM -0700, Jason Huck wrote:
>>
>>> behavior. The other two seem fine. I use the Berkeley DB setup. Could
>>> there
>>> be some corruption there or perhaps a write-lock issue of some sort?
>> Maybe. I've never used bdb.
>> What if you export the repo in mention and import it into a FSFS repo?
>>
>> Rainer
>>
>>
>
> Just tried that. Didn't help, but, after doing it, I realized that the
> problem has something to do with authz. I've got two groups defined, and one
> group has r/w perms on the whole repo, while the other has read-only perms
> on just one folder within the repo. Have the rules for this changed in
> recent versions of Subversion? When I make perms wide open, everything works
> normally (in both the old and new versions of the repo), but obviously I
> can't leave it that way.
One known cause of the "Not authorized to open root of edit operation"
error is issue #2712 (which has been fixed in trunk, but not yet
backported to 1.4.x):
http://subversion.tigris.org/issues/show_bug.cgi?id=2712
Is anon-access set to "read" in the repositoy's svnserve.conf file?
If it is, and you don't want to allow anonymous users, you can set it to
"none" as a workaround.
--
Vlad
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: "connection closed unexpectedly" and/or "not authorized to open
root of edit operation"
Posted by Jason Huck <ja...@gmail.com>.
Rainer Sokoll wrote:
>
> On Fri, Aug 10, 2007 at 09:51:28AM -0700, Jason Huck wrote:
>
> Hi,
>
>> Just tried that. Didn't help, but, after doing it, I realized that the
>> problem has something to do with authz. I've got two groups defined, and
>> one
>> group has r/w perms on the whole repo, while the other has read-only
>> perms
>> on just one folder within the repo. Have the rules for this changed in
>> recent versions of Subversion? When I make perms wide open, everything
>> works
>> normally (in both the old and new versions of the repo), but obviously I
>> can't leave it that way.
>
> You are getting closer :-)
> You did not mention the trac version you use - could you do that,
> please?
> Also, you may post your authz file (anonymized, of course).
>
>
We're not using trac. We do have roundup running on the machine, but it's
not integrated with subversion.
Here's a generic rundown of the authz configuration:
---
svnserve.conf
---
[general]
anon-access = none
auth-access = write
password-db = /svn/svnusers
realm = My Repo
authz-db = /svn/authz
---
svnusers
---
[users]
UserA = 12345
UserB = 54321
UserC = 90210
UserD = 86753
---
authz
---
[groups]
main = UserA, UserB
sub = UserC, UserD
[repo:/]
@main = rw
[repo:/trunk]
@sub = r
Thanks,
Jason
--
View this message in context: http://www.nabble.com/%22connection-closed-unexpectedly%22-and-or-%22not-authorized-to-open-root-of-edit-operation%22-tf4248974.html#a12095959
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: "connection closed unexpectedly" and/or "not authorized to
open root of edit operation"
Posted by Rainer Sokoll <R....@intershop.de>.
On Fri, Aug 10, 2007 at 09:51:28AM -0700, Jason Huck wrote:
Hi,
> Just tried that. Didn't help, but, after doing it, I realized that the
> problem has something to do with authz. I've got two groups defined, and one
> group has r/w perms on the whole repo, while the other has read-only perms
> on just one folder within the repo. Have the rules for this changed in
> recent versions of Subversion? When I make perms wide open, everything works
> normally (in both the old and new versions of the repo), but obviously I
> can't leave it that way.
You are getting closer :-)
You did not mention the trac version you use - could you do that,
please?
Also, you may post your authz file (anonymized, of course).
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: "connection closed unexpectedly" and/or "not authorized to open
root of edit operation"
Posted by Jason Huck <ja...@gmail.com>.
Rainer Sokoll wrote:
>
> On Fri, Aug 10, 2007 at 07:57:01AM -0700, Jason Huck wrote:
>
>> behavior. The other two seem fine. I use the Berkeley DB setup. Could
>> there
>> be some corruption there or perhaps a write-lock issue of some sort?
>
> Maybe. I've never used bdb.
> What if you export the repo in mention and import it into a FSFS repo?
>
> Rainer
>
>
Just tried that. Didn't help, but, after doing it, I realized that the
problem has something to do with authz. I've got two groups defined, and one
group has r/w perms on the whole repo, while the other has read-only perms
on just one folder within the repo. Have the rules for this changed in
recent versions of Subversion? When I make perms wide open, everything works
normally (in both the old and new versions of the repo), but obviously I
can't leave it that way.
Thanks,
Jason
--
View this message in context: http://www.nabble.com/%22connection-closed-unexpectedly%22-and-or-%22not-authorized-to-open-root-of-edit-operation%22-tf4248974.html#a12095116
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: "connection closed unexpectedly" and/or "not authorized to
open root of edit operation"
Posted by Rainer Sokoll <R....@intershop.de>.
On Fri, Aug 10, 2007 at 07:57:01AM -0700, Jason Huck wrote:
> behavior. The other two seem fine. I use the Berkeley DB setup. Could there
> be some corruption there or perhaps a write-lock issue of some sort?
Maybe. I've never used bdb.
What if you export the repo in mention and import it into a FSFS repo?
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: "connection closed unexpectedly" and/or "not authorized to open
root of edit operation"
Posted by Jason Huck <ja...@gmail.com>.
I should also mention that I tried 'svnadmin recover ...' as the svn user. It
completed almost instantaneously, but made no difference.
- jason
--
View this message in context: http://www.nabble.com/%22connection-closed-unexpectedly%22-and-or-%22not-authorized-to-open-root-of-edit-operation%22-tf4248974.html#a12093349
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: "connection closed unexpectedly" and/or "not authorized to open
root of edit operation"
Posted by Jason Huck <ja...@gmail.com>.
Rainer Sokoll wrote:
>
> On Fri, Aug 10, 2007 at 07:26:50AM -0700, Jason Huck wrote:
>
>> Whenever I try to connect to the repository now, even just to get a
>> list of commits, whether from the command line, SVNX, Subclipse,
>> Subversive, or TortoiseSVN, I get a string of messages like this:
>>
>> svn: Network connection closed unexpectedly
>> svn: Malformed network data
>> svn: Network connection closed unexpectedly
>> svn: Network connection closed unexpectedly
>> svn: Network connection closed unexpectedly
>> svn: Network connection closed unexpectedly
>> svn: Network connection closed unexpectedly
>> svn: Connection reset
>> svn: Authorization failed
>
> Can you sniff the traffic with e.g. wireshark to see if this is a
> network related problem?
> You could also test from localhost - does it work without problems?
>
> Rainer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
>
Same issues from localhost. However, I have narrowed it down a little bit. I
use separate repositories for each project, but they all point to the same
svnusers and authz-db files. Only *one* of the three is exhibiting this
behavior. The other two seem fine. I use the Berkeley DB setup. Could there
be some corruption there or perhaps a write-lock issue of some sort?
Thanks,
Jason
--
View this message in context: http://www.nabble.com/%22connection-closed-unexpectedly%22-and-or-%22not-authorized-to-open-root-of-edit-operation%22-tf4248974.html#a12092789
Sent from the Subversion Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org