Re: [Users] engine-backup --restore
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 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 ''\"" >>> $ 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=restore --scope=all >>> --file=engine-20140211-1457.tar.bz2 --log=engine-backup.log >>> --change-db-credentials --db-host=localhost --db-port=5432 >>> --db-user=engine --db-name=engine --db-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 >>> wrote: Well, too soon to say boodbye. Thought I used --change-db-credentials in the restore, the engine seems to be unable to connect to the database. I assume that it didn't get the new password, so, is there a way to tell the engine about the new password? Regards, On 12/02/14 16:03, Yedidyah Bar David wrote: > - Original Message - >> From: "Juan Pablo Lorier" >> To: "Yedidyah Bar David" >> Cc: "Sahina Bose" , "users" >> 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=backup > (perhaps do other stuff here) > 3. engine-cleanup > 4. engine-backup --mode=restore > > Why does this work? Because 'engine-cleanup', since 3.3, does not drop > the database nor user inside postgres. So when restore tries to access > 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 random, > 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 >> signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-backup --restore
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 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 ''\"" >> $ 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=restore --scope=all >> --file=engine-20140211-1457.tar.bz2 --log=engine-backup.log >> --change-db-credentials --db-host=localhost --db-port=5432 >> --db-user=engine --db-name=engine --db-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 >> wrote: >>> Well, too soon to say boodbye. >>> Thought I used --change-db-credentials in the restore, the engine seems >>> to be unable to connect to the database. I assume that it didn't get the >>> new password, so, is there a way to tell the engine about the new password? >>> Regards, >>> >>> On 12/02/14 16:03, Yedidyah Bar David wrote: - Original Message - > From: "Juan Pablo Lorier" > To: "Yedidyah Bar David" > Cc: "Sahina Bose" , "users" > 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=backup (perhaps do other stuff here) 3. engine-cleanup 4. engine-backup --mode=restore Why does this work? Because 'engine-cleanup', since 3.3, does not drop the database nor user inside postgres. So when restore tries to access 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 random, 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 >>> > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-backup --restore
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 ''\"" > $ 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=restore --scope=all > --file=engine-20140211-1457.tar.bz2 --log=engine-backup.log > --change-db-credentials --db-host=localhost --db-port=5432 > --db-user=engine --db-name=engine --db-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 wrote: >> Well, too soon to say boodbye. >> Thought I used --change-db-credentials in the restore, the engine seems >> to be unable to connect to the database. I assume that it didn't get the >> new password, so, is there a way to tell the engine about the new password? >> Regards, >> >> On 12/02/14 16:03, Yedidyah Bar David wrote: >>> - Original Message - From: "Juan Pablo Lorier" To: "Yedidyah Bar David" Cc: "Sahina Bose" , "users" 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=backup >>> (perhaps do other stuff here) >>> 3. engine-cleanup >>> 4. engine-backup --mode=restore >>> >>> Why does this work? Because 'engine-cleanup', since 3.3, does not drop >>> the database nor user inside postgres. So when restore tries to access >>> 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 random, >>> 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 >> signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-backup --restore
Hi David, It ended correctly and password was changed in the 10-setup-database.conf but there were still errors in the engine log pointing to an authentication problem against the database. I'm starting over again with some hints from another post, lets see what happens. Regards, On 13/02/14 04:23, Yedidyah Bar David wrote: > - Original Message - >> From: "Alon Bar-Lev" >> To: "Juan Pablo Lorier" >> Cc: "Yedidyah Bar David" , "users" >> Sent: Wednesday, February 12, 2014 9:13:30 PM >> Subject: Re: [Users] engine-backup --restore >> >> >> >> - Original Message - >>> From: "Juan Pablo Lorier" >>> To: "Yedidyah Bar David" >>> Cc: "users" >>> Sent: Wednesday, February 12, 2014 9:10:43 PM >>> Subject: Re: [Users] engine-backup --restore >>> >>> Well, too soon to say boodbye. >>> Thought I used --change-db-credentials in the restore, the engine seems >>> to be unable to connect to the database. I assume that it didn't get the >>> new password, so, is there a way to tell the engine about the new password? >>> Regards, >> /etc/ovirt-engine/engine.conf/10-setup-database.conf or similar. >> Look for ENGINE_DB_* variables. > Indeed, but this should happen automatically if you passed correct > credentials and restore succeeded. See e.g. the other report posted. > Did restore succeed? > > Thanks, signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-backup --restore
Thanks Alon, you were right. On 12/02/14 17:13, Alon Bar-Lev wrote: > > - Original Message - >> From: "Juan Pablo Lorier" >> To: "Yedidyah Bar David" >> Cc: "users" >> Sent: Wednesday, February 12, 2014 9:10:43 PM >> Subject: Re: [Users] engine-backup --restore >> >> Well, too soon to say boodbye. >> Thought I used --change-db-credentials in the restore, the engine seems >> to be unable to connect to the database. I assume that it didn't get the >> new password, so, is there a way to tell the engine about the new password? >> Regards, > /etc/ovirt-engine/engine.conf/10-setup-database.conf or similar. > Look for ENGINE_DB_* variables. > >> On 12/02/14 16:03, Yedidyah Bar David wrote: >>> - Original Message - >>>> From: "Juan Pablo Lorier" >>>> To: "Yedidyah Bar David" >>>> Cc: "Sahina Bose" , "users" >>>> 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=backup >>> (perhaps do other stuff here) >>> 3. engine-cleanup >>> 4. engine-backup --mode=restore >>> >>> Why does this work? Because 'engine-cleanup', since 3.3, does not drop >>> the database nor user inside postgres. So when restore tries to access >>> 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 random, >>> 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 >> signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-backup --restore
- Original Message - > From: "Alon Bar-Lev" > To: "Juan Pablo Lorier" > Cc: "Yedidyah Bar David" , "users" > Sent: Wednesday, February 12, 2014 9:13:30 PM > Subject: Re: [Users] engine-backup --restore > > > > - Original Message - > > From: "Juan Pablo Lorier" > > To: "Yedidyah Bar David" > > Cc: "users" > > Sent: Wednesday, February 12, 2014 9:10:43 PM > > Subject: Re: [Users] engine-backup --restore > > > > Well, too soon to say boodbye. > > Thought I used --change-db-credentials in the restore, the engine seems > > to be unable to connect to the database. I assume that it didn't get the > > new password, so, is there a way to tell the engine about the new password? > > Regards, > > /etc/ovirt-engine/engine.conf/10-setup-database.conf or similar. > Look for ENGINE_DB_* variables. Indeed, but this should happen automatically if you passed correct credentials and restore succeeded. See e.g. the other report posted. Did restore succeed? Thanks, -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-backup --restore
- Original Message - > From: "Trey Dockendorf" > To: "Juan Pablo Lorier" > Cc: "Yedidyah Bar David" , "users" > Sent: Wednesday, February 12, 2014 9:32:55 PM > Subject: Re: [Users] engine-backup --restore > > 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 ''\"" > $ 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=restore --scope=all > --file=engine-20140211-1457.tar.bz2 --log=engine-backup.log > --change-db-credentials --db-host=localhost --db-port=5432 > --db-user=engine --db-name=engine --db-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. Good job. Thanks for the report! -- Didi ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-backup --restore
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 ''\"" $ 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=restore --scope=all --file=engine-20140211-1457.tar.bz2 --log=engine-backup.log --change-db-credentials --db-host=localhost --db-port=5432 --db-user=engine --db-name=engine --db-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 wrote: > Well, too soon to say boodbye. > Thought I used --change-db-credentials in the restore, the engine seems > to be unable to connect to the database. I assume that it didn't get the > new password, so, is there a way to tell the engine about the new password? > Regards, > > On 12/02/14 16:03, Yedidyah Bar David wrote: >> - Original Message - >>> From: "Juan Pablo Lorier" >>> To: "Yedidyah Bar David" >>> Cc: "Sahina Bose" , "users" >>> 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=backup >> (perhaps do other stuff here) >> 3. engine-cleanup >> 4. engine-backup --mode=restore >> >> Why does this work? Because 'engine-cleanup', since 3.3, does not drop >> the database nor user inside postgres. So when restore tries to access >> 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 random, >> 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 > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-backup --restore
- Original Message - > From: "Juan Pablo Lorier" > To: "Yedidyah Bar David" > Cc: "users" > Sent: Wednesday, February 12, 2014 9:10:43 PM > Subject: Re: [Users] engine-backup --restore > > Well, too soon to say boodbye. > Thought I used --change-db-credentials in the restore, the engine seems > to be unable to connect to the database. I assume that it didn't get the > new password, so, is there a way to tell the engine about the new password? > Regards, /etc/ovirt-engine/engine.conf/10-setup-database.conf or similar. Look for ENGINE_DB_* variables. > > On 12/02/14 16:03, Yedidyah Bar David wrote: > > - Original Message - > >> From: "Juan Pablo Lorier" > >> To: "Yedidyah Bar David" > >> Cc: "Sahina Bose" , "users" > >> 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=backup > > (perhaps do other stuff here) > > 3. engine-cleanup > > 4. engine-backup --mode=restore > > > > Why does this work? Because 'engine-cleanup', since 3.3, does not drop > > the database nor user inside postgres. So when restore tries to access > > 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 random, > > 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 > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-backup --restore
Well, too soon to say boodbye. Thought I used --change-db-credentials in the restore, the engine seems to be unable to connect to the database. I assume that it didn't get the new password, so, is there a way to tell the engine about the new password? Regards, On 12/02/14 16:03, Yedidyah Bar David wrote: > - Original Message - >> From: "Juan Pablo Lorier" >> To: "Yedidyah Bar David" >> Cc: "Sahina Bose" , "users" >> 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=backup > (perhaps do other stuff here) > 3. engine-cleanup > 4. engine-backup --mode=restore > > Why does this work? Because 'engine-cleanup', since 3.3, does not drop > the database nor user inside postgres. So when restore tries to access > 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 random, > 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, signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-backup --restore
OK, that did work. I droped the database and created it back and also changed the password for the engine user. That did the trick. I now have to figure out why the web is blank, but at least is a step forward. Regards, On 12/02/14 16:03, Yedidyah Bar David wrote: > - Original Message - >> From: "Juan Pablo Lorier" >> To: "Yedidyah Bar David" >> Cc: "Sahina Bose" , "users" >> 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=backup > (perhaps do other stuff here) > 3. engine-cleanup > 4. engine-backup --mode=restore > > Why does this work? Because 'engine-cleanup', since 3.3, does not drop > the database nor user inside postgres. So when restore tries to access > 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 random, > 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, signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-backup --restore
Almost, when you mean random password, you mean for the engine user in the database? The new install and the old differ in some things in the db, so I tried to made then the same, but I saw a post of a user that removed the engine database and user and created them again before trying to restore, is that a good path? Regards, On 12/02/14 16:03, Yedidyah Bar David wrote: > - Original Message - >> From: "Juan Pablo Lorier" >> To: "Yedidyah Bar David" >> Cc: "Sahina Bose" , "users" >> 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=backup > (perhaps do other stuff here) > 3. engine-cleanup > 4. engine-backup --mode=restore > > Why does this work? Because 'engine-cleanup', since 3.3, does not drop > the database nor user inside postgres. So when restore tries to access > 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 random, > 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, signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-backup restore how to
It's supposed to exist, but by default it contains only comments. So the fact
that it's missing
does not in itself cause problems, but might indicate that there are some other
problems.
Sorry for not replying to your previous email - I really don't know how exactly
to proceed.
Some random notes/ideas/questions:
1. Was the restore done on a new clean system? The same system that the backup
was on? Something else?
2. Was it done with the same version used for backup? Which version?
3. In case it wasn't obvious: It does not create a database for you or manage
postgres in any way. You already know that, just noting.
4. In general you should run engine-setup after restore. It fixes almost all
the things that restore does not do. See [1] for details. The only things it
does not do (that I know about) are to enable postgres to start on reboot
(which you should do anyway yourself, see previous point) and websocket-proxy.
See [2] if you really care.
5. Another idea: Try to use something simpler than the engine to see if the
system can access the database. Not sure if it's easy to find something that
does that and does not need the engine - you can try e.g. log-collector.
[1] http://www.ovirt.org/Migrate_to_Hosted_Engine
[2] https://bugzilla.redhat.com/1024707
Good luck, and please report back/ask more if you get any insight!
--
Didi
- Original Message -
> From: "Steve Dainard"
> To: "Yedidyah Bar David"
> Cc: "Alon Bar-Lev" , "users" , "Eli
> Mesika"
> Sent: Thursday, January 30, 2014 9:04:35 PM
> Subject: Re: [Users] engine-backup restore how to
> Is this file supposed to exist:
> 2014-01-30 10:24:18,990 WARN [org.ovirt.engine.core.utils. LocalConfig] (MSC
> service thread 1-23) The file "/etc/ovirt-engine/engine. conf" doesn't exist
> or isn't readable. Will return an empty set of properties.
> I can't find it anywhere on the system.
> Steve Dainard
> IT Infrastructure Manager
> Miovision | Rethink Traffic
> 519-513-2407 ex.250
> 877-646-8476 (toll-free)
> Blog | LinkedIn | Twitter | Facebook
> Miovision Technologies Inc. | 148 Manitou Drive, Suite 101, Kitchener, ON,
> Canada | N2C 1L3
> This e-mail may contain information that is privileged or confidential. If
> you are not the intended recipient, please delete the e-mail and any
> attachments and notify us immediately.
> On Thu, Jan 30, 2014 at 10:32 AM, Steve Dainard < sdain...@miovision.com >
> wrote:
> > I can connect to the db with the 'engine' user.
>
> > Initially 'engine' wasn't a member of any roles, I added it to 'postgres'.
>
> > engine=> \du
>
> > List of roles
>
> > Role name | Attributes | Member of
>
> > ---+-+
>
> > engine | | {postgres}
>
> > postgres | Superuser | {}
>
> > : Create role
>
> > : Create DB
>
> > If you meant file permissions they are:
>
> > # ll
>
> > total 24
>
> > -rw---. 1 ovirt ovirt 380 Jan 29 18:35 10-setup-database.conf
>
> > -rw---. 1 ovirt ovirt 378 Jan 15 15:58
> > 10-setup-database.conf.20140129183539
>
> > -rw-r--r--. 1 root root 33 Jan 15 15:58 10-setup-jboss.conf
>
> > -rw---. 1 ovirt ovirt 384 Jan 15 15:59 10-setup-pki.conf
>
> > -rw-r--r--. 1 root root 259 Jan 15 15:58 10-setup-protocols.conf
>
> > -rw-r--r--. 1 root root 204 Dec 13 03:22 README
>
> > On ovirt-engine restart (engine.log):
>
> > i
>
> > 2014-01-30 10:24:18,988 INFO [org.ovirt.engine.core.utils.LocalConfig] (MSC
> > service thread 1-23) Loaded file
> > "/usr/share/ovirt-engine/services/ovirt-engine/ovirt-engine.conf".
>
> > 2014-01-30 10:24:18,990 WARN [org.ovirt.engine.core.utils.LocalConfig] (MSC
> > service thread 1-23) The file "/etc/ovirt-engine/engine.conf" doesn't exist
> > or isn't readable. Will return an empty set of properties.
>
> > 2014-01-30 10:24:18,991 INFO [org.ovirt.engine.core.utils.LocalConfig] (MSC
> > service thread 1-23) Loaded file
> > "/etc/ovirt-engine/engine.conf.d/10-setup-database.conf".
>
> > 2014-01-30 10:24:18,992 INFO [org.ovirt.engine.core.utils.LocalConfig] (MSC
> > service thread 1-23) Loaded file
> > "/etc/ovirt-engine/engine.conf.d/10-setup-jboss.conf".
>
> > 2014-01-30 10:24:18,994 INFO [org.ovirt.engine.core.utils.LocalConfig] (MSC
> > service thread 1-23) Loaded file
> > "/etc/ovirt-engine/engine.conf.d/10-setup-pki.conf".
>
> > 2014-01-30 10:24:18,994 INFO [org.ovirt.engine.core.utils.LocalConfig] (MSC
> > s
Re: [Users] engine-backup restore how to
Value of property "ENGINE_PERM_MIN" is "256m".
> 2014-01-30 10:24:19,017 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_PKI" is
> "/etc/pki/ovirt-engine".
> 2014-01-30 10:24:19,017 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_PKI_CA" is
> "/etc/pki/ovirt-engine/ca.pem".
> 2014-01-30 10:24:19,018 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_PKI_ENGINE_CERT" is
> "/etc/pki/ovirt-engine/certs/engine.cer".
> 2014-01-30 10:24:19,018 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_PKI_ENGINE_STORE" is
> "/etc/pki/ovirt-engine/keys/engine.p12".
> 2014-01-30 10:24:19,019 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_PKI_ENGINE_STORE_ALIAS"
> is "1".
> 2014-01-30 10:24:19,019 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property
> "ENGINE_PKI_ENGINE_STORE_PASSWORD" is "***".
> 2014-01-30 10:24:19,020 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_PKI_TRUST_STORE" is
> "/etc/pki/ovirt-engine/.truststore".
> 2014-01-30 10:24:19,021 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property
> "ENGINE_PKI_TRUST_STORE_PASSWORD" is "***".
> 2014-01-30 10:24:19,021 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_PROPERTIES" is "
> jsse.enableSNIExtension=false".
> 2014-01-30 10:24:19,022 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_PROXY_ENABLED" is
> "true".
> 2014-01-30 10:24:19,022 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_PROXY_HTTPS_PORT" is
> "443".
> 2014-01-30 10:24:19,023 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_PROXY_HTTP_PORT" is
> "80".
> 2014-01-30 10:24:19,023 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_STOP_INTERVAL" is "1".
> 2014-01-30 10:24:19,024 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_STOP_TIME" is "10".
> 2014-01-30 10:24:19,024 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_TMP" is
> "/var/tmp/ovirt-engine".
> 2014-01-30 10:24:19,024 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_UP_MARK" is
> "/var/lib/ovirt-engine/engine.up".
> 2014-01-30 10:24:19,025 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_USER" is "ovirt".
> 2014-01-30 10:24:19,025 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_USR" is
> "/usr/share/ovirt-engine".
> 2014-01-30 10:24:19,026 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_VAR" is
> "/var/lib/ovirt-engine".
> 2014-01-30 10:24:19,026 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "ENGINE_VERBOSE_GC" is "false".
> 2014-01-30 10:24:19,027 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "JBOSS_HOME" is
> "/usr/share/jboss-as".
> 2014-01-30 10:24:19,027 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC service thread 1-23) Value of property "SENSITIVE_KEYS" is
> ",ENGINE_DB_PASSWORD,ENGINE_PKI_TRUST_STORE_PASSWORD,ENGINE_PKI_ENGINE_STORE_PASSWORD".
> 2014-01-30 10:24:19,391 ERROR [org.ovirt.engine.core.bll.Backend] (MSC
> service thread 1-2) Error in getting DB connection. The database is
> inaccessible. Original exception is: BadSqlGrammarException:
> CallableStatementCallback; bad SQL grammar [{call checkdbconnection()}];
> nested exception is org.postgresql.util.PSQLException: ERROR: function
> checkdbconnection() does not exist
> Hint: No function matches the given name and argument types. You might
> need to add explicit type casts.
> Position: 15
> 2014-01-30 10:24:20,398 ERROR [org.ovirt.engine.
Re: [Users] engine-backup restore how to
is "
jsse.enableSNIExtension=false".
2014-01-30 10:24:19,022 INFO [org.ovirt.engine.core.utils.LocalConfig]
(MSC service thread 1-23) Value of property "ENGINE_PROXY_ENABLED" is
"true".
2014-01-30 10:24:19,022 INFO [org.ovirt.engine.core.utils.LocalConfig]
(MSC service thread 1-23) Value of property "ENGINE_PROXY_HTTPS_PORT" is
"443".
2014-01-30 10:24:19,023 INFO [org.ovirt.engine.core.utils.LocalConfig]
(MSC service thread 1-23) Value of property "ENGINE_PROXY_HTTP_PORT" is
"80".
2014-01-30 10:24:19,023 INFO [org.ovirt.engine.core.utils.LocalConfig]
(MSC service thread 1-23) Value of property "ENGINE_STOP_INTERVAL" is "1".
2014-01-30 10:24:19,024 INFO [org.ovirt.engine.core.utils.LocalConfig]
(MSC service thread 1-23) Value of property "ENGINE_STOP_TIME" is "10".
2014-01-30 10:24:19,024 INFO [org.ovirt.engine.core.utils.LocalConfig]
(MSC service thread 1-23) Value of property "ENGINE_TMP" is
"/var/tmp/ovirt-engine".
2014-01-30 10:24:19,024 INFO [org.ovirt.engine.core.utils.LocalConfig]
(MSC service thread 1-23) Value of property "ENGINE_UP_MARK" is
"/var/lib/ovirt-engine/engine.up".
2014-01-30 10:24:19,025 INFO [org.ovirt.engine.core.utils.LocalConfig]
(MSC service thread 1-23) Value of property "ENGINE_USER" is "ovirt".
2014-01-30 10:24:19,025 INFO [org.ovirt.engine.core.utils.LocalConfig]
(MSC service thread 1-23) Value of property "ENGINE_USR" is
"/usr/share/ovirt-engine".
2014-01-30 10:24:19,026 INFO [org.ovirt.engine.core.utils.LocalConfig]
(MSC service thread 1-23) Value of property "ENGINE_VAR" is
"/var/lib/ovirt-engine".
2014-01-30 10:24:19,026 INFO [org.ovirt.engine.core.utils.LocalConfig]
(MSC service thread 1-23) Value of property "ENGINE_VERBOSE_GC" is "false".
2014-01-30 10:24:19,027 INFO [org.ovirt.engine.core.utils.LocalConfig]
(MSC service thread 1-23) Value of property "JBOSS_HOME" is
"/usr/share/jboss-as".
2014-01-30 10:24:19,027 INFO [org.ovirt.engine.core.utils.LocalConfig]
(MSC service thread 1-23) Value of property "SENSITIVE_KEYS" is
",ENGINE_DB_PASSWORD,ENGINE_PKI_TRUST_STORE_PASSWORD,ENGINE_PKI_ENGINE_STORE_PASSWORD".
2014-01-30 10:24:19,391 ERROR [org.ovirt.engine.core.bll.Backend] (MSC
service thread 1-2) Error in getting DB connection. The database is
inaccessible. Original exception is: BadSqlGrammarException:
CallableStatementCallback; bad SQL grammar [{call checkdbconnection()}];
nested exception is org.postgresql.util.PSQLException: ERROR: function
checkdbconnection() does not exist
Hint: No function matches the given name and argument types. You might
need to add explicit type casts.
Position: 15
2014-01-30 10:24:20,398 ERROR [org.ovirt.engine.core.bll.Backend] (MSC
service thread 1-2) Error in getting DB connection. The database is
inaccessible. Original exception is: UncategorizedSQLException:
CallableStatementCallback; uncategorized SQLException for SQL [{call
checkdbconnection()}]; SQL state [25P02]; error code [0]; ERROR: current
transaction is aborted, commands ignored until end of transaction block;
nested exception is org.postgresql.util.PSQLException: ERROR: current
transaction is aborted, commands ignored until end of transaction block
[last error repeats]
Thanks,
*Steve Dainard *
IT Infrastructure Manager
Miovision <http://miovision.com/> | *Rethink Traffic*
519-513-2407 ex.250
877-646-8476 (toll-free)
*Blog <http://miovision.com/blog> | **LinkedIn
<https://www.linkedin.com/company/miovision-technologies> | Twitter
<https://twitter.com/miovision> | Facebook
<https://www.facebook.com/miovision>*
--
Miovision Technologies Inc. | 148 Manitou Drive, Suite 101, Kitchener, ON,
Canada | N2C 1L3
This e-mail may contain information that is privileged or confidential. If
you are not the intended recipient, please delete the e-mail and any
attachments and notify us immediately.
On Thu, Jan 30, 2014 at 2:18 AM, Yedidyah Bar David wrote:
> *From: *"Steve Dainard"
> *To: *"Alon Bar-Lev"
> *Cc: *"users" , "Yedidyah Bar David" ,
> "Eli Mesika"
> *Sent: *Thursday, January 30, 2014 7:44:01 AM
> *Subject: *Re: [Users] engine-backup restore how to
>
>
> I also see this error in engine.log which repeats every second if I am
> trying to access the web ui.
>
> 2014-01-29 18:59:47,531 ERROR [org.ovirt.engine.core.bll.Backend]
> (ajp--127.0.0.1-8702-4) Error in getting DB connection. The database is
> inaccessible. Original exception is: UncategorizedSQLException:
> CallableStatementCallback; uncategorized SQLException for SQL [{call
> checkdbconnection()}]; SQL state [25P02]; error code [0]; ERROR: current
> transaction is aborted, commands ignored until end of transaction block;
> nested exception is org.postgresql.util.PSQLException: ERROR: current
> transaction is aborted, commands ignored until end of transaction block
>
> It looks like the db inserted correctly, I took a quick look through some
> tables and can see the valid admin user, and snapshots. But I can't say for
> certain.
>
> The IP address of the new server does not match the IP of the old (backup
> file) server, would this have any impact? I would think not as its a local
> db.
>
> When I changed the password for the psql engine user, is there any config
> file this is referenced in that may not have been updated?
>
>
> In principle, the only needed file is
> /etc/ovirt-engine/engine.conf.d/10-setup-database.conf
> which was updated by restore. Can you please verify that you can connect
> to the database
> using the credentials in this file? What are its permissions/owner?
>
> Thanks,
> --
> Didi
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-backup restore how to
> From: "Steve Dainard"
> To: "Alon Bar-Lev"
> Cc: "users" , "Yedidyah Bar David" , "Eli
> Mesika"
> Sent: Thursday, January 30, 2014 7:44:01 AM
> Subject: Re: [Users] engine-backup restore how to
> I also see this error in engine.log which repeats every second if I am trying
> to access the web ui.
> 2014-01-29 18:59:47,531 ERROR [org.ovirt.engine.core.bll.Backend]
> (ajp--127.0.0.1-8702-4) Error in getting DB connection. The database is
> inaccessible. Original exception is: UncategorizedSQLException:
> CallableStatementCallback; uncategorized SQLException for SQL [{call
> checkdbconnection()}]; SQL state [25P02]; error code [0]; ERROR: current
> transaction is aborted, commands ignored until end of transaction block;
> nested exception is org.postgresql.util.PSQLException: ERROR: current
> transaction is aborted, commands ignored until end of transaction block
> It looks like the db inserted correctly, I took a quick look through some
> tables and can see the valid admin user, and snapshots. But I can't say for
> certain.
> The IP address of the new server does not match the IP of the old (backup
> file) server, would this have any impact? I would think not as its a local
> db.
> When I changed the password for the psql engine user, is there any config
> file this is referenced in that may not have been updated?
In principle, the only needed file is
/etc/ovirt-engine/engine.conf.d/10-setup-database.conf
which was updated by restore. Can you please verify that you can connect to the
database
using the credentials in this file? What are its permissions/owner?
Thanks,
--
Didi
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] engine-backup restore how to
I also see this error in engine.log which repeats every second if I am
trying to access the web ui.
2014-01-29 18:59:47,531 ERROR [org.ovirt.engine.core.bll.Backend]
(ajp--127.0.0.1-8702-4) Error in getting DB connection. The database is
inaccessible. Original exception is: UncategorizedSQLException:
CallableStatementCallback; uncategorized SQLException for SQL [{call
checkdbconnection()}]; SQL state [25P02]; error code [0]; ERROR: current
transaction is aborted, commands ignored until end of transaction block;
nested exception is org.postgresql.util.PSQLException: ERROR: current
transaction is aborted, commands ignored until end of transaction block
It looks like the db inserted correctly, I took a quick look through some
tables and can see the valid admin user, and snapshots. But I can't say for
certain.
The IP address of the new server does not match the IP of the old (backup
file) server, would this have any impact? I would think not as its a local
db.
When I changed the password for the psql engine user, is there any config
file this is referenced in that may not have been updated?
Thanks,
*Steve Dainard *
IT Infrastructure Manager
Miovision | **LinkedIn
| Twitter
| Facebook
*
--
Miovision Technologies Inc. | 148 Manitou Drive, Suite 101, Kitchener, ON,
Canada | N2C 1L3
This e-mail may contain information that is privileged or confidential. If
you are not the intended recipient, please delete the e-mail and any
attachments and notify us immediately.
On Wed, Jan 29, 2014 at 7:06 PM, Alon Bar-Lev wrote:
>
>
> - Original Message -
> > From: "Steve Dainard"
> > To: "users"
> > Sent: Thursday, January 30, 2014 1:59:08 AM
> > Subject: [Users] engine-backup restore how to
> >
> > There doesn't seem to be any solid documentation on how to use the
> > engine-backup restore function, and I'm not able to restore a backup.
> >
> > The best I've come up with is:
> > 1. Install engine on new host
> > 2. Stop engine
> > 3. run engine-backup --mode=restore --file=filename --log=logfile
> >
> > Fail.
> >
> > Log shows:
> > psql: FATAL: password authentication failed for user "engine"
> > 2014-01-29 18:20:30 10285: FATAL: Can't connect to the database
> >
> > 4. engine-backup --mode=restore --file=engine.bak --log=logfile
> > --change-db-credentials --db-host=localhost --db-user=engine
> > --db-name=engine --db-password='newpassword'
> >
> > Fails with same error.
>
> the --db-password must match the user's actual password within database,
> --change-db-credentials does not change the password in database but the
> host/port/user/password that are used by enigne.
>
> >
> > 5. change user to postgres, drop the old db, create a new db named
> engine,
> > set password for engine user same as 'newpassword'
> >
> > 6. engine-backup --mode=restore --file=engine.bak --log=logfile
> > --change-db-credentials --db-host=localhost --db-user=engine
> > --db-name=engine --db-password='newpassword'
>
> Ok, this is correct now.
>
> > 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.
> >
> > 7. start ovirt-engine, restart httpd, browse to web ui
> >
> > Blank page, no content.
> >
> > 8. stop firewall, browse to web ui
> >
> > Blank page, no content
> >
> > 9. Engine log contains:
> >
> > 2014-01-29 18:35:56,973 INFO [org.ovirt.engine.core.utils.LocalConfig]
> (MSC
> > service
> > thread 1-40) Value of property "SENSITIVE_KEYS" is
> > ",ENGINE_DB_PASSWORD,ENGINE_PKI_TR
> > UST_STORE_PASSWORD,ENGINE_PKI_ENGINE_STORE_PASSWORD".
> > 2014-01-29 18:35:57,330 ERROR [org.ovirt.engine.core.bll.Backend] (MSC
> > service thread
> > 1-25) Error in getting DB connection. The database is inaccessible.
> Original
> > exception is: BadSqlGrammarException: CallableStatementCallback; bad SQL
> > grammar [{call checkdbconnection()}]; nested exception is
> > org.postgresql.util.PSQLException: ERROR: function checkdbconnection()
> does
> > not exist
> > Hint: No function matches the given name and argument types. You might
> need
> > to add explicit type casts.
> > Position: 15
> > 2014-01-29 18:35:58,336 ERROR [org.ovirt.engine.core.bll.Backend] (MSC
> > service thread 1-25) Error in getting DB connection. The database is
> > inaccessible. Original exception is: UncategorizedSQLException:
> > CallableStatementCallback; uncategorized SQLException for SQL [{call
> > checkdbconnection()}]; SQL state [25P02]; error code [0]; ERROR: current
> > transaction is aborted, commands ignored until end of transaction block;
> > nested exception
Re: [Users] engine-backup restore how to
- Original Message -
> From: "Steve Dainard"
> To: "users"
> Sent: Thursday, January 30, 2014 1:59:08 AM
> Subject: [Users] engine-backup restore how to
>
> There doesn't seem to be any solid documentation on how to use the
> engine-backup restore function, and I'm not able to restore a backup.
>
> The best I've come up with is:
> 1. Install engine on new host
> 2. Stop engine
> 3. run engine-backup --mode=restore --file=filename --log=logfile
>
> Fail.
>
> Log shows:
> psql: FATAL: password authentication failed for user "engine"
> 2014-01-29 18:20:30 10285: FATAL: Can't connect to the database
>
> 4. engine-backup --mode=restore --file=engine.bak --log=logfile
> --change-db-credentials --db-host=localhost --db-user=engine
> --db-name=engine --db-password='newpassword'
>
> Fails with same error.
the --db-password must match the user's actual password within database,
--change-db-credentials does not change the password in database but the
host/port/user/password that are used by enigne.
>
> 5. change user to postgres, drop the old db, create a new db named engine,
> set password for engine user same as 'newpassword'
>
> 6. engine-backup --mode=restore --file=engine.bak --log=logfile
> --change-db-credentials --db-host=localhost --db-user=engine
> --db-name=engine --db-password='newpassword'
Ok, this is correct now.
> 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.
>
> 7. start ovirt-engine, restart httpd, browse to web ui
>
> Blank page, no content.
>
> 8. stop firewall, browse to web ui
>
> Blank page, no content
>
> 9. Engine log contains:
>
> 2014-01-29 18:35:56,973 INFO [org.ovirt.engine.core.utils.LocalConfig] (MSC
> service
> thread 1-40) Value of property "SENSITIVE_KEYS" is
> ",ENGINE_DB_PASSWORD,ENGINE_PKI_TR
> UST_STORE_PASSWORD,ENGINE_PKI_ENGINE_STORE_PASSWORD".
> 2014-01-29 18:35:57,330 ERROR [org.ovirt.engine.core.bll.Backend] (MSC
> service thread
> 1-25) Error in getting DB connection. The database is inaccessible. Original
> exception is: BadSqlGrammarException: CallableStatementCallback; bad SQL
> grammar [{call checkdbconnection()}]; nested exception is
> org.postgresql.util.PSQLException: ERROR: function checkdbconnection() does
> not exist
> Hint: No function matches the given name and argument types. You might need
> to add explicit type casts.
> Position: 15
> 2014-01-29 18:35:58,336 ERROR [org.ovirt.engine.core.bll.Backend] (MSC
> service thread 1-25) Error in getting DB connection. The database is
> inaccessible. Original exception is: UncategorizedSQLException:
> CallableStatementCallback; uncategorized SQLException for SQL [{call
> checkdbconnection()}]; SQL state [25P02]; error code [0]; ERROR: current
> transaction is aborted, commands ignored until end of transaction block;
> nested exception is org.postgresql.util.PSQLException: ERROR: current
> transaction is aborted, commands ignored until end of transaction block
>
It looks like the database is empty... are you sure the engine.bak is intact?
does you see CheckDBConnection there?
Thanks,
Alon
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
