[ClusterLabs] crm services not getting started after upgrading to snmp40

[., Anoop]

What is the "certain filesystem"? If cluster services require it, that would explain why they can't start.
 -  Here we have btrfs and xfs filesystems. Yes cluster services require these filesystem to be mounted.
What do the systemd journal logs say about the filesystem and cluster services? Did it try to start them at all?
 -  journalctl doesn't give you much input, it does try to start, but it fails. Another thing is if you boot with downgraded version of snmp (snmp30) all works fine



-----Original Message-----
From: Users <users-bounces at clusterlabs.org> On Behalf Of Ken Gaillot
Sent: Wednesday, May 22, 2024 7:32 PM
To: Cluster Labs - All topics related to open-source clustering welcomed <users at clusterlabs.org>
Subject: Re: [ClusterLabs] crm services not getting started after upgrading to snmp40

On Wed, 2024-05-22 at 07:33 +0000, ., Anoop wrote:
> Hello,
>  
> We have HA setup with 2 node cluster using CRM. OS is Suse 15sp3.
> After upgrading to snmp40, cluster services are not getting started 
> like pacemaker , corosync etc. After booting we have to manually mount 
> certain filesystem and start the crm services like pacemaker etc. We 
> have a SharedFileSystem group as the resource with 5 fileystems , but 
> not getting mounted while booting.  Let me know any other info 
> required.
>  
> Regards
> Anoop
> 

What is the "certain filesystem"? If cluster services require it, that would explain why they can't start.

What do the systemd journal logs say about the filesystem and cluster services? Did it try to start them at all?
--
Ken Gaillot <kgaillot at redhat.com>

_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users 

ClusterLabs home: https://www.clusterlabs.org/