This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --SnttCR8A5pcpcjpd4mLUME5X5iF7q9VSe Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I'll do then next week. Regards and again, thanks to everyone. On 13/02/14 13:50, Trey Dockendorf wrote:
A wiki page is a good idea, glad the steps worked in more than my case.=
- Trey
On Thu, Feb 13, 2014 at 9:37 AM, Juan Pablo Lorier <jplorier@gmail.com>=
wrote:
Hi Trey,
Following your procedure, I was able to get the engine running. THANKS= A LOT TO EVERYONE!! If you allow me, I'll create a wiki page with this mentioning you so others can get this easily. Regards,
On 12/02/14 17:32, Trey Dockendorf wrote:
I was having the same issue (and posted about it today, with full steps). I'd reply to my current post to list but I don't seem to receive my own posts.
I have since taken these steps (as root)
$ su - postgres -c "dropdb engine" $ su - postgres -c "psql -c \"create user engine password '<PASSWORD>= '\"" $ su - postgres -c "psql -c \"create database engine owner engine template template0 encoding 'UTF8' lc_collate 'en_US.UTF-8' lc_ctype 'en_US.UTF-8'\"" $ engine-backup --mode=3Drestore --scope=3Dall --file=3Dengine-20140211-1457.tar.bz2 --log=3Dengine-backup.log --change-db-credentials --db-host=3Dlocalhost --db-port=3D5432 --db-user=3Dengine --db-name=3Dengine --db-password=3D<PASSWORD> Restoring... Rewriting /etc/ovirt-engine/engine.conf.d/10-setup-database.conf Note: you might need to manually fix: - iptables/firewalld configuration - autostart of ovirt-engine service You can now start the engine service and then restart httpd Done.
$ engine-setup
I believe I initially created the database incorrectly (ran 'createdb=
engine' as postgres user). I was getting errors during engine-setup that indicated the database could not be accessed.
After the steps above, everything looks good.
- Trey
Well, too soon to say boodbye. Thought I used --change-db-credentials in the restore, the engine se= ems to be unable to connect to the database. I assume that it didn't get=
On Wed, Feb 12, 2014 at 1:10 PM, Juan Pablo Lorier <jplorier@gmail.co= m> wrote: the
new password, so, is there a way to tell the engine about the new pa= ssword? Regards,
On 12/02/14 16:03, Yedidyah Bar David wrote:
----- Original Message -----
From: "Juan Pablo Lorier" <jplorier@gmail.com> To: "Yedidyah Bar David" <didi@redhat.com> Cc: "Sahina Bose" <sabose@redhat.com>, "users" <users@ovirt.org> Sent: Wednesday, February 12, 2014 7:55:35 PM Subject: Re: [Users] Problems accesing the database
Hi Yedidyah,
But If I run engine-setup and then engine-backup restore shuldn't = it import the data to the existing db created by engine-setup? That's shown everywhere so I thought it's a valid way to migrate No.
There is a specific case in which this works automatically: All on the same host: 1. engine-setup 2. engine-backup --mode=3Dbackup (perhaps do other stuff here) 3. engine-cleanup 4. engine-backup --mode=3Drestore
Why does this work? Because 'engine-cleanup', since 3.3, does not d= rop the database nor user inside postgres. So when restore tries to acc= ess this database using this user and password it succeeds.
In general, if you do the restore on another machine, and do there 'engine-setup; engine-cleanup' as a quick-postgres-provisioning-too= l, you end up almost ready, but not quite - because the password is ra= ndom, and therefore different between the installations. In principle you= could have provided just the password to restore, but we decided that if = you need to change the credentials, you should pass all of them (except= for defaults).
Hope this clarifies,
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--SnttCR8A5pcpcjpd4mLUME5X5iF7q9VSe Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS/Ov3AAoJEC5KDDg2+NMM5ssH/jaqgEgIEwaLtwRwS3mpGnRj UO3Edpusz/Ry2V15lUjWrPBIenLwC2/Sch8jnHMb2DiLsB5pguXybT/0GUxAMDDm 3KkZt513DoG5q5Ja9EiqF148ItoW9oCQxiZQxYGKukzPUgDrMfXLlWnnKtMjTOzN 2bWkZc/Pgk/TaNU6k9nR5fPCo+wQv35OObh5qbF6K/Tr2rIyaiTvC+Hh95A6VHsJ ynqcgiF90XC3wrV0MVVjv9mBBaOhUfcg/0ulXSRjtKIwyqdkwii6GuS/ofkQx/2u OZr2Fk2YSgiOmeMgKtFZ6ERQFkuNhFlkJzmQy30CAiuejC8LQaWx27K8JbMV+VA= =Dz2U -----END PGP SIGNATURE----- --SnttCR8A5pcpcjpd4mLUME5X5iF7q9VSe--