Description of problem: Activating event notifification, along with trying to add/delete domain by rhevm-manage-domains cause DB related commands to fail on database access. Version-Release number of selected component (if applicable): SI24.5 How reproducible: always (tried on 2 clean install setups) Steps to Reproduce: 1. Define the /etc/ovirt-engine/notifier/notifier.conf for sending notifications (My conf attached as example) 2. Activate engine-notifierd service. (/etc/rc.d/init.d/engine-notifierd start) 3. Attach event notification to a user (I added a user from AD, attached to it event notification for ovirt-engine stop) 4. rhevm-manage-domains delete or add domain fail to access DB. (I run: rhevm-manage-domains -action=delete -addPermissions -domain=qa.lab.tlv.redhat.com -user=dafna -interactive -provider=activeDirectory Failure while connecting to database. Details: FATAL: connection limit exceeded for non-superusers) Actual results: Commands related to database DB connection fail on limit exceeded error: Examples: -------- 1. rhevm-manage-domains -action=delete -addPermissions -domain=qa.lab.tlv.redhat.com -user=dafna -interactive -provider=activeDirectory Failure while connecting to database. Details: FATAL: connection limit exceeded for non-superusers 2. rhevm-config -l Connection to the Database failed. Please check that the hostname and port number are correct and that the Database service is up and running. Expected results: Event notification should not interfere DB access. Additional info: Stop engine-notifierd release the DB.
Created attachment 656124 [details] notifier.conf
Created attachment 656125 [details] notifier log
Created attachment 656126 [details] engine.log
Duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=882847 Connection handling at notifier was vastly improved at this bug. Since notifierd does not work connection pool, each time a connection is obtained in its code a new connection is opened towards the DB, and the DB has a limit of open connections. The above bug fix reduced the time the connection is begin opened. *** This bug has been marked as a duplicate of bug 882847 ***