Hello, Excuse me, when I rebooted my server, that problem appeared! How to look at ocf:heartbeat:LVM and ocf:heartbeat:LVM-activate resource agents?
# pcs resource config Group: apache Resource: httpd_fs (class=ocf provider=heartbeat type=Filesystem) Attributes: device=/dev/mapper/vg_apache-lv_apache directory=/var/www fstype=ext4 Operations: monitor interval=20s timeout=40s (httpd_fs-monitor-interval-20s) start interval=0s timeout=60s (httpd_fs-start-interval-0s) stop interval=0s timeout=60s (httpd_fs-stop-interval-0s) Resource: httpd_vip (class=ocf provider=heartbeat type=IPaddr2) Attributes: cidr_netmask=24 ip=192.168.56.100 Operations: monitor interval=10s timeout=20s (httpd_vip-monitor-interval-10s) start interval=0s timeout=20s (httpd_vip-start-interval-0s) stop interval=0s timeout=20s (httpd_vip-stop-interval-0s) Resource: httpd_ser (class=ocf provider=heartbeat type=apache) Attributes: configfile=/etc/httpd/conf/httpd.conf statusurl=http://127.0.0.1/server-status Operations: monitor interval=10s timeout=20s (httpd_ser-monitor-interval-10s) start interval=0s timeout=40s (httpd_ser-start-interval-0s) stop interval=0s timeout=60s (httpd_ser-stop-interval-0s) On Monday, April 5, 2021, 07:28:11 PM GMT+4:30, Ken Gaillot <kgail...@redhat.com> wrote: On Sat, 2021-04-03 at 14:35 +0000, Jason Long wrote: > Hello, > I configure my clustering labs with three nodes. One of my nodes > is iSCSI Shared Storage. Everything was OK until I restarted my iSCSI > Shared Storage. On node1 I checked the status of my cluster: > > # pcs status > Cluster name: mycluster > Cluster Summary: > * Stack: corosync > * Current DC: node1 (version 2.0.5-10.fc33-ba59be7122) - partition > with quorum > * Last updated: Sat Apr 3 18:45:49 2021 > * Last change: Mon Mar 29 19:36:35 2021 by root via cibadmin on > node1 > * 2 nodes configured > * 3 resource instances configured > > > Node List: > * Online: [ node1 node2 ] > > > Full List of Resources: > * Resource Group: apache: > * httpd_fs (ocf::heartbeat:Filesystem): Stopped > * httpd_vip (ocf::heartbeat:IPaddr2): Stopped > * httpd_ser (ocf::heartbeat:apache): Stopped > > > Failed Resource Actions: > * httpd_fs_start_0 on node1 'not installed' (5): call=14, > status='complete', exitreason='Couldn't find device > [/dev/mapper/vg_apache-lv_apache]. Expected /dev/??? to exist', last- > rc-change='2021-04-03 18:37:04 +04:30', queued=0ms, exec=502ms > * httpd_fs_start_0 on node2 'not installed' (5): call=14, > status='complete', exitreason='Couldn't find device > [/dev/mapper/vg_apache-lv_apache]. Expected /dev/??? to exist', last- > rc-change='2021-04-03 18:37:05 +04:30', queued=0ms, exec=540ms The above messages suggest that the web server file system requires the vg_apache volume group and lv_apache logical volume to be active, but they aren't. You may want to look at the ocf:heartbeat:LVM and ocf:heartbeat:LVM-activate resource agents to bring these dependencies into the cluster. The ocf:heartbeat:iSCSILogicalUnit and ocf:heartbeat:iSCSITarget agents may also be of interest. > > Daemon Status: > corosync: active/enabled > pacemaker: active/enabled > pcsd: active/enabled > > > And checked the iSCSI Shared Storage. It showed me below error: > > [root@node3 ~]# systemctl status iscsi.service > ● iscsi.service - Login and scanning of iSCSI devices > Loaded: loaded (/usr/lib/systemd/system/iscsi.service; enabled; > vendor preset: enabled) > Active: inactive (dead) > Condition: start condition failed at Sat 2021-04-03 18:49:08 +0430; > 2s ago > └─ ConditionDirectoryNotEmpty=/var/lib/iscsi/nodes was > not met > Docs: man:iscsiadm(8) > man:iscsid(8) > > > Apr 03 18:39:17 node3.localhost.localdomain systemd[1]: Condition > check resulted in Login and scanning of iSCSI devices being skipped. > Apr 03 18:39:17 node3.localhost.localdomain systemd[1]: > iscsi.service: Unit cannot be reloaded because it is inactive. > Apr 03 18:39:17 node3.localhost.localdomain systemd[1]: > iscsi.service: Unit cannot be reloaded because it is inactive. > Apr 03 18:49:08 node3.localhost.localdomain systemd[1]: Condition > check resulted in Login and scanning of iSCSI devices being skipped. > > > Why "iscsi.service" is inactive? I tried to restart it, but it > couldn't start! > How to solve it? > > Thanks. > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users > > ClusterLabs home: https://www.clusterlabs.org/ -- Ken Gaillot <kgail...@redhat.com> _______________________________________________ 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/