You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Dheeraj <kv...@gmail.com> on 2020/04/14 03:51:34 UTC
SVN Server migration to a new server
Hi
I have upgraded my SVN from RHEL 6 to RHEL 7 to a new server.
I still have RHEL 6 server in production and have an DNS alias named
svn-server poditing to the old server. My plan is to do a SVN dump of
repos from old server and load it on new server. Once I load all repos, I
will make the old server (RHEL 6) to read only and then make DNS change to
point svn-server alias to new server (RHEL 7) and make it production.
Do I need to do any other thing apart from this.
Will I get any error while doing commit/check out to the existing one,
since server is changed.
Will I get "svn: E155000:" error?
Appreciate your help.
Thanks,
Dheeraj
Re: SVN Server migration to a new server
Posted by Johan Corveleyn <jc...@gmail.com>.
On Tue, May 12, 2020 at 1:00 PM Dheeraj <kv...@gmail.com> wrote:
>
> Hi All
>
> I did SVN server migration from RHEL 6 to RHEL 7 and migrated the repos.
> Also DNS entry is changed so that alias points to the news server. When I did svn up from an existing setup, I got below error.
>
> svn: E175002: Unable to connect to a repository at URL 'https://svn-hpc.americas.shell.com/svn/RnD'
> svn: E175002: Server sent unexpected return value (500 Internal Server Error) in response to OPTIONS request for 'https://svn-hpc.americas.shell.com/svn/RnD'
>
> Any solution to this.
A "500 Internal Server Error" always indicates that the server had
some error internally. You have to take a look at the (Apache httpd)
error log on the server to get more information about the nature of
the error. Perhaps there is something wrong on the server side with
your new installation.
--
Johan
Re: SVN Server migration to a new server
Posted by Dheeraj <kv...@gmail.com>.
Sorry, that was a permission issue with apache. Issue fixed.
Thanks
Best Regards,
Dheeraj
On Tue, May 12, 2020 at 4:30 PM Dheeraj <kv...@gmail.com> wrote:
> Hi All
>
> I did SVN server migration from RHEL 6 to RHEL 7 and migrated the repos.
> Also DNS entry is changed so that alias points to the news server. When I
> did svn up from an existing setup, I got below error.
>
> svn: E175002: Unable to connect to a repository at URL '
> https://svn-hpc.americas.shell.com/svn/RnD'
> svn: E175002: Server sent unexpected return value (500 Internal Server
> Error) in response to OPTIONS request for '
> https://svn-hpc.americas.shell.com/svn/RnD'
>
> Any solution to this.
>
>
> Best Regards,
> Dheeraj
>
>
> On Tue, Apr 14, 2020 at 8:07 PM Johan Corveleyn <jc...@gmail.com> wrote:
>
>> On Tue, Apr 14, 2020 at 11:36 AM Dheeraj <kv...@gmail.com> wrote:
>> >
>> > Hi Johan
>> >
>> > Thanks for the update. I have taken care of the hooks and
>> configuration, probably I missed the locks part.
>> > I will have a look into it.
>> > I was thinking since the IP address is changing will it cause any issue
>> during Checkout or commit even though the alias will be the same.
>>
>> I think that would be okay. If they have done the checkout from the
>> DNS name, then it should work out fine.
>>
>> --
>> Johan
>>
>
Re: SVN Server migration to a new server
Posted by Dheeraj <kv...@gmail.com>.
Hi All
I did SVN server migration from RHEL 6 to RHEL 7 and migrated the repos.
Also DNS entry is changed so that alias points to the news server. When I
did svn up from an existing setup, I got below error.
svn: E175002: Unable to connect to a repository at URL '
https://svn-hpc.americas.shell.com/svn/RnD'
svn: E175002: Server sent unexpected return value (500 Internal Server
Error) in response to OPTIONS request for '
https://svn-hpc.americas.shell.com/svn/RnD'
Any solution to this.
Best Regards,
Dheeraj
On Tue, Apr 14, 2020 at 8:07 PM Johan Corveleyn <jc...@gmail.com> wrote:
> On Tue, Apr 14, 2020 at 11:36 AM Dheeraj <kv...@gmail.com> wrote:
> >
> > Hi Johan
> >
> > Thanks for the update. I have taken care of the hooks and configuration,
> probably I missed the locks part.
> > I will have a look into it.
> > I was thinking since the IP address is changing will it cause any issue
> during Checkout or commit even though the alias will be the same.
>
> I think that would be okay. If they have done the checkout from the
> DNS name, then it should work out fine.
>
> --
> Johan
>
Re: SVN Server migration to a new server
Posted by Johan Corveleyn <jc...@gmail.com>.
On Tue, Apr 14, 2020 at 11:36 AM Dheeraj <kv...@gmail.com> wrote:
>
> Hi Johan
>
> Thanks for the update. I have taken care of the hooks and configuration, probably I missed the locks part.
> I will have a look into it.
> I was thinking since the IP address is changing will it cause any issue during Checkout or commit even though the alias will be the same.
I think that would be okay. If they have done the checkout from the
DNS name, then it should work out fine.
--
Johan
Re: SVN Server migration to a new server
Posted by Dheeraj <kv...@gmail.com>.
Hi Johan
Thanks for the update. I have taken care of the hooks and configuration,
probably I missed the locks part.
I will have a look into it.
I was thinking since the IP address is changing will it cause any issue
during Checkout or commit even though the alias will be the same.
Best Regards,
Dheeraj
On Tue, Apr 14, 2020 at 1:46 PM Johan Corveleyn <jc...@gmail.com> wrote:
> On Tue, Apr 14, 2020 at 9:28 AM Dheeraj <kv...@gmail.com> wrote:
> >
> > Hi
> >
> > I have upgraded my SVN from RHEL 6 to RHEL 7 to a new server.
> > I still have RHEL 6 server in production and have an DNS alias named
> svn-server poditing to the old server. My plan is to do a SVN dump of repos
> from old server and load it on new server. Once I load all repos, I will
> make the old server (RHEL 6) to read only and then make DNS change to point
> svn-server alias to new server (RHEL 7) and make it production.
> > Do I need to do any other thing apart from this.
> > Will I get any error while doing commit/check out to the existing one,
> since server is changed.
> > Will I get "svn: E155000:" error?
>
> Hi Dheeraj,
>
> Dump & load will only transfer the versioned data (FSFS database).
> Don't forget to also copy over:
>
> - hook scripts: OLDREPOS/hooks to NEWREPOS/hooks (it's best to
> review them at this point, to make sure they'll work on the new
> machine)
>
> - conf files: OLDREPOS/conf to NEWREPOS/conf (also, review them, and
> check the new default conf files to see if there are any interesting
> new options or comments)
>
> - locks: OLDREPOS/db/locks to NEWREPOS/db/locks (the locks that are
> kept in working copies, for which a token is held on the server -- be
> sure to do this during your maintenance window)
>
> If you've done a full dump and load onto the new machine (in a freshly
> created new repository), the repository UUID should be transferred as
> well, so normally your old working copies will keep working, and you
> won't get the E155000 error.
>
> Perhaps also take a look at this FAQ entry for some more details of
> the dump&load procedure:
> http://subversion.apache.org/faq.html#dumpload
>
> --
> Johan
>
Re: SVN Server migration to a new server
Posted by Johan Corveleyn <jc...@gmail.com>.
On Tue, Apr 14, 2020 at 9:28 AM Dheeraj <kv...@gmail.com> wrote:
>
> Hi
>
> I have upgraded my SVN from RHEL 6 to RHEL 7 to a new server.
> I still have RHEL 6 server in production and have an DNS alias named svn-server poditing to the old server. My plan is to do a SVN dump of repos from old server and load it on new server. Once I load all repos, I will make the old server (RHEL 6) to read only and then make DNS change to point svn-server alias to new server (RHEL 7) and make it production.
> Do I need to do any other thing apart from this.
> Will I get any error while doing commit/check out to the existing one, since server is changed.
> Will I get "svn: E155000:" error?
Hi Dheeraj,
Dump & load will only transfer the versioned data (FSFS database).
Don't forget to also copy over:
- hook scripts: OLDREPOS/hooks to NEWREPOS/hooks (it's best to
review them at this point, to make sure they'll work on the new
machine)
- conf files: OLDREPOS/conf to NEWREPOS/conf (also, review them, and
check the new default conf files to see if there are any interesting
new options or comments)
- locks: OLDREPOS/db/locks to NEWREPOS/db/locks (the locks that are
kept in working copies, for which a token is held on the server -- be
sure to do this during your maintenance window)
If you've done a full dump and load onto the new machine (in a freshly
created new repository), the repository UUID should be transferred as
well, so normally your old working copies will keep working, and you
won't get the E155000 error.
Perhaps also take a look at this FAQ entry for some more details of
the dump&load procedure:
http://subversion.apache.org/faq.html#dumpload
--
Johan