[Gluster-users] gluster nfs-ganesha enable fails and is driving me crazy

[Soumya Koduri]

On 12/10/2015 02:51 AM, Marco Antonio Carcano wrote:
> Hi Kaleb,
>
> thank you very much for the quick reply
>
> I tried what you suggested, but I got the same error
>
> I tried both
>
> HA_CLUSTER_NODES="glstr01.carcano.local,glstr02.carcano.local"
> VIP_glstr01.carcano.local="192.168.65.250"
> VIP_glstr02.carcano.local="192.168.65.251"
>
> as well as
>
> HA_CLUSTER_NODES="glstr01.carcano.local,glstr02.carcano.local"
> VIP_glstr01_carcano_local="192.168.65.250"
> VIP_glstr02_carcano_local="192.168.65.251"
>
> Finally I reiinstalled everything and tried also with hostname rather
> than FQDN, that is
>
> HA_NAME="ganesha-ha-360"
> HA_VOL_SERVER="glstr01"
> HA_CLUSTER_NODES="glstr01v,glstr02v"
> VIP_glstr01v="192.168.65.250"
> VIP_glstr02v="192.168.65.251"
>
> but still no luck - Maybe do you have any other advice?
>

Could you check glusterd logs now? Does it still complain with below error?

[glusterd-ganesha.c:264:glusterd_op_set_ganesha] 0-management: Initial 
NFS-Ganesha set up failed

Also please check below log files for the errors/warnings thrown during 
the setup -

'/var/log/messages'
'/var/log/pacemaker.log'
'/var/log/ganesha.log'
'/var/log/ganesha-gfapi.log'

Thanks.
Soumya

> Kind regards
>
> Marco
>
>
> Il 08/12/15 13:30, Kaleb KEITHLEY ha scritto:
>> On 12/08/2015 03:46 AM, Marco Antonio Carcano wrote:
>>> Hi,
>>>
>>> /etc/ganesha/ganesha-ha.conf
>>>
>>> HA_NAME="ganesha-ha-360"
>>> HA_VOL_SERVER="glstr01.carcano.local"
>>> HA_CLUSTER_NODES="glstr01.carcano.local,glstr02.carcano.local"
>>> VIP_server1="192.168.65.250"
>>> VIP_server2="192.168.65.251"
>>>
>> change your /etc/ganesha/ganesha-ha.conf file:
>>
>> HA_NAME="ganesha-ha-360"
>> HA_VOL_SERVER="glstr01.carcano.local"
>> HA_CLUSTER_NODES="glstr01.carcano.local,glstr02.carcano.local"
>> VIP_glstr01.carcano.local="192.168.65.250"
>> VIP_glstr02.carcano.local="192.168.65.251"
>>
>> I'd change the HA_NAME to something else too, but as long as you don't
>> set up another cluster on the same network you should be fine.
>>
>> --
>>
>> Kaleb
>>
>
> _______________________________________________
> Gluster-users mailing list
> Gluster-users at gluster.org
> http://www.gluster.org/mailman/listinfo/gluster-users