Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not syncing new files on CentOS 6.3 #148

Open
software2 opened this issue Jun 18, 2013 · 3 comments
Open

Not syncing new files on CentOS 6.3 #148

software2 opened this issue Jun 18, 2013 · 3 comments

Comments

@software2
Copy link

I have set up fileconveyor on a CentOS6.3 box which I intend to use to host several Magento commerce platforms.

FileConveyor is configured and works on startup (correctly syncing all the changed files) but does not seem to be picking up file changes while running.. See this simple test, where I:

  • Ran fileconveyor
  • Uploaded two images to the source directories
  • Waited 5 minutes with no activity
  • Shut down fileconveyor
  • Immediately re-ran fileconveyor
  • The two new files were instantly sync'd

magetest1
....
magetest2

Any advice would be appreciated
Ryan

@edmooney
Copy link

By chance are the files you're watching on a mounted windows share? If so it wont detect the changes. File Conveyor uses inotify to be alerted to changes on the linux file system. On startup I'm pretty sure it uses polling, which is why it finds the files after restarting.

@software2
Copy link
Author

I'm not sure, not being a massive linux person.. as far as I am aware it is the local file system.. Would the mount results answer that question?

~$ mount
/dev/xvda1 on / type ext3 (rw,noatime,barrier=0)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
none on /proc/xen type xenfs (rw)

How efficient is polling? Worst case is I am going to have to set a cron to restart fileconveyor!

@wimleers
Copy link
Owner

@software2 also first contacted me via e-mail, and for once I briefly replied there instead of directing him

I suspected the same as @edmooney:

It sounds like you're on a Linux system, which would mean that inotify is what powers instant file system change tracking. That doesn't work on networked file systems like gluster and NFS. Any chance you're using something like that?

I'm no Linux expert myself either, so I don't know how to interpret the mount output you provided, @software2. But it sure looks like you're on a file system where inotify does not work, or you must have somehow disabled inotify.

Could you please verify that inotify is working correctly by installing the inotify-tools package and then doing something like http://exyr.org/2011/inotify-run/? :) Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants