Hey Atul,
You'd need to provide adequate information to us to get to the actual
issue. I'd recommend you to provide the following:
1. The detailed description of the problem statement.
2. Steps you did in the cluster.
3. log files from all the nodes in the cluster.
You can file a bug for the sam
I could see that glusterd process is up from the log file. Aren't you able
to run any gluster commands on the same node?
~Atin
On Tue, Jul 5, 2016 at 4:05 PM, Atul Yadav wrote:
> Hi Team,
>
> Please go through the attachment
>
> Thank you
> Atul Yadav
>
> On Tue, Jul 5, 2016 at 3:55 PM, Samiksh
On 07/05/2016 03:15 PM, Atul Yadav wrote:
Hi Atin,
please go through the attachment for log file.
Waiting for your input
Hi Atul,
The glusterd log file can be found here:
/var/log/glusterfs/usr-local-etc-glusterfs-glusterd.vol.log
Sharing that instead of a RAR archive would make th
Why don't you share the glusterd log file?
On Tue, Jul 5, 2016 at 12:53 PM, Atul Yadav wrote:
> Hi ,
>
> After restarting the service. service entered in to the fail state.
> [root@master1 ~]# /etc/init.d/glusterd restart
> Stopping glusterd: [FAILED]
> St
Hi ,
After restarting the service. service entered in to the fail state.
[root@master1 ~]# /etc/init.d/glusterd restart
Stopping glusterd: [FAILED]
Starting glusterd: [FAILED]
Note: This behavior only happening over r
On Tue, Jul 5, 2016 at 11:01 AM, Atul Yadav wrote:
> Hi All,
>
> The glusterfs environment details are given below:-
>
> [root@master1 ~]# cat /etc/redhat-release
> CentOS release 6.7 (Final)
> [root@master1 ~]# uname -r
> 2.6.32-642.1.1.el6.x86_64
> [root@master1 ~]# rpm -qa | grep -i gluster
>
Hi All,
The glusterfs environment details are given below:-
[root@master1 ~]# cat /etc/redhat-release
CentOS release 6.7 (Final)
[root@master1 ~]# uname -r
2.6.32-642.1.1.el6.x86_64
[root@master1 ~]# rpm -qa | grep -i gluster
glusterfs-rdma-3.8rc2-1.el6.x86_64
glusterfs-api-3.8rc2-1.el6.x86_64
gl
