[Gluster-users] glusterd and ctdb services whit problem

[Niels de Vos]

On Wed, Mar 11, 2015 at 10:14:00AM -0300, Marcelo Barbosa wrote:
> 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 ?

Start by filing a bug against the glusterd component. The GlusterD guys
would be the ones that can check if the script is doing the right thing.
I think that only 'sed' is not sufficient. Some of the files under
/var/lib/glusterd/ have the hostname or ip-address in the filename. You
would need to rename them too (or maybe only on certain occasions?).

After you have a bug, and a Gerrit account with a public ssh-key
uploaded, you should clone the git repository that contains the
glusterfs sources:

    $ git clone ssh://ndevos@git.gluster.org/glusterfs

Some users are limited by their company firewall, they should also set a
HTTP password in their Gerrit settings:

    http://review.gluster.org/#/settings/http-password

That should (I did not try it) allow you to clone using the http(s?)
transport:

    $ git clone http://ndevos@review.gluster.org/glusterfs

Once you have the clone, start a new branch for your script:

    $ git checkout -t -b rename-storage-server origin/master

Make the changes, add the script and all:

    $ cp /path/to/script extras/change-ip.sh
    $ git add extras/change-ip.sh
    $ git commit extras/change-ip.sh
    (edit the commit message, have a one-line subject and some text on
     how to use this script and what it does. Add a Signed-off-line with
     your full name and email address.)

Check the commit:

    $ git show

If you would like to make some changes to the commit message, you can
use this command:

    $ git commit --amend

Once done, you can use this to submit the change to review.gluster.org:

    $ ./rfc.sh

While running that script, it will ask you for a bug number, enter the
number of the bug you opened earlier. When the script is done, the bug
should get a note that a patch was submitted for review.

Most of this should also be included in the wiki page that explains how
to submit patches. If something is missing there, anyone is free to add
more details:

    http://www.gluster.org/community/documentation/index.php/Simplified_dev_workflow

If you (or any one else) has difficulties with these instructions, reply
to this email. I'll try to explain whatever questions you have. Try to
keep the list on CC, you are most likely not the only one with the
questions :)

Good luck,
Niels


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