Re: could not start ovirt-engine: TagsDirector.init() fails
by Liebe, André-Sebastian
Donwngrading postgresql-jdbc from 42.2.14-1.el8 to 42.2.3-3.el8_2 (hint from failing ovirt 4.5 deployment https://lists.ovirt.org/archives/list/users@ovirt.org/thread/FA6BLIAIYY7G...) did the trick.
> dnf downgrade postgresql-jdbc
> systemctl restart ovirt-engine
sincerely
André-Sebastian Liebe
Zukunftslabor
gematik GmbH | Friedrichstr. 136 | 10117 Berlin
Tel +49 30 40041-197 | Fax +49 30 40041-111
andre.liebe(a)gematik.de | www.gematik.de
Amtsgericht Charlottenburg HRB 96351
Geschäftsführer: Dr. med Markus Leyck Dieken
-----Ursprüngliche Nachricht-----
Von: Liebe, André-Sebastian
Gesendet: Freitag, 6. Mai 2022 07:46
An: users(a)ovirt.org
Betreff: could not start ovirt-engine: TagsDirector.init() fails
Hello list,
I'm unable to start ovirt-engine after switching from CentOS 8 to CentOS 8-stream, doing a system update and a reboot. A previously done ovirt update from 4.4.9 to 4.4.10 (w/o system reboot but with service restart) went smoothly, so I guess it's somehow caused by one oft he centOS updates?
The root cause logged in server.log reads:
> org.springframework.dao.InvalidDataAccessApiUsageException: Unable to determine the correct call signature - no procedure/function/signature for 'gettagsbyparent_id'
But according to ovirt-engine-setup-*.log a GettagsByparent_id(v_parent_id UUID) function ist created duging engine-setup (which I run after dnf update).
When searching google for " org.ovirt.engine.core.bll.TagsDirector.init()" and "'gettagsbyparent_id" I got some results hinting for a faulty PosgreSQL jdbc driver from 2018
Any hints?
sincerely
André-Sebastian Liebe
Zukunftslabor
gematik GmbH | Friedrichstr. 136 | 10117 Berlin Tel +49 30 40041-197 | Fax +49 30 40041-111 andre.liebe(a)gematik.de | www.gematik.de
Amtsgericht Charlottenburg HRB 96351
Geschäftsführer: Dr. med Markus Leyck Dieken