search

gluster / gluster-containers

Dockerfiles (CentOS, Fedora, Red Hat) for GlusterFS
https://github.com/gluster/gluster-containers/pkgs/container/gluster-containers
223 stars 135 forks source link

Readiness probe failed: /usr/local/bin/status-probe.sh failed check: systemctl -q is-active glusterd.service #157

Open papanito opened 5 years ago

papanito commented 5 years ago

I've followed the setup guide using the gk-deploy script

./gk-deploy.sh --admin-key xxxx --user-key xxx -v -g

This went fine. However, the deployed container fail with

Readiness probe failed: /usr/local/bin/status-probe.sh failed check: systemctl -q is-active glusterd.service

The glusterd.service on the node is running:

$ systemctl status glusterd
● glusterd.service - GlusterFS, a clustered file-system server
   Loaded: loaded (/lib/systemd/system/glusterd.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2019-10-19 18:48:25 CEST; 1 day 17h ago
     Docs: man:glusterd(8)
  Process: 939 ExecStart=/usr/sbin/glusterd -p /var/run/glusterd.pid --log-level $LOG_LEVEL $GLUSTERD_
 Main PID: 955 (glusterd)
    Tasks: 10 (limit: 4915)
   Memory: 30.5M
   CGroup: /system.slice/glusterd.service
           └─955 /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level INFO
....
minhnnhat commented 4 years ago

I've followed the setup guide using the gk-deploy script

./gk-deploy.sh --admin-key xxxx --user-key xxx -v -g

This went fine. However, the deployed container fail with

Readiness probe failed: /usr/local/bin/status-probe.sh failed check: systemctl -q is-active glusterd.service

The glusterd.service on the node is running:

$ systemctl status glusterd
● glusterd.service - GlusterFS, a clustered file-system server
   Loaded: loaded (/lib/systemd/system/glusterd.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2019-10-19 18:48:25 CEST; 1 day 17h ago
     Docs: man:glusterd(8)
  Process: 939 ExecStart=/usr/sbin/glusterd -p /var/run/glusterd.pid --log-level $LOG_LEVEL $GLUSTERD_
 Main PID: 955 (glusterd)
    Tasks: 10 (limit: 4915)
   Memory: 30.5M
   CGroup: /system.slice/glusterd.service
           └─955 /usr/sbin/glusterd -p /var/run/glusterd.pid --log-level INFO
....

Hi @papanito , i met the same problem. Did you solve this ? Thank

papanito commented 4 years ago

Not really, as I am anyway looking into another solution for gluster in k8s: kadalu

A lightweight Persistent storage solution for Kubernetes / OpenShift using GlusterFS in background. There are still some issues bit the guys are very responsive and the solution looks promising - at least for my use case