<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">I activated debug=cib, and retried.<br>
<br>
New log file up at <a href="http://proteus.systemec.nl/~shadur/pacemaker/pacemaker_2.log.txt">
http://proteus.systemec.nl/~shadur/pacemaker/pacemaker_2.log.txt</a> ; unfortunately, while that *is* more information I'm not seeing anything that looks like it could be the cause, although it shouldn't be reading any config files yet because there shouldn't
be any *to* read...<br>
<br>
As to the misleading error message, it gets weirder: I grabbed a copy of the source code via apt-get source, and the phrase 'key has expired' does not occur anywhere in any file according to find ./ -type f -exec grep -il 'key has expired' {} \; so I have absolutely
NO idea where it's coming from...<br>
<br>
--<br>
Rens Houben<br>
Systemec Internet Services<br>
<table width="98%" style="FONT-SIZE: 11pt; BORDER-TOP: medium none; FONT-FAMILY: Calibri, Helvetica, Arial, sans-serif; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; COLOR: #000000; BORDER-LEFT: medium none; BACKGROUND-COLOR: #ffffff" cellspacing="2" cellpadding="1" bgcolor="#ffffff" align="left" border="0" id="c1-id-6">
<colgroup id="c1-id-7"><col id="c1-id-8"></colgroup>
<tbody id="c1-id-9">
<tr id="c1-id-10">
<td style="FONT-WEIGHT: bold" id="c1-id-11">
<p style="font-family: Calibri, Helvetica, Arial, sans-serif;FONT-SIZE: 11pt;font-weight:bold" id="c1-id-12">
SYSTEMEC BV</p>
</td>
</tr>
<tr style="TEXT-DECORATION: ; BORDER-TOP-COLOR: ; BORDER-LEFT-COLOR: ; COLOR: ; BORDER-BOTTOM-COLOR: ; BORDER-RIGHT-COLOR: " id="c1-id-13">
<td id="c1-id-14">
<p style="font-family: Calibri, Helvetica, Arial, sans-serif;FONT-SIZE: 11pt" id="c1-id-15">
Marinus Dammeweg 25, 5928 PW Venlo<br id="c1-id-16">
Postbus 3290, 5902 RG Venlo<br id="c1-id-17">
Industrienummer: 6817<br id="c1-id-18">
Nederland<br id="c1-id-19">
<br id="c1-id-20">
T: 077-3967572 (Support)<br id="c1-id-21">
K.V.K. nummer: 12027782 (Venlo)</p>
</td>
</tr>
<tr id="c1-id-22">
<td style="VERTICAL-ALIGN: bottom" align="left" id="c1-id-23">
<p style="font-family:Arial" id="c1-id-24"><a href="https://www.systemec.nl" title="Systemec Datacenter Venlo & Nettetal" id="c1-id-25"><img style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none" width="260" height="130" src="https://www.systemec.nl/layout/mail/SystemecDatacenterVenloenNettetalbanner2.jpg" border="0" alt="Systemec Datacenter Venlo & Nettetal" id="c1-id-26"></a></p>
</td>
</tr>
<tr id="c1-id-27">
<td style="VERTICAL-ALIGN: bottom" align="left" id="c1-id-28">
<p style="font-family: Calibri, Helvetica, Arial, sans-serif;FONT-SIZE: 11pt" id="c1-id-29">
<a href="https://support.systemec.nl" title="Systemec Helpdesk" id="c1-id-30"><img width="20" height="24" style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none" src="https://www.systemec.nl/layout/mail/systemechelpdesk.png" border="0" alt="Systemec Helpdesk" id="c1-id-31"></a>
<a href="https://support.systemec.nl" style="color:#009cda" title="Systemec Helpdesk" id="c1-id-32">Helpdesk</a></p>
</td>
</tr>
<tr id="c1-id-33">
<td style="VERTICAL-ALIGN: bottom" align="left" id="c1-id-34">
<p style="font-family: Calibri, Helvetica, Arial, sans-serif;FONT-SIZE: 11pt" id="c1-id-35">
<a href="https://www.systemec.nl/nl/nieuwsbrief" id="c1-id-36"><img width="21" height="16" style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none" src="https://www.systemec.nl/layout/mail/nieuwsbrief.png" border="0" alt="Aanmelden nieuwsbrief" title="Aanmelden nieuwsbrief" id="c1-id-37"></a>
<a href="https://www.systemec.nl/nl/nieuwsbrief" style="color:#009cda" id="c1-id-38">Aanmelden nieuwsbrief</a></p>
</td>
</tr>
<tr id="c1-id-39">
<td style="VERTICAL-ALIGN: bottom" align="left" id="c1-id-40">
<p style="font-family:Calibri, Helvetica, Arial, sans-serif;FONT-SIZE: 11pt;color:#009cda" id="c1-id-41">
Volg ons op: <a href="https://twitter.com/systemec" title="Systemec Twitter" target="_blank" id="c1-id-42"><img style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none" width="16" height="16" src="https://www.systemec.nl/layout/mail/twitterbird.png" border="0" alt="Systemec Twitter" id="c1-id-43"></a> <a href="https://www.facebook.com/systemecbv" title="Systemec Facebook" target="_blank" id="c1-id-44"><img style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none" width="16" height="16" src="https://www.systemec.nl/layout/mail/facebook.png" border="0" alt="Systemec Facebook" id="c1-id-45"></a> <a href="http://www.linkedin.com/company/systemec-b.v." title="Systemec Linkedin" target="_blank" id="c1-id-46"><img style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none" width="16" height="16" src="https://www.systemec.nl/layout/mail/linkedin.png" border="0" alt="Systemec Linkedin" id="c1-id-47"></a> <a href="http://www.youtube.com/user/systemec1" title="Systemec Youtube" target="_blank" id="c1-id-48"><img style="BORDER-TOP: medium none; BORDER-RIGHT: medium none; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none" width="16" height="16" src="https://www.systemec.nl/layout/mail/youtube.png" border="0" alt="Systemec Youtube" id="c1-id-49"></a></p>
</td>
</tr>
</tbody>
</table>
<br>
________________________________________<br>
Van: Ken Gaillot <kgaillot@redhat.com><br>
Verzonden: vrijdag 24 maart 2017 16:49<br>
Aan: users@clusterlabs.org<br>
Onderwerp: Re: [ClusterLabs] error: The cib process (17858) exited: Key has expired (127)<br>
<br>
On 03/24/2017 08:06 AM, Rens Houben wrote:<br>
> I recently upgraded a two-node cluster (named 'castor' and 'pollux'<br>
> because I should not be allowed to think up computer names before I've<br>
> had my morning caffeine) from Debian wheezy to Jessie after the<br>
> backports for corosync and pacemaker finally made it in. However, one of<br>
> the two servers failed to start correctly for no really obvious reason.<br>
><br>
> Given as how it'd been years since I last set them up and had forgotten<br>
> pretty much everything about it in the interim I decided to purge<br>
> corosync and pacemaker on both systems and run with clean installs instead.<br>
><br>
> This worked on pollux, but not on castor. Even after going pack,<br>
> re-purging, removing everything legacy in /var/lib/heartbeat and<br>
> emptying both directories, castor still refuses to bring up pacemaker.<br>
><br>
><br>
> I put the full log of a start attempt up at<br>
> <a href="http://proteus.systemec.nl/~shadur/pacemaker/pacemaker.log.txt">http://proteus.systemec.nl/~shadur/pacemaker/pacemaker.log.txt</a><br>
> <<a href="http://proteus.systemec.nl/%7Eshadur/pacemaker/pacemaker.log.txt">http://proteus.systemec.nl/%7Eshadur/pacemaker/pacemaker.log.txt</a>>, but<br>
> this is the excerpt that I /think/ is causing the failure:<br>
><br>
> Mar 24 13:59:05 [25495] castor pacemakerd: error: pcmk_child_exit:The<br>
> cib process (25502) exited: Key has expired (127)<br>
> Mar 24 13:59:05 [25495] castor pacemakerd: notice:<br>
> pcmk_process_exit:Respawning failed child process: cib<br>
><br>
> I don't see any entries from cib in the log that suggest anything's<br>
> going wrong, though, and I'm running out of ideas on where to look next.<br>
<br>
The "Key has expired" message is misleading. (Pacemaker really needs an<br>
overhaul of the exit codes it can return, so these messages can be<br>
reliable, but there are always more important things to take care of ...)<br>
<br>
Pacemaker is getting 127 as the exit status of cib, and interpreting<br>
that as a standard system error number, but it probably isn't one. I<br>
don't actually see any way that the cib can return 127, so I'm not sure<br>
what that might indicate.<br>
<br>
In any case, the cib is mysteriously dying whenever it tries to start,<br>
apparently without logging why or dumping core. (Do you have cores<br>
disabled at the OS level?)<br>
<br>
> Does anyone have any suggestions as to how to coax more information out<br>
> of the processes and into the log files so I'll have a clue to work with?<br>
<br>
Try it again with PCMK_debug=cib in /etc/default/pacemaker. That should<br>
give more log messages.<br>
<br>
><br>
> Regards,<br>
><br>
> --<br>
> Rens Houben<br>
> Systemec Internet Services<br>
><br>
> SYSTEMEC BV<br>
><br>
> Marinus Dammeweg 25, 5928 PW Venlo<br>
> Postbus 3290, 5902 RG Venlo<br>
> Industrienummer: 6817<br>
> Nederland<br>
><br>
> T: 077-3967572 (Support)<br>
> K.V.K. nummer: 12027782 (Venlo)<br>
><br>
> Systemec Datacenter Venlo & Nettetal <<a href="https://www.systemec.nl">https://www.systemec.nl</a>><br>
><br>
> Systemec Helpdesk <<a href="https://support.systemec.nl">https://support.systemec.nl</a>> Helpdesk<br>
> <<a href="https://support.systemec.nl">https://support.systemec.nl</a>><br>
><br>
> Aanmelden nieuwsbrief <<a href="https://www.systemec.nl/nl/nieuwsbrief">https://www.systemec.nl/nl/nieuwsbrief</a>><br>
> Aanmelden nieuwsbrief <<a href="https://www.systemec.nl/nl/nieuwsbrief">https://www.systemec.nl/nl/nieuwsbrief</a>><br>
><br>
> Volg ons op: Systemec Twitter <<a href="https://twitter.com/systemec">https://twitter.com/systemec</a>> Systemec<br>
> Facebook <<a href="https://www.facebook.com/systemecbv">https://www.facebook.com/systemecbv</a>> Systemec Linkedin<br>
> <<a href="http://www.linkedin.com/company/systemec-b.v.">http://www.linkedin.com/company/systemec-b.v.</a>> Systemec Youtube<br>
> <<a href="http://www.youtube.com/user/systemec1">http://www.youtube.com/user/systemec1</a>><br>
<br>
_______________________________________________<br>
Users mailing list: Users@clusterlabs.org<br>
<a href="http://lists.clusterlabs.org/mailman/listinfo/users">http://lists.clusterlabs.org/mailman/listinfo/users</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">
http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</a><br>
</div>
</span></font>
</body>
</html>