Niels de Vos
2015-Mar-08 00:22 UTC
[Gluster-users] glusterd and ctdb services whit problem
On Sat, Mar 07, 2015 at 07:06:22PM -0300, Marcelo Barbosa wrote:> hi guys, > > I'm have one problem with my gluster solution, I change all ip address > in my servers and service ctdb.service don't start, I have this > configurations:http://ur1.ca/jv8m1 anyone help me ?This error caught my eye: Mar 7 18:55:33 ped-dc01 systemd: Mounting /run/lock/ctdb... Mar 7 18:55:33 ped-dc01 systemd: Mounted /run/lock/ctdb. Mar 7 18:55:33 ped-dc01 mount: /sbin/mount.glusterfs: line 13: /dev/stderr: No such device or address Mar 7 18:55:33 ped-dc01 systemd: run-lock-ctdb.mount mount process exited, code=exited status=1 Mar 7 18:55:33 ped-dc01 systemd: Unit run-lock-ctdb.mount entered failed state. This suggests /run/lock/ctdb is not getting mounted, and hence ctdb can not access its lock file. This problem has been reported a few days back, and a patch has been merged in the master and release-3.6 branches: - http://review.gluster.org/9824 - http://review.gluster.org/9826 The next 3.6 and the upcoming 3.7 releases should not run into this issue anymore. HTH, Niels
Marcelo Barbosa
2015-Mar-11 13:14 UTC
[Gluster-users] glusterd and ctdb services whit problem
Niels, Very thank you, I change all IP address information in log of gluster using sed, I solved this problem with my hand, I suggest our create one simple command: 'change ip' for gluster, how can I send one patch about this ? Cheers, firemanxbr On Sat, Mar 7, 2015 at 9:22 PM, Niels de Vos <ndevos at redhat.com> wrote:> On Sat, Mar 07, 2015 at 07:06:22PM -0300, Marcelo Barbosa wrote: > > hi guys, > > > > I'm have one problem with my gluster solution, I change all ip address > > in my servers and service ctdb.service don't start, I have this > > configurations:http://ur1.ca/jv8m1 anyone help me ? > > This error caught my eye: > > Mar 7 18:55:33 ped-dc01 systemd: Mounting /run/lock/ctdb... > Mar 7 18:55:33 ped-dc01 systemd: Mounted /run/lock/ctdb. > Mar 7 18:55:33 ped-dc01 mount: /sbin/mount.glusterfs: line 13: > /dev/stderr: No such device or address > Mar 7 18:55:33 ped-dc01 systemd: run-lock-ctdb.mount mount process > exited, code=exited status=1 > Mar 7 18:55:33 ped-dc01 systemd: Unit run-lock-ctdb.mount entered > failed state. > > This suggests /run/lock/ctdb is not getting mounted, and hence ctdb can > not access its lock file. > > This problem has been reported a few days back, and a patch has been > merged in the master and release-3.6 branches: > > - http://review.gluster.org/9824 > - http://review.gluster.org/9826 > > The next 3.6 and the upcoming 3.7 releases should not run into this > issue anymore. > > HTH, > Niels >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.gluster.org/pipermail/gluster-users/attachments/20150311/4f8b2621/attachment.html>