This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --mEvAgst0dIjlkjhP3giOcIRW6QCC31tgL Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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
On Wed, Feb 12, 2014 at 1:10 PM, Juan Pablo Lorier <jplorier@gmail.com>= wrote:
Well, too soon to say boodbye. Thought I used --change-db-credentials in the restore, the engine seem= s to be unable to connect to the database. I assume that it didn't get t= he new password, so, is there a way to tell the engine about the new pass= word? 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 dro= p the database nor user inside postgres. So when restore tries to acces= s 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-tool,=
you end up almost ready, but not quite - because the password is rand= om, and therefore different between the installations. In principle you c= ould have provided just the password to restore, but we decided that if yo= u need to change the credentials, you should pass all of them (except f= or defaults).
Hope this clarifies,
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
--mEvAgst0dIjlkjhP3giOcIRW6QCC31tgL 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/ObHAAoJEC5KDDg2+NMMJHoIALPzqv+wOBSBYvPTVVOYyDwq AmlNsLovYAxxtLWb1Vek6UtJPU3uSW3A48o33NhG43rBrrbayKYYMWiC/+mPUr18 i3UFzbETYK+iN79iBvBoVkpgxt7k1TxvHmP1Qr34sBweT+8z3ZsJyIK7GykMgDEU qV6wFHnJmdMLqo3RUdWPSBAQWlLBrnogBa/ATd0X/LTdImU9BFsF0S05Z1+zXQ/H tccyTtOPDnhmEyCsTsxTPuH+IAKo4Ripiogh9RRot3KBuPziLnquE/eUbfIzNMX1 lj9H17e8vP1/g4mOM8+/x7gR+TLmqsMHL/Jjc8w2JwLuz1FX+11MbiNGFg5ydKA= =fjv6 -----END PGP SIGNATURE----- --mEvAgst0dIjlkjhP3giOcIRW6QCC31tgL--