On Wed, Jun 22, 2022 at 1:46 PM Priyanka Balotra <priyanka.14balo...@gmail.com> wrote: > > Hi All, > > We are seeing an issue where we performed cluster shutdown followed by > cluster boot operation. All the nodes joined the cluster excet one (the first > node). Here are some pacemaker logs around that timestamp: > > 2022-06-19T07:02:08.690213+00:00 FILE-1 pacemaker-fenced[11637]: notice: > Operation 'off' targeting FILE-1 on FILE-2 for > pacemaker-controld.11523@FILE-2.0b09e949: OK > > 2022-06-19T07:02:08.690604+00:00 FILE-1 pacemaker-fenced[11637]: error: > stonith_construct_reply: Triggered assert at fenced_commands.c:2363 : request > != NULL > > 2022-06-19T07:02:08.690781+00:00 FILE-1 pacemaker-fenced[11637]: warning: > Can't create a sane reply > > 2022-06-19T07:02:08.691872+00:00 FILE-1 pacemaker-controld[11643]: crit: We > were allegedly just fenced by FILE-2 for FILE-2! > > 2022-06-19T07:02:08.693994+00:00 FILE-1 pacemakerd[11622]: warning: Shutting > cluster down because pacemaker-controld[11643] had fatal failure > > 2022-06-19T07:02:08.694209+00:00 FILE-1 pacemakerd[11622]: notice: Shutting > down Pacemaker > > 2022-06-19T07:02:08.694381+00:00 FILE-1 pacemakerd[11622]: notice: Stopping > pacemaker-schedulerd > > > > Let us know if you need any more logs to find an rca to this.
A little bit more info about your configuration and the pacemaker-version (cib?) used would definitely be helpful. Klaus > > Thanks > Priyanka > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
