Description of problem: ovirt-engine-notifier[10280] ERROR run:593 Error: Directory '/usr/share/jboss-as' is required but missing Version-Release number of selected component (if applicable): Red Hat Storage Console Version: 2.1.0-0.bb4.el6rhs How reproducible: Always Steps to Reproduce: 1. Try to start ovirt-engine-notifier using # /etc/init.d/ovirt-engine-notifier start Actual results: ---------------------------- # /etc/init.d/ovirt-engine-notifier start Starting oVirt Engine Notifier: [FAILED] # tailf /var/log/messages Jun 21 17:06:34 rhs-client3 ovirt-engine-notifier[10260] ERROR run:593 Error: Directory '/usr/share/jboss-as' is required but missing Jun 21 17:06:35 rhs-client3 ovirt-engine-notifier[10280] ERROR run:593 Error: Directory '/usr/share/jboss-as' is required but missing Jun 21 17:08:52 rhs-client3 ovirt-engine-notifier[10336] ERROR run:593 Error: Directory '/usr/share/jboss-as' is required but missing Jun 21 17:11:37 rhs-client3 ovirt-engine-notifier[10378] ERROR run:593 Error: Directory '/usr/share/jboss-as' is required but missing Jun 21 17:11:38 rhs-client3 ovirt-engine-notifier[10397] ERROR run:593 Error: Directory '/usr/share/jboss-as' is required but missing Jun 21 17:14:23 rhs-client3 ovirt-engine-notifier[10421] ERROR run:593 Error: Directory '/usr/share/jboss-as' is required but missing ---------------------------- Expected results: The service should start successfully Additional info:
The service now appears to be starting but the status and log says the following: --------------- [root@rhs-client3 notifier]# /etc/init.d/ovirt-engine-notifier start Starting oVirt Engine Notifier: [ OK ] [root@rhs-client3 notifier]# /etc/init.d/ovirt-engine-notifier status dead but pid file exists [root@rhs-client3 notifier]# cat console.log Traceback (most recent call last): File "/usr/lib64/python2.6/logging/handlers.py", line 799, in emit self._connect_unixsocket(self.address) File "/usr/lib64/python2.6/logging/handlers.py", line 731, in _connect_unixsocket self.socket.connect(address) File "<string>", line 1, in connect error: [Errno 91] Protocol wrong type for socket [root@rhs-client3 notifier]# service ovirt-engine-notifier stop Stopping oVirt Engine Notifier: [FAILED] --------------- Hence, moving back to Assigned
Set all MAIL related configurations in /usr/share/ovirt-engine/conf/notifier.conf.defaults and then start the ovirt-engine-notifier service.
Fixed in bb6
Have you set the configuration as per comment #3?
(In reply to Sahina Bose from comment #6) > Have you set the configuration as per comment #3? Yes! [root@rhs-client3 ~]# grep "MAIL_SERVER" /usr/share/ovirt-engine/conf/notifier.conf.defaults MAIL_SERVER=rhs-client3.lab.eng.blr.redhat.com [root@rhs-client3 ~]# /etc/init.d/ovirt-engine-notifier start Starting oVirt Engine Notifier: [ OK ] [root@rhs-client3 ~]# /etc/init.d/ovirt-engine-notifier status dead but pid file exists Can you confirm the exact configuration file to be modified and all the mandatory fields to be filled for successfully starting the service? Also, if the MAIL_SERVER is not defined, we should be getting a meaningful error message something like: "Error: $MAIL_SERVER is not defined, please check for this in configuration file" instead of simply starting the service and showing the status as "dead but pid file exists"
Please set all the configuration values in /usr/share/ovirt-engine/conf/notifier.conf.defaults and start the service MAIL_SERVER= MAIL_USER= MAIL_PASSWORD= MAIL_FROM= MAIL_REPLY_TO= There's an issue with logging where proper message is not logged if values are not set.
Verified as fixed in bb6. ovirt-engine-notifier now seems to start fine once the required configuration values are set in /usr/share/ovirt-engine/conf/notifier.conf.defaults file. I've logged separate bugs for the problems with the error message and log file. Bug 989382 & Bug 989422
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1262.html