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

Packager crashes, unable to talk to watchman #36

Closed
zenghuilipete opened this issue May 27, 2016 · 4 comments
Closed

Packager crashes, unable to talk to watchman #36

zenghuilipete opened this issue May 27, 2016 · 4 comments
Labels

Comments

@zenghuilipete
Copy link

After i clicked one simulator, red box appeared in simulator which shows "could not connect to development server". Bellow are console error info in packager output:
┌────────────────────────────────────────────────────────────────────────────┐
│ Running packager on port 8081. │
│ │
│ Keep this packager running while developing on any JS projects. Feel │
│ free to close this tab and run your own packager instance if you │
│ prefer. │
│ │
https://github.com/facebook/react-native
│ │
└────────────────────────────────────────────────────────────────────────────┘
Looking for JS files in
/Users/lizenghui/.Deco/tmp/Project

[11:25:02 AM] Building Dependency Graph
[11:25:02 AM] Crawling File System
[Hot Module Replacement] Server listening on /hot

React packager ready.

2016-05-27T11:25:02,749: [cli] failed to identify PDU: fill_buffer: EOF
2016-05-27T11:25:02,749: [cli] unable to talk to your watchman on /usr/local/var/run/watchman/lizenghui-state/sock! (Undefined error: 0)

/Users/lizenghui/Library/LaunchAgents/com.github.facebook.watchman.plist: service already loaded
2016-05-27T11:25:02,748: [cli] failed to identify PDU: fill_buffer: EOF
2016-05-27T11:25:02,749: [cli] unable to talk to your watchman on /usr/local/var/run/watchman/lizenghui-state/sock! (Undefined error: 0)

Watchman: watchman--no-pretty get-sockname returned with exit code 1 /Users/lizenghui/Library/LaunchAgents/com.github.facebook.watchman.plist: service already loaded
2016-05-27T11:25:02,748: [cli] failed to identify PDU: fill_buffer: EOF
2016-05-27T11:25:02,749: [cli] unable to talk to your watchman on /usr/local/var/run/watchman/lizenghui-state/sock! (Undefined error: 0)

ERROR watchman--no-pretty get-sockname returned with exit code 1 /Users/lizenghui/Library/LaunchAgents/com.github.facebook.watchman.plist: service already loaded
2016-05-27T11:25:02,748: [cli] failed to identify PDU: fill_buffer: EOF
2016-05-27T11:25:02,749: [cli] unable to talk to your watchman on /usr/local/var/run/watchman/lizenghui-state/sock! (Undefined error: 0)

Error: watchman--no-pretty get-sockname returned with exit code 1 /Users/lizenghui/Library/LaunchAgents/com.github.facebook.watchman.plist: service already loaded
2016-05-27T11:25:02,748: [cli] failed to identify PDU: fill_buffer: EOF
2016-05-27T11:25:02,749: [cli] unable to talk to your watchman on /usr/local/var/run/watchman/lizenghui-state/sock! (Undefined error: 0)

at ChildProcess.<anonymous> (/Users/lizenghui/.Deco/tmp/Project/node_modules/fb-watchman/index.js:198:18)
at emitTwo (events.js:100:13)
at ChildProcess.emit (events.js:185:7)
at maybeClose (internal/child_process.js:827:16)
at Socket.<anonymous> (internal/child_process.js:319:11)
at emitOne (events.js:90:13)
at Socket.emit (events.js:182:7)
at Pipe._onclose (net.js:475:12)

See http://facebook.github.io/react-native/docs/troubleshooting.html
for common problems and solutions.

Anyone come across this kind of situation?

@gdowens gdowens added the bug label May 27, 2016
@gdowens gdowens changed the title could not connect to development server Packager crashes, unable to talk to watchman May 27, 2016
@dsibiski
Copy link
Contributor

One solution that worked for me was after you quit Deco, go into Activity Monitor and kill any watchman process that is still running.

However, sometimes there is no watchman process there and I found I was still getting this error. However, I use tmux. I found that if I tried to start the packager manually "outside" of tmux (it might take a couple tries), it would end up working. Then trying back "inside" of tmux worked.

Kinda strange, but I was able to reproduce this process reliably.

@dsibiski
Copy link
Contributor

I found the "tmux" solution on this issue: facebook/watchman#69

@chouti
Copy link

chouti commented Jun 1, 2016

Yep, I was able to reproduce the same process, and also it's not possible to kill watch in Activity Monitor, as long as I quit the process, it start up automatically.

@gdowens
Copy link
Contributor

gdowens commented Jun 28, 2016

please reopen a separate issue if the error continues to persist.

@gdowens gdowens closed this as completed Jun 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants