[Gluster-users] Weekly Community Meeting 14/Sep/2016 - Minutes

2016-09-14 Thread Samikshan Bairagya

Hi everyone,

Thanks everyone for your participation. The minutes and logs for today's 
meeting can be accessed from the following links:


 - Minutes: 
https://meetbot.fedoraproject.org/gluster-meeting/2016-09-14/gluster_community_meeting.2016-09-14-12.00.html
 - Minutes (text): 
https://meetbot.fedoraproject.org/gluster-meeting/2016-09-14/gluster_community_meeting.2016-09-14-12.00.txt
 - Log: 
https://meetbot.fedoraproject.org/gluster-meeting/2016-09-14/gluster_community_meeting.2016-09-14-12.00.log.html


kshlm will be hosting the meeting next week (21st September, 2016) at 
#gluster-meeting. See you all then.


~ Samikshan

Meeting summary
---
* Roll call  (samikshan, 12:01:53)

* Next week's host  (samikshan, 12:04:56)
  * kshlm is next week's host  (samikshan, 12:06:22)

* GlusterFS 4.0  (samikshan, 12:06:53)

* GlusterFS-3.9  (samikshan, 12:12:02)
  * ACTION: RC tagging to be done by this week for 3.9 by aravindavk
(samikshan, 12:14:44)
  *

http://www.gluster.org/pipermail/gluster-devel/2016-September/050851.html
(aravindavk, 12:15:33)

* GlusterFS-3.8  (samikshan, 12:16:54)

* GlusterFS-3.7  (samikshan, 12:19:44)

* Project Infrastructure  (samikshan, 12:27:03)

* NFS-Ganesha  (samikshan, 12:33:27)

* Samba  (samikshan, 12:36:59)

* AI's from last week  (samikshan, 12:40:16)

* aravindavk to update the lists with the target dates for the 3.9
  release  (samikshan, 12:41:03)
  * LINK:

http://www.gluster.org/pipermail/gluster-devel/2016-September/050851.html
(aravindavk, 12:43:07)

* rastar_afk/ndevos/jdarcy to improve cleanup to control the processes
  that test starts  (samikshan, 12:44:26)
  * ACTION: rastar_afk/ndevos/jdarcy to improve cleanup to control the
processes that test starts  (samikshan, 12:46:06)

* Open floor  (samikshan, 12:46:54)
  * LINK: https://www.gluster.org/events/summit2016/ says September 12,
which was yesterday.  (jdarcy, 12:49:46)
  * ACTION: jdarcy will bug amye regarding a public announcement for
Gluster Summit talks  (samikshan, 12:51:24)

Meeting ended at 12:58:39 UTC.




Action Items

* RC tagging to be done by this week for 3.9 by aravindavk
* rastar_afk/ndevos/jdarcy to improve cleanup to control the processes
  that test starts
* jdarcy will bug amye regarding a public announcement for Gluster
  Summit talks




Action Items, by person
---
* aravindavk
  * RC tagging to be done by this week for 3.9 by aravindavk
* jdarcy
  * rastar_afk/ndevos/jdarcy to improve cleanup to control the processes
that test starts
  * jdarcy will bug amye regarding a public announcement for Gluster
Summit talks
* ndevos
  * rastar_afk/ndevos/jdarcy to improve cleanup to control the processes
that test starts
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* samikshan (90)
* kshlm (30)
* jdarcy (17)
* nigelb (9)
* aravindavk (5)
* zodbot (4)
* ankitraj (3)
* Saravanakmr (2)
* partner (2)
* ndevos (1)
* rafi (1)
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users


[Gluster-users] Reminder: Weekly Gluster Community Meeting

2016-09-14 Thread Samikshan Bairagya

Hi all,

The weekly Gluster community meeting is about to take place in ~90 minutes.

