no sign of life

[ags799]

I have followed the instructions to install the plugin on my Vagrant VM.

When I vagrant up, I see

...
==> default: Waiting for the VM to receive an address...
==> default: Forwarding ports...
    default: -- 29324 => 29324
==> default: Waiting for machine to boot. This may take a few minutes...
...
==> default: Starting notify-forwarder ...
    default: Notify-forwarder: guest listening for file change notifications on 0.0.0.0:29324.
    default: Notify-forwarder: host sending file change notifications to 127.0.0.1:29324
    default: Notify-forwarder: host forwarding notifications on /Users/hello/my/friends to /vagrant
    default: Notify-forwarder: host sending file change notifications to 127.0.0.1:29324
    default: Notify-forwarder: host forwarding notifications on /Users/hello/my to /home/vagrant/my
...

But when I run a continuous build that should respond to file changes, it doesn't. It will respond to file changes made within the VM. Just not from the host.

Is there any way to debug this plugin? To view logs or something? Thanks.

[pward123]

The notification should go to the IP address of the guest and not the host (127.0.0.1), right?

If I run the vagrant plugin, notification doesn't work. However, if I manually run notify-forwarder with the IP address of the guest it works.

[pward123]

Ah, I didn't think about the port forwarding that's automatically configured by this plugin. For some reason the port forwarding setup is showing up in the parallels UI, but port forwarding itself is not working in parallels.

[youfeis]

So I'm pretty sure the port communication is working properly, but yeah, same here, no sign of life.

Anything we can do to debug this plugin?

[pward123]

I ended up creating a mashup of this plugin + vagrant-address. Instead of sending the notifications to a localhost port it sends them to the ip address that vagrant-address would return.

https://github.com/pward123/savi-vagrant-notify

[pward123]

Oh one other thing. Some watch type applications (like bazel-watcher in my case) don't catch the type of events that this plugin fires. I recommend something like iwatchnotify as a troubleshooting tool. It'll tell you if any inotify events are occurring.

In my case, I ended up creating my own bazel watcher to work around the problem.

[ags799]

I'm not using this plugin anymore, feel free to close this issue if that's appropriate.