Soumya, do you have any other idea of what to check on my side?
Many thanks,
Alessandro
Il giorno 10/giu/2015, alle ore 21:07, Alessandro De Salvo
alessandro.desa...@roma1.infn.it ha scritto:
Hi,
by looking at the connections I also see a strange problem:
# netstat -ltaupn |
CCin ganesha-devel to get more inputs.
In case of ipv6 enabled, only v6 interfaces are used by NFS-Ganesha.
commit - git show 'd7e8f255' , which got added in v2.2 has more details.
# netstat -ltaupn | grep 2049
tcp6 4 0 :::2049 :::*
LISTEN 32080/ganesha.nfsd
On 06/10/2015 05:49 AM, Alessandro De Salvo wrote:
Hi,
I have enabled the full debug already, but I see nothing special. Before
exporting any volume the log shows no error, even when I do a showmount (the
log is attached, ganesha.log.gz). If I do the same after exporting a volume
Hi Soumya,
OK, that trick worked, but now I'm back to the same situation of the
hanging showmount -e. Did you check the logs I sent yesterday? Now I'm
essentially back to the situation of the fir log (ganesha.log.gz) in all
cases.
Thanks,
Alessandro
On Wed, 2015-06-10 at 15:28 +0530,
Hi,
by looking at the connections I also see a strange problem:
# netstat -ltaupn | grep 2049
tcp6 4 0 :::2049 :::*
LISTEN 32080/ganesha.nfsd
tcp6 1 0 x.x.x.2:2049 x.x.x.2:33285 CLOSE_WAIT
-
tcp6 1 0
A better solution to the pid file problem is to add -p
/var/run/ganesha.nfsd.pid” to the OPTIONS in /etc/sysconfig/ganesha, so that it
becomes:
# cat /etc/sysconfig/ganesha
OPTIONS=-L /var/log/ganesha.log -f /etc/ganesha/ganesha.conf -N NIV_EVENT -p
/var/run/ganesha.nfsd.pid”
This is
On 06/09/2015 02:48 PM, Alessandro De Salvo wrote:
Hi,
OK, the problem with the VIPs not starting is due to the ganesha_mon
heartbeat script looking for a pid file called
/var/run/ganesha.nfsd.pid, while by default ganesha.nfsd v.2.2.0 is
creating /var/run/ganesha.pid, this needs to be
On 06/09/2015 02:06 PM, Alessandro De Salvo wrote:
Hi Soumya,
Il giorno 09/giu/2015, alle ore 08:06, Soumya Koduri skod...@redhat.com ha
scritto:
On 06/09/2015 01:31 AM, Alessandro De Salvo wrote:
OK, I found at least one of the bugs.
The /usr/libexec/ganesha/ganesha.sh has the
Hi,
OK, the problem with the VIPs not starting is due to the ganesha_mon heartbeat
script looking for a pid file called /var/run/ganesha.nfsd.pid, while by
default ganesha.nfsd v.2.2.0 is creating /var/run/ganesha.pid, this needs to be
corrected. The file is in
Hi,
Il giorno 09/giu/2015, alle ore 11:46, Soumya Koduri skod...@redhat.com ha
scritto:
On 06/09/2015 02:48 PM, Alessandro De Salvo wrote:
Hi,
OK, the problem with the VIPs not starting is due to the ganesha_mon
heartbeat script looking for a pid file called
Hi Soumya,
Il giorno 09/giu/2015, alle ore 08:06, Soumya Koduri skod...@redhat.com ha
scritto:
On 06/09/2015 01:31 AM, Alessandro De Salvo wrote:
OK, I found at least one of the bugs.
The /usr/libexec/ganesha/ganesha.sh has the following lines:
if [ -e /etc/os-release ]; then
On 06/09/2015 01:31 AM, Alessandro De Salvo wrote:
OK, I found at least one of the bugs.
The /usr/libexec/ganesha/ganesha.sh has the following lines:
if [ -e /etc/os-release ]; then
RHEL6_PCS_CNAME_OPTION=
fi
This is OK for RHEL 7, but does not work for = 7. I have
Another update: the fact that I was unable to use vol set ganesha.enable
was due to another bug in the ganesha scripts. In short, they are all
using the following line to get the location of the conf file:
CONF=$(cat /etc/sysconfig/ganesha | grep CONFFILE | cut -f 2 -d =)
First of all by default
On 06/09/2015 09:47 PM, Alessandro De Salvo wrote:
Another update: the fact that I was unable to use vol set ganesha.enable
was due to another bug in the ganesha scripts. In short, they are all
using the following line to get the location of the conf file:
CONF=$(cat /etc/sysconfig/ganesha |
Hi,
I have enabled the full debug already, but I see nothing special. Before
exporting any volume the log shows no error, even when I do a showmount (the
log is attached, ganesha.log.gz). If I do the same after exporting a volume
nfs-ganesha does not even start, complaining for not being able
OK, I can confirm that the ganesha.nsfd process is actually not
answering to the calls. Here it is what I see:
# rpcinfo -p
program vers proto port service
104 tcp111 portmapper
103 tcp111 portmapper
102 tcp111 portmapper
10
OK, I found at least one of the bugs.
The /usr/libexec/ganesha/ganesha.sh has the following lines:
if [ -e /etc/os-release ]; then
RHEL6_PCS_CNAME_OPTION=
fi
This is OK for RHEL 7, but does not work for = 7. I have changed it to the
following, to make it working:
if [ -e
On 06/08/2015 08:20 PM, Alessandro De Salvo wrote:
Sorry, just another question:
- in my installation of gluster 3.7.1 the command gluster features.ganesha
enable does not work:
# gluster features.ganesha enable
unrecognized word: features.ganesha (position 0)
Which version has full
Hi,
indeed, it does not work :-)
OK, this is what I did, with 2 machines, running CentOS 7.1, Glusterfs 3.7.1
and nfs-ganesha 2.2.0:
1) ensured that the machines are able to resolve their IPs (but this was
already true since they were in the DNS);
2) disabled NetworkManager and enabled network
Hi,
I have seen the demo video on ganesha HA,
https://www.youtube.com/watch?v=Z4mvTQC-efM
However there is no advice on the appropriate size of the shared volume. How is
it really used, and what should be a reasonable size for it?
Also, are the slides from the video available somewhere, as well
Great, many thanks Soumya!
Cheers,
Alessandro
Il giorno 08/giu/2015, alle ore 13:53, Soumya Koduri skod...@redhat.com ha
scritto:
Hi,
Please find the slides of the demo video at [1]
We recommend to have a distributed replica volume as a shared volume for
better
Hi,
Please find the slides of the demo video at [1]
We recommend to have a distributed replica volume as a shared volume for
better data-availability.
Size of the volume depends on the workload you may have. Since it is
used to maintain states of NLM/NFSv4 clients, you may calculate the
Sorry, just another question:
- in my installation of gluster 3.7.1 the command gluster features.ganesha
enable does not work:
# gluster features.ganesha enable
unrecognized word: features.ganesha (position 0)
Which version has full support for it?
- in the documentation the ccs and cman
23 matches
Mail list logo
