As promised here the log file of the brick itself:
[2015-02-05 20:38:41.614491] I [glusterfsd.c:1959:main] 0-/usr/sbin/glusterfsd:
Started running /usr/sbin/glusterfsd version 3.5.3 (/usr/sbin/glusterfsd -s
gfs1a --volfile-id myvol.gfs1a.data-myvol-brick1 -p
/var/lib/glusterd/vols/myvol/run/gfs
On 02/05/2015 06:46 PM, ML mail wrote:
Dear Pranith
As asked you will find below the glusterd logfile including the log entries at
the boot of the server. On Debian the logfile is located in the
/var/log/glusterfs/etc-glusterfs-glusterd.vol.log file.
[2015-02-05 13:13:03.566059] I [glusterf
On Thu, Feb 05, 2015 at 01:16:54PM +, ML mail wrote:
> Dear Pranith
>
> As asked you will find below the glusterd logfile including the log
> entries at the boot of the server. On Debian the logfile is located in
> the /var/log/glusterfs/etc-glusterfs-glusterd.vol.log file.
This is the log fi
Dear Pranith
As asked you will find below the glusterd logfile including the log entries at
the boot of the server. On Debian the logfile is located in the
/var/log/glusterfs/etc-glusterfs-glusterd.vol.log file.
[2015-02-05 13:13:03.566059] I [glusterfsd.c:1959:main] 0-/usr/sbin/glusterd:
Sta
On 02/05/2015 04:08 AM, ML mail wrote:
Hi,
I have installed Gluster 3.5.3 on Debian 7 and have one single test volume
right now. Unfortunately after a reboot this volume does not get get started
automatically: the glusterfsd process for that volume is inexistant although
the glusterd process
Hi,
I have installed Gluster 3.5.3 on Debian 7 and have one single test volume
right now. Unfortunately after a reboot this volume does not get get started
automatically: the glusterfsd process for that volume is inexistant although
the glusterd process is running.
After a boot running "glus