You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Stephan Robotta <ro...@ontoprise.de> on 2009/07/30 09:06:13 UTC
RE: Subversion 1.6 on Fedora: Cannot resolve hostname
Hello,
By searching for a solution to my problem, I found this message from
David which apprarently seems the same that I have.
SVN worked well before but suddenly quits with "could not resolve
hostname". There havent been any changes in the configuration. So I
do not assume any proxy problem. This happend after an package update
on Fedora 11.
Resolving the hostname is not the issue, a wget or ssh login on the
repositories machine works well.
Any help will be appreciated.
Best regards, Stephan
RE: path based authorization issue
Posted by Bob Archer <bo...@amsi.com>.
> > A path based authorization configuration problem.
> > I have a rules file with content as follows:
> >
> > # -------------------------------------------------
> > [groups]
> > test = harry, sally
> >
> > [/]
> > * = rw
> >
> > [/trunk/org/secure]
> > @test =
> > # -------------------------------------------------
> >
> > I would expect that harry and sally have access to all but not
> > to 'secure'.
> > But: The result is, everyone has access to /trunk/org/secure.
> > In comparison, the following example runs as expected:
> >
> > # -------------------------------------------------
> > [/]
> > * = rw
> >
> > [/trunk/org/secure]
> > * =
> > # -------------------------------------------------
> >
> > I'm running Subversion 1.5.5, Apache 2.0.63 on Windows XP Prof.
> >
> >
> > Any hint?
>
> Have you tried using
>
> [/]
> $authenticated = rw
>
> instead of
>
> [/]
> * = rw
>
> ?
>
> I wonder if right now those users are falling back to gaining access as
> non-authenticated (anonymous) users.
I think also make sure you have anon_access set to nothing also. If you don't require authentication for read access them svn doesn't know who it is letting in an falls back to anon access settings.
BOb
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2377058
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
RE: path based authorization issue
Posted by "Todd C. Gleason" <tg...@impac.com>.
> -----Original Message-----
> From: Schroeder, Hartmut [mailto:Hartmut.Schroeder@plath.de]
> Sent: Thursday, July 30, 2009 9:36 AM
> To: users@subversion.tigris.org
> Subject: path based authorization issue
>
> Hi,
> A path based authorization configuration problem.
> I have a rules file with content as follows:
>
> # -------------------------------------------------
> [groups]
> test = harry, sally
>
> [/]
> * = rw
>
> [/trunk/org/secure]
> @test =
> # -------------------------------------------------
>
> I would expect that harry and sally have access to all but not
> to 'secure'.
> But: The result is, everyone has access to /trunk/org/secure.
> In comparison, the following example runs as expected:
>
> # -------------------------------------------------
> [/]
> * = rw
>
> [/trunk/org/secure]
> * =
> # -------------------------------------------------
>
> I'm running Subversion 1.5.5, Apache 2.0.63 on Windows XP Prof.
>
>
> Any hint?
Have you tried using
[/]
$authenticated = rw
instead of
[/]
* = rw
?
I wonder if right now those users are falling back to gaining access as
non-authenticated (anonymous) users.
Another thing you could try might involve some variant of using ~@test
to allow access to everyone other than the test group. So maybe
[/trunk/org/secure]
* =
(or $authenticated = )
~@test = rw
See also http://svn.haxx.se/users/archive-2009-06/0804.shtml .
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2377051
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
path based authorization issue
Posted by "Schroeder, Hartmut" <Ha...@plath.de>.
Hi,
A path based authorization configuration problem.
I have a rules file with content as follows:
# -------------------------------------------------
[groups]
test = harry, sally
[/]
* = rw
[/trunk/org/secure]
@test =
# -------------------------------------------------
I would expect that harry and sally have access to all but not
to 'secure'.
But: The result is, everyone has access to /trunk/org/secure.
In comparison, the following example runs as expected:
# -------------------------------------------------
[/]
* = rw
[/trunk/org/secure]
* =
# -------------------------------------------------
I'm running Subversion 1.5.5, Apache 2.0.63 on Windows XP Prof.
Any hint?
Hartmut
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2377019
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Subversion 1.6 on Fedora: Cannot resolve hostname
Posted by Stephan Robotta <ro...@ontoprise.de>.
On Thu, Jul 30, 2009 at 10:10:27AM -0400, David Weintraub wrote:
>
> I found that if I used the IP address instead of the machine name, it
> worked. Therefore, I added the machine name/IP address combo into my
> /etc/hosts file. This allows me to once again access our server by machine
> name.
That didn't seem to work here. But I am also not sure if I did everything
right.
regards, Stephan
Re: Subversion 1.6 on Fedora: Cannot resolve hostname
Posted by David Weintraub <qa...@gmail.com>.
Just to let you know, I never really solved the problem, but I did find a
way go get around the issue.
I found that if I used the IP address instead of the machine name, it
worked. Therefore, I added the machine name/IP address combo into my
/etc/hosts file. This allows me to once again access our server by machine
name.
Someone told me there might be a bug somewhere in the version of Neon that
Fedora uses since Subversion uses Neon to do name resolution. I reported
this to the neon people a while ago, but haven't heard anything.
On Thu, Jul 30, 2009 at 5:06 AM, Stephan Robotta <ro...@ontoprise.de>wrote:
> Hello,
>
> By searching for a solution to my problem, I found this message from
> David which apprarently seems the same that I have.
>
> SVN worked well before but suddenly quits with "could not resolve
> hostname". There havent been any changes in the configuration. So I
> do not assume any proxy problem. This happend after an package update
> on Fedora 11.
>
> Resolving the hostname is not the issue, a wget or ssh login on the
> repositories machine works well.
>
> Any help will be appreciated.
>
> Best regards, Stephan
>
>
--
David Weintraub
qazwart@gmail.com
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2376956
To unsubscribe from this discussion, e-mail: [users-unsubscribe@subversion.tigris.org].
Re: Subversion 1.6 on Fedora: Cannot resolve hostname
Posted by Stephan Robotta <ro...@ontoprise.de>.
On Thu, Jul 30, 2009 at 03:04:40PM +0100, Stefan Sperling wrote:
> On Thu, Jul 30, 2009 at 03:19:54PM +0200, Stephan Robotta wrote:
> > On Thu, Jul 30, 2009 at 11:01:30AM +0100, Stefan Sperling wrote:
> > >
> > > What RA layer do you use? Something using HTTP?
> > > If so, what HTTP library are you using Subversion with, serf or neon?
> > > Hostname lookups are done by those libraries.
> >
> > I don't exactly understand the question, what is the RA layer?
>
> Apologies. "RA layer" is Subversion-speak for "repository access layer",
> which refers to the method used by the client to contact the repository.
Oh, thank you for that.
> When you run svn --version, you get a list of available RA layers,
> (or "modules" as they are called in the help output):
>
> The following repository access (RA) modules are available:
>
> * ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
> - handles 'http' scheme
> - handles 'https' scheme
> * ra_svn : Module for accessing a repository using the svn network protocol.
> - with Cyrus SASL authentication
> - handles 'svn' scheme
> * ra_local : Module for accessing a repository on local disk.
> - handles 'file' scheme
I've got all these.
> Because I think so far, all reporters of this problem were using Fedora.
> Is this correct?
I guess so, at least David was.
Best regards, Stephan
Re: Subversion 1.6 on Fedora: Cannot resolve hostname
Posted by Stefan Sperling <st...@elego.de>.
On Thu, Jul 30, 2009 at 03:19:54PM +0200, Stephan Robotta wrote:
> Hello,
>
> On Thu, Jul 30, 2009 at 11:01:30AM +0100, Stefan Sperling wrote:
> > On Thu, Jul 30, 2009 at 11:06:13AM +0200, Stephan Robotta wrote:
> > >
> > > SVN worked well before but suddenly quits with "could not resolve
> > > hostname". There havent been any changes in the configuration. So I
> > > do not assume any proxy problem. This happend after an package update
> > > on Fedora 11.
> > >
> > > Resolving the hostname is not the issue, a wget or ssh login on the
> > > repositories machine works well.
> >
> > What RA layer do you use? Something using HTTP?
> > If so, what HTTP library are you using Subversion with, serf or neon?
> > Hostname lookups are done by those libraries.
>
> I don't exactly understand the question, what is the RA layer?
Apologies. "RA layer" is Subversion-speak for "repository access layer",
which refers to the method used by the client to contact the repository.
When you run svn --version, you get a list of available RA layers,
(or "modules" as they are called in the help output):
The following repository access (RA) modules are available:
* ra_neon : Module for accessing a repository via WebDAV protocol using Neon.
- handles 'http' scheme
- handles 'https' scheme
* ra_svn : Module for accessing a repository using the svn network protocol.
- with Cyrus SASL authentication
- handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
- handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using serf.
- handles 'http' scheme
- handles 'https' scheme
> What I did get e.g. is:
> [stephan@ernie ~]$ ldd /usr/bin/svn | grep neon
> libsvn_ra_neon-1.so.0 => /usr/lib/libsvn_ra_neon-1.so.0 (0x00d9a000)
> libneon.so.27 => /usr/lib/libneon.so.27 (0x06ce0000)
>
> [stephan@ernie ~]$ ldd /usr/bin/svn | grep serf
> returns nothing.
>
> So I assume that I am using some RA layer via HTTP with neon.
Most likely.
> I used to work with eclipse. But error messages there were not really
> helpful. Therefore I once started eclipse within an xterm to get
> information printed on STDOUT. There was a message like:
>
> ssh: Could not resolve hostname myserver.com:9630: Name or
> service not known
>
> Therefore I then tried svn on the command line, similar as described by
> David in the initial message of this thread.
I've heard of this error before, and I think the other reporter was
also using neon. It is hard to say what is really wrong here without
more information. Note though that Subversion relies on neon to resolve
hostnames. So this is possibly a bug in the neon shipped with Fedora.
Because I think so far, all reporters of this problem were using Fedora.
Is this correct?
Stefan
Re: Subversion 1.6 on Fedora: Cannot resolve hostname
Posted by Stephan Robotta <ro...@ontoprise.de>.
Hello,
On Thu, Jul 30, 2009 at 11:01:30AM +0100, Stefan Sperling wrote:
> On Thu, Jul 30, 2009 at 11:06:13AM +0200, Stephan Robotta wrote:
> >
> > SVN worked well before but suddenly quits with "could not resolve
> > hostname". There havent been any changes in the configuration. So I
> > do not assume any proxy problem. This happend after an package update
> > on Fedora 11.
> >
> > Resolving the hostname is not the issue, a wget or ssh login on the
> > repositories machine works well.
>
> What RA layer do you use? Something using HTTP?
> If so, what HTTP library are you using Subversion with, serf or neon?
> Hostname lookups are done by those libraries.
I don't exactly understand the question, what is the RA layer?
What I did get e.g. is:
[stephan@ernie ~]$ ldd /usr/bin/svn | grep neon
libsvn_ra_neon-1.so.0 => /usr/lib/libsvn_ra_neon-1.so.0 (0x00d9a000)
libneon.so.27 => /usr/lib/libneon.so.27 (0x06ce0000)
[stephan@ernie ~]$ ldd /usr/bin/svn | grep serf
returns nothing.
So I assume that I am using some RA layer via HTTP with neon.
I used to work with eclipse. But error messages there were not really
helpful. Therefore I once started eclipse within an xterm to get
information printed on STDOUT. There was a message like:
ssh: Could not resolve hostname myserver.com:9630: Name or
service not known
Therefore I then tried svn on the command line, similar as described by
David in the initial message of this thread.
Best regards, Stephan
Re: Subversion 1.6 on Fedora: Cannot resolve hostname
Posted by Stefan Sperling <st...@elego.de>.
On Thu, Jul 30, 2009 at 11:06:13AM +0200, Stephan Robotta wrote:
> Hello,
>
> By searching for a solution to my problem, I found this message from
> David which apprarently seems the same that I have.
>
> SVN worked well before but suddenly quits with "could not resolve
> hostname". There havent been any changes in the configuration. So I
> do not assume any proxy problem. This happend after an package update
> on Fedora 11.
>
> Resolving the hostname is not the issue, a wget or ssh login on the
> repositories machine works well.
>
> Any help will be appreciated.
What RA layer do you use? Something using HTTP?
If so, what HTTP library are you using Subversion with, serf or neon?
Hostname lookups are done by those libraries.
Stefan