This is caused by OpenID. Your OpenID provider ... the Google OpenID
service... gives out new unique OpenID strings for each host name you
visit. This is to prevent third parties from correlating your
movements across websites by combining their authentication logs
together. It also means you have to use the *EXACT SAME HOST NAME AND
PORT AND URL* of your Gerrit server when you move servers.
Yes, keep the host name the same.
> --
> To unsubscribe, email repo-discuss...@googlegroups.com
> More info at http://groups.google.com/group/repo-discuss?hl=en
> To unsubscribe, email repo-discuss+unsubscribe@googlegroups.com
Manually merge all of your new user accounts to your old user accounts
by editing the database records in accounts and account_external_ids.
Otherwise, no.
>> > To unsubscribe, email repo-discuss...@googlegroups.com
>> > More info at http://groups.google.com/group/repo-discuss?hl=en
>
> --
> To unsubscribe, email repo-discuss...@googlegroups.com
>> > To unsubscribe, email repo-discuss+unsubscribe@googlegroups.com
>> > More info at http://groups.google.com/group/repo-discuss?hl=en
>
> --
> To unsubscribe, email repo-discuss+unsubscribe@googlegroups.com
Was there an error message in the error log? I think there may have
been some confusion in the database records here so it gave up and
refused to login in the user.
> What's the proper way to merge it?
Typically its delete the old account_external_id record and then
update the new one to use the old account_id.
>> >> > To unsubscribe, email repo-discuss...@googlegroups.com
>> >> > More info at http://groups.google.com/group/repo-discuss?hl=en
>> >
>> > --
>> > To unsubscribe, email repo-discuss...@googlegroups.com
>> > More info at http://groups.google.com/group/repo-discuss?hl=en
>
> --
> To unsubscribe, email repo-discuss...@googlegroups.com
>> >> > To unsubscribe, email repo-discuss+unsubscribe@googlegroups.com
>> >> > More info at http://groups.google.com/group/repo-discuss?hl=en
>> >
>> > --
>> > To unsubscribe, email repo-discuss+unsubscribe@googlegroups.com
>> > More info at http://groups.google.com/group/repo-discuss?hl=en
>
> --
> To unsubscribe, email repo-discuss+unsubscribe@googlegroups.com
Yes.
> Is there any advantage migrating just the database from embedded H2 to a
> JDBC H2?
Doesn't make much a difference here, either way its H2. I guess if you
use the JDBC H2 you can use a cluster form, or run H2 as its own
process. But not sure that is a huge win.
> I was thinking about migrating from embedded H2 to MySQL as I know you guys
> were planning this for future release of Gerrit, but I don't think Gerrit
> now has a tool for that because I always end up in scheme error when loading
> the backup.sql onto MySQL.
Right, we don't have tools and thus don't support converting H2 to
MySQL. You might be able to find something on the web that you can
modify to do this for you. The schema as far as table layout goes is
the same, its just that the two dialects of SQL aren't really
compatible.
No.
> Or moving away from H2 embedded in the future?
We will be making changes in the future to move data from SQL storage
to Git based storage, so yes we will migrate some data out of H2.
> which will migrate from H2
> embedded to MySQL?
No, we aren't going to write tools to convert from H2 to MySQL. Nor
are we going to even attempt the crazy idea of embedding MySQL into
the Gerrit server. Some things just shouldn't mix. Embedding MySQL
daemon into a Java process is probably one of those combinations that
should never be attempted by a sane person. Or a crazy person.
I've successfully moved my Gerrit server to a new hostname while using
OpenId. Here are the basic steps:
* Shutdown existing gerrit instance
* Copy entire site path to new server
* Start gerrit on the new server (I didn't re-run init and I don't
think it's necessary)
* Log in with OpenId to new server
** Gerrit will create a new account for you, this is expected, but
don't fill out any info on the new profile
* Log in to gsql (ssh <username>@<gerrit-hostname> -p <gerrit-port> gerrit gsql)
** Run select * from account_external_ids where
email_address="<users-email-address>"
*** Note the correct account id of the account (should be the lower account_id)
** Run something like "update account_external_ids set
account_id=<account_id_from_prev_step> where
email_address="<users-email-address>"
** Delete the new account from account table: delete from account
where account_id=<new-account-d>
Of course you have to do this for every user and it is also a bad user
experience when they first log in and you can't do this for them
without their password.
Jason
>> > To unsubscribe, email repo-discuss...@googlegroups.com
>> > More info at http://groups.google.com/group/repo-discuss?hl=en
>
> --
> To unsubscribe, email repo-discuss...@googlegroups.com