gluster-block-target.service not starting due to dependency issues

Solution Verified - Updated -

Issue

  • The gluster-block-target.service is in failed state and 'start' operations exits with error code.
       #systemctl status gluster-block-target.service

gluster-block-target.service - Restore LIO kernel target configuration
   Loaded: loaded (/usr/lib/systemd/system/gluster-block-target.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2020-08-27 15:46:13 MST; 20h ago
  Process: 128360 ExecStart=/usr/bin/targetctl restore (code=exited, status=1/FAILURE)
 Main PID: 128360 (code=exited, status=1/FAILURE)
: return _default_decoder.decode(s)
: File "/usr/lib64/python2.7/json/decoder.py", line 366, in decode
: obj, end = self.raw_decode(s, idx=_w(s, 0).end())
: File "/usr/lib64/python2.7/json/decoder.py", line 384, in raw_decode
: raise ValueError("No JSON object could be decoded")
: ValueError: No JSON object could be decoded
: gluster-block-target.service: main process exited, code=exited, status=1/FAILURE
: Failed to start Restore LIO kernel target configuration.
: Unit gluster-block-target.service entered failed state.
: gluster-block-target.service failed.

Environment

  • Red Hat Gluster Storage 3.5

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content