On Thu, Feb 24, 2011 at 3:31 PM, Dan Frincu <df.clus...@gmail.com> wrote:
> Hi,
>
> On 02/24/2011 04:24 PM, Stallmann, Andreas wrote:
>> Hi!
>>
>> First: I set up my configuration anew, and it works. I didn't change that
>> much, just set the monitor-action differently from before.
>> Instead of:
>>
>>> webserver_ressource ocf:heartbeat:apache \
>>> params httpd="/usr/sbin/httpd2-prefork" \
>>> op start interval="0" timeout="40s" \
>>> op stop interval="0" timeout="60s" \
>>> op monitor interval="10" timeout="20s" depth="0" \
>>> meta target-role="Started"
>> I have now:
>>
>> primitive web_res ocf:heartbeat:apache \
>> params configfile="/etc/apache2/httpd.conf" \
>> params httpd="/usr/sbin/httpd2-prefork" \
>> op start interval="0" timeout="40s" \
>> op stop interval="0" timeout="60s" \
>> op monitor interval="1min"
>>
>> As you can see, I added the "configfile".
>>
>> This obviously did it, because when I gave the logs a closer look I found:
>>
>> Feb 24 10:43:22 mgmt-01 apache[1191]: ERROR: httpd2-prefork: option requires
>> an argument -- f
>>
>> Somehow the ocf:heartbeat:apache did not supply the default-configfile.
>> Thus, you have to supply the configfile. Well...
>>
>>> The answer should be in the logs.
>> Your right, that's where it was. I somehow got lost in the vast amount of
>> logs...
>>
>> grep -i "error" | grep -i "apache"
>>
>> That did it.
>>
>> Is it, by the way possible, to influence the logging in any way? Make it
>> more verbose, or redirect the logs to a different file (without using
>> filtering in syslog)?
> If you're using corosync, then in /etc/corosync/corosync.conf.
>
> logging {
> debug: off
> fileline: off
> to_syslog: yes
> to_stderr: no
> syslog_facility: local7
> timestamp: on
> to_logfile: yes
> logfile: /var/log/cluster/corosync.log
> logger_subsys {
> subsys: AMF
> debug: off
> }
> }
>
> And in syslog.conf you put local7.*
> /var/log/cluster/corosync.log
>
> And it logs to a file. For anything else other than corosync, someone
> else can reply.
This will tell Pacemaker to also the same logging setup, so no
additional steps there.
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
