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

Haraka does not reload changed files #2950

Closed
wioxjk opened this issue Jun 7, 2021 · 2 comments
Closed

Haraka does not reload changed files #2950

wioxjk opened this issue Jun 7, 2021 · 2 comments

Comments

@wioxjk
Copy link

wioxjk commented Jun 7, 2021

Hi,

I am trying to understand why Haraka is not autoreloading configfiles when they are not edited by a editor on localhost.

I have tried sharing configs on a NFS-share, Gluster Volume and pulling it from an rsync-daemon but the autoreloading is not triggered. How does it work?

If I edit a file on localhost, I get the following:

inotifywait -r -e modify,attrib,close_write,move,create,delete /srv/haraka-outbound/config
Setting up watches.  Beware: since -r was given, this may take a while!
Watches established.
/srv/haraka-outbound/config/ CREATE 4913

But if localhost pulls the files from a remote rsync-server:

inotifywait -r -e modify,attrib,close_write,move,create,delete /srv/haraka-outbound/config
Setting up watches.  Beware: since -r was given, this may take a while!
Watches established.
/srv/haraka-outbound/config/ ATTRIB,ISDIR

Is this the reason that haraka does not see the changes to the files?
What is the recommended approach to sync configs between servers?

@msimerson
Copy link
Member

msimerson commented Jun 14, 2021

File watching in Haraka is has some limitations due to the node.js implementations. Our code for file change watching is in the haraka-config module.

@celesteking
Copy link
Contributor

file reload by polling has been implemented in haraka/haraka-config#58

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