search

ed00m / lsyncd

Automatically exported from code.google.com/p/lsyncd
GNU General Public License v2.0
0 stars 0 forks source link

cannot monitor all files when huge Files size and directories #65

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.i have around 17G data to monitor and they are all be put in different 
hierarchy directories. 

What is the expected output? What do you see instead?
1.i read the lipsyncd.status, it only shows me "Inotify watching 7933 
directories" and i find some directories are missing in this list; I should can 
find all my file hierarchy directories in this lipsyncd.status. 
2.when i modified the file inside this missing directories, no any update rsync 
activities
3.i expect any file modified can active any rsync.

What version of the product are you using? On what operating system?
Lsyncd Version: 2.0.4, Ubuntu 10.04

Please provide any additional information below.

Original issue reported on code.google.com by chungyan5@gmail.com on 8 Jun 2011 at 2:59

GoogleCodeExporter commented 9 years ago 
Additional Info. 

Command as: lsyncd -log scarce -nodaemon ~/.lipsyncd/lsyncd_config

Original comment by chungyan5@gmail.com on 8 Jun 2011 at 4:21

Attachments:

GoogleCodeExporter commented 9 years ago 
Try once witout exclude, maybe your excludeFrom is coming in the way?

Also check if the kernels
 /proc/sys/fs/inotify/max_user_watches
is set large enough.

Original comment by axk...@gmail.com on 11 Jun 2011 at 3:00

GoogleCodeExporter commented 9 years ago 
"less /proc/sys/fs/inotify/max_user_watches", it is "8192"

i removed the excludeFrom="/home/yan/.lipsyncd/lipsyncd_exclude_file", and it 
is the same result. lipsyncd.status shows me "Inotify watching 7995 
directories", still some directories does not include inside lipsyncd.status, 
and the file(s) inside cannot be sync to server.

Original comment by chungyan5@gmail.com on 11 Jun 2011 at 4:28

GoogleCodeExporter commented 9 years ago 
Several possibilties:

a) try increasing proc/sys/fs/inotify/max_user_watches
b) check whatever user Lsyncd runs with, has enough permissions for that 
directories
c) check the logfiles for any messages.

Original comment by axk...@gmail.com on 11 Jun 2011 at 4:47

GoogleCodeExporter commented 9 years ago 
a)i changed from 8192 to 16384, the lipsyncd.status as "Inotify watching 15397 
directories", then the previous un-monitoring directory is been monitoring now. 
I will take a look other directories when daily using. 
Or, i should reduce the number of directories i need to monitor. 

b)all files and directory is inside my home directory, so it is my own 
permissions
c)in my lsyncd_config, it is logfile    = "/home/yan/.lipsyncd/lipsyncd.log", 
but no nay log message.

Original comment by chungyan5@gmail.com on 12 Jun 2011 at 8:08

GoogleCodeExporter commented 9 years ago 
Similarly I just noticed on one of our servers that no notification was given 
that some of the directories could not be watched due to the 
/proc/sys/fs/inotify/max_user_watches not being set high enough.  In the past 
(pre 2.x) I did see notifications, not anymore :(

Original comment by randy.re...@gmail.com on 7 Jul 2011 at 8:36

GoogleCodeExporter commented 9 years ago 
I'll make the next version of Lsyncd quit in case it doesn't get a watch due to 
exceeding the limit.

Its always better not to run than in some kind of quirky state.

Original comment by axk...@gmail.com on 7 Jul 2011 at 9:59

GoogleCodeExporter commented 9 years ago 
Fixed for 2.0.5 (in SVN already)

Original comment by axk...@gmail.com on 18 Aug 2011 at 9:08