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

Watchman does nothing #416

Closed
PaulBGD opened this issue Jan 7, 2017 · 5 comments
Closed

Watchman does nothing #416

PaulBGD opened this issue Jan 7, 2017 · 5 comments

Comments

@PaulBGD
Copy link

PaulBGD commented Jan 7, 2017

I'm using it with react native and it just doesn't respond to any commands except help or version. I've tried reinstalling it multiple times.

All commands that have to do with its actual function don't work, such as watchman shutdown-server

Version 4.7.0 on macOS Sierra

@wez
Copy link
Contributor

wez commented Jan 7, 2017

Can you share a paste of the exact output you're seeing from the watchman commands you're running?

Did you run through the troubleshooting guide?

https://facebook.github.io/watchman/docs/troubleshooting.html

Can you share information from your log file?

https://facebook.github.io/watchman/docs/troubleshooting.html#where-are-the-logs

@PaulBGD
Copy link
Author

PaulBGD commented Jan 7, 2017

Hi, I read through the troubleshooting guide and since no commands work and there's no output from watchman (I've left it running for 30 minutes) I can't find anything that applies to me.

I couldn't find my log in the brew installation place like it said in the troubleshooting page, but I found it at /usr/local/var/run/watchman/paul-state.
I checked the log and it only had entries from 2016, plus the version at the top was 4.6.0 (one version below my current.)

After deleting this folder and recreating it, watchman functions as expected. I guess this issue is fixed for me, but I'm not quite sure why.

@wez
Copy link
Contributor

wez commented Jan 8, 2017

I suspect that you hit #358

@PaulBGD
Copy link
Author

PaulBGD commented Jan 8, 2017

Yeah looks like it, I copied down my logs but they're all 3 months + old with no errors so I don't think they're very helpful.

@wez
Copy link
Contributor

wez commented Jan 9, 2017

OK, let's close this and chalk it up to another case of #358.

@wez wez closed this as completed Jan 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants