Skip to content

Failed to start gluster-blockd.service: Unit gluster-block-target.service has a bad unit file setting #287

@Flavio2005

Description

@Flavio2005

Hello,
I am new to gluster 9 and also gluster-block. I have no idea if this is a bug or just an issue on my side.
My general goal is to build a volume to be exposed in iSCSI in HA.
The failover management will entrust it to the double connection that ESXi allows to make.

With three hosts, Fedora 34, fresh from installation, following the list of commands below, I created three nodes: two in replicate and one in arbiter.

Under clean Fedora34 i run this command

dnf -y install git
git clone https://github.com/gluster/gluster-block.git
cd gluster-block/
dnf install gcc autoconf automake make file libtool libuuid-devel json-c-devel glusterfs-api-devel glusterfs-server tcmu-runner targetcli
dnf install rpcgen libtirpc-devel
./autogen.sh && ./configure && make -j install
gluster-blockd --help
dnf -y install glusterfs-server
dnf -y install glusterfs glusterfs-fuse
systemctl enable --now glusterd

Version

glusterfs 9.2
gluster-block (0.5.1)
NAME=Fedora
VERSION="34 (Server Edition)"
Kernel: Linux 5.11.12-300.fc34.x86_64

gluster peer status

gluster peer status
Number of Peers: 2

Hostname: GluNodo13
Uuid: 678e1de0-95e2-446c-b888-2ebb17b407aa
State: Peer in Cluster (Connected)

Hostname: GluNodo11
Uuid: 8bec5d5c-cf07-4580-b174-eea837514e21
State: Peer in Cluster (Connected)

gluster volume info

Volume Name: hosting-volume
Type: Replicate
Volume ID: a6026b8f-aac0-4bd6-8404-c1c516fc7022
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x (2 + 1) = 3
Transport-type: tcp
Bricks:
Brick1: GluNodo11:/data/brick1/gv0
Brick2: GluNodo12:/data/brick1/gv0
Brick3: GluNodo13:/data/brick1/gv0 (arbiter)

Kind of issue

If I try to create a volume with gluster-block with this command
# gluster-block create hosting-volume/block-volume ha 3 192.168.11.151,192.168.11.152,192.168.11.153 1GiB client create failed: RPC: Remote system error - No such file or directory, unix addr /var/run/gluster-blockd.socket

# systemctl start gluster-blockd Failed to start gluster-blockd.service: Unit gluster-block-target.service has a bad unit file setting. See system logs and 'systemctl status gluster-blockd.service' for details.

I have tried in many ways but I cannot overcome the obstacle.
Can you please tell me where I'm wrong?

# systemctl status gluster-blockd
○ gluster-blockd.service - Gluster block storage utility
Loaded: loaded (/usr/local/lib/systemd/system/gluster-blockd.service; disabled; vendor preset: disabled)
Active: inactive (dead)

If I try to tun
# systemctl start gluster-blockd
Failed to start gluster-blockd.service: Unit gluster-block-target.service has a bad unit file setting.
See system logs and 'systemctl status gluster-blockd.service' for details.
gluster-block-cli.log
gluster-blockd.log

# gluster vol set hosting-volume group gluster-block
volume set: success

follows one of the many unsuccessful attempts
# gluster-block create hosting-volume/gluster-block ha 3 192.168.11.151,192.168.11.152,192.168.11.153 5GiB
client create failed: RPC: Remote system error - No such file or directory, unix addr /var/run/gluster-blockd.socket

Any idea what can be the problem and how I can solve it?
What else can I check for the problem?
Thank you !

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions