Description of problem: If you start qpidd as a service using "sudo /sbin/service qpidd start" then running "sudo /usr/sbin/qpidd -c" gives the output: Exception: Cannot open /var/run/qpidd.5672.pid: No such file or directory to stderr. Even though qpidd is actually running according to ps "sudo /sbin/service qpidd status" gives the correct result though. Version-Release number of selected component (if applicable): qpidd-0.2.656926-1.el5 How reproducible: Repeatable
The reason this happens is that qpidd uses /var/run if running as root and /tmp if not running as root. When the service is started, the daemon is started under user "qpidd", thus the pid is stored in /tmp/qpidd.5672.pid. Then "qpidd -c" is run directly under sudo, it is root and looks in /var/run/qpidd.5672.pid and fails.
turn this off by default / rip it out.
Add a option that specifies that we want a pid file and where to write it.
Since this is called from the rhmd init script, this keeps the service from starting: [root@dhcp-10-16-61-243 ~]# service rhmd start Starting RHM daemon: [ OK ] Exception: Cannot open /tmp/qpidd.5672.pid: No such file or directory [root@dhcp-10-16-61-243 ~]# service rhmd status rhmd is stopped bumping priority
Oh, the above was on RHEL4, by the way. Fresh install, packages added from BT4 RHEL4 repository on webqa.
qpidc-0.2.667603-1.el5, qpidc-perftest-0.2.667603-1.el5, qpidd-0.2.667603-1.el5, and rhm-0.2.2153-1.el5 have been pushed to the staging repo for testing