I'm very aware of those issues.
Our network admin chose to use the administrator account, although I
would have preferred a separate account.
As for running it on a separate network share, I know this is
discouraged, but it was prompted by practicality. If you're telling me
this is not a supported configuration, I'll go back with that message
and we'll see about setting up a new file server for hosting our source
that can run the service on the server itself. But if it is a supported
(if discouraged) configuration, I'd like to figure out why it broke, and
how I can get it to work again.
The problem is that I don't know how to troubleshoot this. What I really
need to know is what the exact reason is that svnserve fails to launch.
Is there any way short of compiling a custom version to get that info?
-----Original Message-----
From: Andy Levy [mailto:andy.levy_at_gmail.com]
Sent: donderdag 26 juni 2008 16:32
To: Joeri Sebrechts
Cc: Kevin Grover; users_at_subversion.tigris.org
Subject: Re: windows: svnserve as a service won't launch
On Thu, Jun 26, 2008 at 8:18 AM, Joeri Sebrechts
<Joeri.Sebrechts_at_mcs.be> wrote:
> Thank you for your response.
>
> The service is installed as "Subversion Service", set to run
automatically.
>
> When I ask for the properties, I get this in the "Path to executable"
field:
> "C:\Program Files\CollabNet Subversion Server\svnserve.exe" --service
--root "\\Srvmcs11\Data\Ontwikkeling\ontw\subversion"
>
> svnserve.exe is found in C:\Program Files\CollabNet Subversion Server
> The path specified with --root is reachable when typed in file
explorer.
>
> Everything is running as the domain administrator account (which has
full rights everywhere), so I don't think rights are an issue.
>
> Logging-wise, all I get is the following in the system log:
> "The Subversion Server service failed to start due to the following
error:
> The service did not respond to the start or control request in a
timely fashion."
Hosting the repository database on a different server from the one where
your server process runs is discouraged. There are several ways things
can break, resulting in (at best) the service not running or (at worst)
repository corruption.
You shouldn't be running a service as a domain admin in the first place,
and yes it's possible that you still have permissions issues even though
you're using it.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-26 20:23:22 CEST