<blockquote style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;" class="gmail_quote">On Mon, Jan 10, 2011 at 5:40 PM, Dejan Muhamedagic <<a href="mailto:deja...@fastmail.fm">deja...@fastmail.fm</a>> wrote:<br>
> Hi,<br>><br>> On Mon, Jan 10, 2011 at 10:46:58AM +0100, Simon Jansen wrote:<br>>> Hi,<br>>><br>>> I would like to test my cluster with the cluster test suite. I followed the<br>>> instructions of the README file to set up the logging with syslog-ng.<br>
>> Further I changed the syslog_facility in the corosync.conf file to local7.<br>>> The cluster nodes are sending their logs to the exerciser and the exerciser<br>>> writes the log entries into the file /var/log/ha-log-local7. The entries<br>
>> have the form<br>>> Jan 10 10:27:11 192.168.200.10 corosync[903]: [SERV ] Unloading all<br>>> Corosync service engines.<br>>> Jan 10 10:27:11 192.168.200.10 corosync[903]: [pcmk ] notice:<br>
>> pcmk_shutdown: Shuting down Pacemaker<br>>> Jan 10 10:27:11 192.168.200.10 corosync[903]: [pcmk ] notice:<br>>> pcmk_shutdown: mgmtd confirmed stopped<br>>> Jan 10 10:27:11 192.168.200.10 corosync[903]: [pcmk ] notice: stop_child:<br>
>> Sent -15 to crmd: [1023]<br>>> So I would say that the remote logging is working.<br>>> But when I start the CTS by executing the following command on the exerciser<br>>><br>>> python CTSlab.py --nodes "192.168.200.10 192.168.200.20" --at-boot 1<br>
>> --stack corosync --stonith no --logfile /var/log/ha-log-local7 1<br>>> the LogAudit fails.<br>>><br>>> The output of CTS is<br>>> Jan 10 10:04:03 Random seed is: 1294650243<br>>> Jan 10 10:04:03 >>>>>>>>>>>>>>>> BEGINNING 1 TESTS<br>
>> Jan 10 10:04:03 Stack: corosync (flatiron)<br>>> Jan 10 10:04:03 Schema: pacemaker-1.0<br>>> Jan 10 10:04:03 Scenario: Random Test Execution<br>>> Jan 10 10:04:03 Random Seed: 1294650243<br>
>> Jan 10 10:04:03 System log files: /var/log/ha-log-local7<br>>> Jan 10 10:04:03 Cluster nodes:<br>>> Jan 10 10:04:03 * 192.168.200.10<br>>> Jan 10 10:04:03 * 192.168.200.20<br>>> Jan 10 10:06:17 Testing for syslog logs<br>
>> Jan 10 10:06:17 Testing for remote logs<br>>> Jan 10 10:07:26 Restarting logging on: ['192.168.200.10', '192.168.200.20']<br>>> Jan 10 10:09:01 Restarting logging on: ['192.168.200.10', '192.168.200.20']<br>
>> Jan 10 10:11:37 Restarting logging on: ['192.168.200.10', '192.168.200.20']<br>>> Jan 10 10:15:02 Restarting logging on: ['192.168.200.10', '192.168.200.20']<br>>> Jan 10 10:19:02 ERROR: Cluster logging unrecoverable.<br>
>> Jan 10 10:19:02 Audit LogAudit FAILED.<br>><br>> What happened to the node names? I mean, your nodes are being<br>> named after their IP addresses. That's unusual.<br>><br></blockquote><div>The exerciser machine is placed in another network than the public one and I didn't defiend the hosts in the /etc/hosts file. The IP addresses are in the log summary on the exercise, too. So I thought the IP would be the best choice.<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">> Otherwise, it should work. BTW, what do you see when you run<br>> "logger -p <a href="http://local7.info">local7.info</a> hi" on one of the nodes? Does that end in<br>
> the syslog on your central host?<br></blockquote><div> Yes, it does end in the syslog of the exerciser.<br>Today I tested the following command:<br>python CTSlab.py --nodes "192.168.200.10 192.168.200.20" --logfile /var/log/ha-log-local7 --syslog-facility local7 --no-unsafe-tests --at-boot 1<br>
--stack corosync --stonith no 1<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"><br>thats not a requirement anymore<br></blockquote>
If it is not a requirement anymore, how do I have to call the CTSlab script and what parameters do I need?<br clear="all"><br>Thanks for your help.<br>-- <br><br><br>Best regards,<br><br>Simon Jansen<br><br><br>---------------------------<br>
Simon Jansen<br>64291 Darmstadt<br>