[Gluster-users] Changing the server hostname

[Franco Broi]

The hostname of the machine didn't actually change but the interface
that I wanted to export the filesystem over did. I went through all the
files in /var/lib/glusterd changing all instances of the hostname to the
hostname of the interface, ie;

hostname was nas1
new interface is nas1-10g

Same thing happened when I tried to start glusterd. I ran glusterd
-debug and searched the log for anything obvious but couldn't find
anything.

I eventually got desperate and reverted everything and it's back up and
running.

The new system was using a newer version of gluster, glusterfs 3.4.1 the
old one is  3.4.0, could that have something to do with it?

I've got 2 new servers I want to add to the system, these are running
the newer version of gluster so I thought it best to upgrade the old
server before doing that.

Cheers,


On Tue, 2014-01-07 at 10:46 +0530, Vijay Bellur wrote: 
> On 01/07/2014 09:05 AM, Franco Broi wrote:
> >
> > What are the steps to change a server's hostname? The documentation
> > appears to have a broken link to the article in Gluster 3.2: Brick
> > Restoration - Replace Crashed Server
> >
> > I have rebuilt my 2 gluster servers and restored the files
> > in /var/lib/glusterd but I can't start gluster, I assume because I have
> > changed the IP address.
> >
> > All I get in my log file is this:
> >
> > [2014-01-07 03:08:53.771575] E [rpc-transport.c:253:rpc_transport_load] 0-rpc-transport: /usr/lib64/glusterfs/3.4.1/rpc-transport/rdma.so: cannot open shared object file: No such file or directory
> > [2014-01-07 03:08:53.771605] W [rpc-transport.c:257:rpc_transport_load] 0-rpc-transport: volume 'rdma.management': transport-type 'rdma' is not valid or not found on this machine
> > [2014-01-07 03:08:53.771615] W [rpcsvc.c:1389:rpcsvc_transport_create] 0-rpc-service: cannot create listener, initing the transport failed
> > [2014-01-07 03:08:53.810098] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-0
> > [2014-01-07 03:08:53.810122] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-1
> > [2014-01-07 03:08:53.810132] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-2
> > [2014-01-07 03:08:53.810141] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-3
> > [2014-01-07 03:08:53.810149] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-4
> > [2014-01-07 03:08:53.810158] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-5
> > [2014-01-07 03:08:53.810167] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-6
> > [2014-01-07 03:08:53.810175] E [glusterd-store.c:1858:glusterd_store_retrieve_volume] 0-: Unknown key: brick-7
> > [2014-01-07 03:08:54.201857] E [glusterd-store.c:2487:glusterd_resolve_all_bricks] 0-glusterd: resolve brick failed in restore
> 
> This seems to point to a failure in identifying a previously know brick 
> during glusterd start. It might be worthwhile to check 
> /var/lib/glusterd/vols/<volname>/bricks to see if it contains the old IP 
> address/hostname.
> 
> -Vijay