Le 25 avr. 2017 à 07:59, Yedidyah Bar David <didi@redhat.com> a écrit :
On Mon, Apr 24, 2017 at 5:59 PM, Fabrice Bacchella <fabrice.bacchella@orange.fr> wrote:
https://www.dropbox.com/s/70h2ajt049i89p6/ovirt-engine.log.tar.gz?dl=0
Seems like this wasn't the first error. Before that, the engine lost connection to the database:
Later the engine was restarted and then the error you reported.
Are you sure your database is ok?
Of course I needed to restart the database, to change the requested setting about vacuum. But it was a scheduled restart, not during the upgrade.
Please provide the output of 'pg_dump -s' for it, and the output of 'select * from schema_version'.
it ? what it's name. I have no knowledge of pg, how can I connect to it to give the requested informations.
Can you please describe the full flow that you went through?
On last friday, I tried a first upgrade, but it stop because of the requested version mismatch. So I stopped it and asked for help. On monday I tried to apply the tuning on my database about autovacuum and so restart it. At this time, ovirt was still working fine. I then upgraded the pg client, to match pg_dump with the server but not the jdbc library, to keep the one supported (9.2). And then it failed and didn't want to restart any more.