Meeting details:
- Location: #gluster-meeting on Freenode IRC
(https://webchat.freenode.net/?channels=gluster-meeting)
- Date: Every Wednesday
- Time: 12:00 UTC
(on your terminal, run: date -d "12:00 UTC")

Please find the agenda to be discussed in the meeting here: 
https://public.pad.fsfe.org/p/gluster-community-meetings.


Currently the following topics are listed:
 - GlusterFS 4.0
 - GlusterFS 3.9
 - GlusterFS 3.8
 - GlusterFS 3.7
 - GlusterFS 3.6
 - Project infrastructure
 - NFS Ganesha
 - Samba
 - Last week's AI's
 - Open floor

If you have any other topic to be discussed please add so under the Open 
floor section as a sub-topic.


Looking forward to your participation.

Thanks and Regards,

Samikshan Bairagya
___
Gluster-users mailing list
Gluster-users@gluster.org
http://www.gluster.org/mailman/listinfo/gluster-users


Re: [Gluster-users] geo-rep: -1 (Directory not empty) warning - STATUS Faulty

2016-09-14 Thread ML mail
As requested you will find below the last few 100 lines of the geo-rep log file 
from the master node.


FILE: 
/var/log/glusterfs/geo-replication/cloud-pro/ssh%3A%2F%2Froot%40192.168.20.107%3Agluster%3A%2F%2F127.0.0.1%3Acloud-pro-geo.log


[2016-09-13 19:39:48.686060] I [syncdutils(/data/cloud-pro/brick):220:finalize] 
: exiting.
[2016-09-13 19:39:48.688112] I [repce(agent):92:service_loop] RepceServer: 
terminating on reaching EOF.
[2016-09-13 19:39:48.688461] I [syncdutils(agent):220:finalize] : exiting.
[2016-09-13 19:39:49.518510] I [monitor(monitor):343:monitor] Monitor: 
worker(/data/cloud-pro/brick) died in startup phase
[2016-09-13 19:39:59.675405] I [monitor(monitor):266:monitor] Monitor: 

[2016-09-13 19:39:59.675740] I [monitor(monitor):267:monitor] Monitor: starting 
gsyncd worker
[2016-09-13 19:39:59.768181] I [gsyncd(/data/cloud-pro/brick):710:main_i] 
: syncing: gluster://localhost:cloud-pro -> 
ssh://r...@gfs1geo.domain.tld:gluster://localhost:cloud-pro-geo
[2016-09-13 19:39:59.768640] I [changelogagent(agent):73:__init__] 
ChangelogAgent: Agent listining...
[2016-09-13 19:40:02.554076] I 
[master(/data/cloud-pro/brick):83:gmaster_builder] : setting up xsync 
change detection mode
[2016-09-13 19:40:02.554500] I [master(/data/cloud-pro/brick):367:__init__] 
_GMaster: using 'rsync' as the sync engine
[2016-09-13 19:40:02.555332] I 
[master(/data/cloud-pro/brick):83:gmaster_builder] : setting up changelog 
change detection mode
[2016-09-13 19:40:02.555600] I [master(/data/cloud-pro/brick):367:__init__] 
_GMaster: using 'rsync' as the sync engine
[2016-09-13 19:40:02.556711] I 
[master(/data/cloud-pro/brick):83:gmaster_builder] : setting up 
changeloghistory change detection mode
[2016-09-13 19:40:02.556983] I [master(/data/cloud-pro/brick):367:__init__] 
_GMaster: using 'rsync' as the sync engine
[2016-09-13 19:40:04.692655] I [master(/data/cloud-pro/brick):1249:register] 
_GMaster: xsync temp directory: 
/var/lib/misc/glusterfsd/cloud-pro/ssh%3A%2F%2Froot%40192.168.20.107%3Agluster%3A%2F%2F127.0.0.1%3Acloud-pro-geo/6b844f56a11ecd24d5e36242f045e58c/xsync
[2016-09-13 19:40:04.692945] I 
[resource(/data/cloud-pro/brick):1491:service_loop] GLUSTER: Register time: 
1473795604
[2016-09-13 19:40:04.724827] I [master(/data/cloud-pro/brick):510:crawlwrap] 
_GMaster: primary master with volume id d99af2fa-439b-4a21-bf3a-38f3849f87ec ...
[2016-09-13 19:40:04.734505] I [master(/data/cloud-pro/brick):519:crawlwrap] 
_GMaster: crawl interval: 1 seconds
[2016-09-13 19:40:04.754487] I [master(/data/cloud-pro/brick):1163:crawl] 
_GMaster: starting history crawl... turns: 1, stime: (1473688054, 0), etime: 
1473795604
[2016-09-13 19:40:05.757395] I [master(/data/cloud-pro/brick):1192:crawl] 
_GMaster: slave's time: (1473688054, 0)
[2016-09-13 19:40:05.832189] E [repce(/data/cloud-pro/brick):207:__call__] 
RepceClient: call 28167:140561674450688:1473795605.78 (entry_ops) failed on 
peer with OSError
[2016-09-13 19:40:05.832458] E 
[syncdutils(/data/cloud-pro/brick):276:log_raise_exception] : FAIL: 
Traceback (most recent call last):
File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/gsyncd.py", line 
201, in main
main_i()
File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/gsyncd.py", line 
720, in main_i
local.service_loop(*[r for r in [remote] if r])
File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/resource.py", line 
1497, in service_loop
g3.crawlwrap(oneshot=True)
File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/master.py", line 
571, in crawlwrap
self.crawl()
File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/master.py", line 
1201, in crawl
self.changelogs_batch_process(changes)
File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/master.py", line 
1107, in changelogs_batch_process
self.process(batch)
File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/master.py", line 
992, in process
self.process_change(change, done, retry)
File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/master.py", line 
934, in process_change
failures = self.slave.server.entry_ops(entries)
File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/repce.py", line 
226, in __call__
return self.ins(self.meth, *a)
File "/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/repce.py", line 
208, in __call__
raise res
OSError: [Errno 39] Directory not empty
[2016-09-13 19:40:05.834218] I [syncdutils(/data/cloud-pro/brick):220:finalize] 
: exiting.
[2016-09-13 19:40:05.836263] I [repce(agent):92:service_loop] RepceServer: 
terminating on reaching EOF.
[2016-09-13 19:40:05.836611] I [syncdutils(agent):220:finalize] : exiting.
[2016-09-13 19:40:06.558499] I [monitor(monitor):343:monitor] Monitor: 
worker(/data/cloud-pro/brick) died in startup phase
[2016-09-13 19:40:16.715217] I [monitor(monitor):266:monitor] Monitor: 

[2016-09-13 19:40:16.71551