Could the oom killer be kicking in? is this a repeatable issue?
--
Lindsay Mathieson
___
Gluster-users mailing list
Gluster-users@gluster.org
http://lists.gluster.org/mailman/listinfo/gluster-users
That file exists but is empty.
Joe
On Wed, Jan 25, 2017 at 7:44 AM Samikshan Bairagya
wrote:
>
>
> On 01/25/2017 06:57 PM, Joseph Lorenzini wrote:
> > Hi Atin,
> >
> > I assume you are referring to the /var/log/glustershd.log. If so, that
> file
> > never gets created.
>
> You'd find the gluste
On 01/25/2017 06:57 PM, Joseph Lorenzini wrote:
Hi Atin,
I assume you are referring to the /var/log/glustershd.log. If so, that file
never gets created.
You'd find the glusterd log file as
/var/log/glusterfs/etc-glusterfs-glusterd.vol.log AFAR for glusterfs-3.8.
~ Samikshan
Joe
On Wed
Hi Atin,
I assume you are referring to the /var/log/glustershd.log. If so, that file
never gets created.
Joe
On Wed, Jan 25, 2017 at 6:14 AM Atin Mukherjee wrote:
> On Wed, Jan 25, 2017 at 5:15 PM, Joseph Lorenzini
> wrote:
>
> Hi all,
>
> I have recently started exploring the DFS solution sp
On Wed, Jan 25, 2017 at 5:15 PM, Joseph Lorenzini wrote:
> Hi all,
>
> I have recently started exploring the DFS solution space and was doing
> some basic setup and testing with gluster. I set up a pool of three nodes
> following the quick start guide. That seemed to work fine.
>
> However, short
Hi all,
I have recently started exploring the DFS solution space and was doing some
basic setup and testing with gluster. I set up a pool of three nodes
following the quick start guide. That seemed to work fine.
However, shortly after that, I noticed that one of the servers in the pool
was becomi
