[ClusterLabs] "iscsi.service: Unit cannot be reloaded because it is inactive."

Jason Long hack3rcon at yahoo.com
Sat Apr 3 10:59:09 EDT 2021


Sorry, I didn't know my problem is not relevant to the pacemaker.






On Saturday, April 3, 2021, 07:22:30 PM GMT+4:30, Andrei Borzenkov <arvidjaar at gmail.com> wrote: 





On 03.04.2021 17:35, Jason Long wrote:
> Hello,
> I configure my clustering labs with three nodes.

You have two node cluster. What is running on nodes outside of cluster
is out of scope of pacemaker.

> 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
> 
> 
> Daemon Status:
>   corosync: active/enabled
>   pacemaker: active/enabled
>   pcsd: active/enabled
> 
> 
> And checked the iSCSI Shared Storage. It showed me below error:
> 
> [root at 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

It seems to tell you why it was not started.


>        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?

> 

Did you try asking on support list/forum dedicated to Linux iSCSI?
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

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



More information about the Users mailing list