https://bugzilla.novell.com/show_bug.cgi?id=838871 https://bugzilla.novell.com/show_bug.cgi?id=838871#c14 --- Comment #14 from Dejan Muhamedagic <dmuhamedagic@suse.com> 2013-09-11 16:46:28 CEST --- (In reply to comment #13)
Irritatingly, it works fine for me :-/
That's cool. I mean not the irritation but the other part :)
So the PidFile business is as follows, looking at the RA source on my test VM:
- If there's no PidFile in your apache config, the parser in apache-conf.sh notices, deliberately sets PidFile=$HA_VARRUNDIR/${httpd_basename}.pid (which becomes /var/run//httpd2.pid), and sets PIDFILE_DIRECTIVE="true"
- Later, the RA checks if $PIDFILE_DIRECTIVE is set (as it will be from the above) and starts apache with:
ocf_run $HTTPD $HTTPDOPTS $OPTIONS -f $CONFIGFILE -c "PidFile $PidFile"
Yeah, I can recall now, that's pretty new.
Some further digging around shows that apache actually does create a pidfile by itself if one isn't specified, but it's creating /var/run/httpd.pid (note the missing '2', which doesn't match what the RA wants). Interestingly, apache on SLE 11 SP3 *does* create the pidfile /var/run/httpd2.pid by default, which is why we never saw this before.
The pidfile stuff in Factory: [0]hex-10:obs > grep /var/run/httpd2.pid openSUSE:Factory/apache2/* openSUSE:Factory/apache2/apache2.changes:- set DEFAULT_PIDLOG to /var/run/httpd2.pid, so we don't need to ... openSUSE:Factory/apache2/rc.apache2:: ${pidfile:=/var/run/httpd2.pid} The very same as in SLE11SP3. The difference is that apache this time gets started through systemd and obviously this particular setting wasn't propagated. I guess that somebody would need to open a bugzilla for that.
I hate this RA.
Heh, you're not the only one. But this time it was not at fault. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.