Hi Andrew,<br><br>thank you for your answer.<br><br><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">Does the ocf:heartbeat:Rsyslog script call crm_master?<br>
It needs to to tell pacemaker which instance to promote.<br></blockquote><div>Yes it does. But I forgot to call crm_master with the option -D in the stop action. I think that this was the error. After correcting this issue the ra starts as expected. <br>
<br></div><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">Two questions though...<br>1) Why use master/slave for rsyslog?<br></blockquote><div>
In the master role the rsyslog daemon should function as central log server and write the entries received on UDP port 514 into a MySQL database.<br>On the passive node the rsyslog service should be started with the standard config.<br>
Do you think there is a better solution to solve this requirement?<br> <br></div><blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">2) Is this an upstream RA? If not, you shouldn't be using the<br>
ocf:heartbeat namespace.<br clear="all"></blockquote>Ok thank you for the advice. Should I use the pacemaker class instead or should I define a custom namespace?<br><br>--<br><br>Regards,<br><br>Simon Jansen<br><br><br>---------------------------<br>
Simon Jansen<br>64291 Darmstadt<br><br>