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.

Sign up for GitHub

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

Jump to bottom

[cli] unable to talk to your watchman on \\.\pipe\watchman! (No such file or directory) #832

Open
karimhekal opened this issue Jul 16, 2020 · 8 comments
Open

[cli] unable to talk to your watchman on \\.\pipe\watchman! (No such file or directory) #832

karimhekal opened this issue Jul 16, 2020 · 8 comments

Comments

@karimhekal
Copy link

karimhekal commented Jul 16, 2020 •
edited
Loading

I always get this error when i start the project :

[cli] unable to talk to your watchman on \\.\pipe\watchman! (No such file or directory)

Watchman: watchman --no-pretty get-sockname returned with exit code=1, signal=null, stderr= 2020-07-16T08:11:17,351: [cli] unable to talk to your watchman on \\.\pipe\watchman-karim! (No such file or directory)

Reinstalled watchman but didn't work,
I'm on windows.
Here's the log

2020-07-16T07:38:00,279: [listener] Watchman 20200712.162157.0 f73e809 starting up on DESKTOP-NQ4OQGU
2020-07-16T07:38:00,297: [listener] failed to parse json from C:/Users/karim/AppData/Local/watchman/state: unable to open C:/Users/karim/AppData/Local/watchman/state: No such file or directory
2020-07-16T07:38:00,471: [listener] Unhandled win32 exception. Fatal error detected at:
#0 00007FF946C342CD CxxThrowException
#1 00007FF7AF185710 <failed to resolve symbol: Attempt to access invalid address.

#2 00007FF7AF210AA5 <failed to resolve symbol: Attempt to access invalid address.

#3 00007FF7AF213862 <failed to resolve symbol: Attempt to access invalid address.

#4 00007FF7AF224C58 <failed to resolve symbol: Attempt to access invalid address.

#5 00007FF7AF22574D <failed to resolve symbol: Attempt to access invalid address.

#6 00007FF7AF478940 <failed to resolve symbol: Attempt to access invalid address.

#7 00007FF96CB32784 BaseThreadInitThunk
#8 00007FF96F110C31 RtlUserThreadStart
the stack trace for the exception filter call is:
#0 00007FF96F16D4C4 memset
#1 00007FF96F156386 _C_specific_handler
#2 00007FF96F169FDD _chkstk
#3 00007FF96F0F51C8 RtlLookupFunctionEntry
#4 00007FF96F0F0DD1 RtlRaiseException
#5 00007FF96B8156B8 RaiseException
#6 00007FF946C342CD CxxThrowException
#7 00007FF7AF185710 <failed to resolve symbol: Attempt to access invalid address.

#8 00007FF7AF210AA5 <failed to resolve symbol: Attempt to access invalid address.

#9 00007FF7AF213862 <failed to resolve symbol: Attempt to access invalid address.

#10 00007FF7AF224C58 <failed to resolve symbol: Attempt to access invalid address.

#11 00007FF7AF22574D <failed to resolve symbol: Attempt to access invalid address.

#12 00007FF7AF478940 <failed to resolve symbol: Attempt to access invalid address.

#13 00007FF96CB32784 BaseThreadInitThunk
#14 00007FF96F110C31 RtlUserThreadStart
2020-07-16T07:49:19,012: [listener] Watchman 20200712.162157.0 f73e809 starting up on DESKTOP-NQ4OQGU
2020-07-16T07:49:19,015: [listener] failed to parse json from C:/Users/karim/AppData/Local/watchman/state: unable to open C:/Users/karim/AppData/Local/watchman/state: No such file or directory
2020-07-16T07:49:19,108: [listener] Unhandled win32 exception. Fatal error detected at:
#0 00007FF948B242CD CxxThrowException
#1 00007FF7AF185710 <failed to resolve symbol: Attempt to access invalid address.

#2 00007FF7AF210AA5 <failed to resolve symbol: Attempt to access invalid address.

#3 00007FF7AF213862 <failed to resolve symbol: Attempt to access invalid address.

#4 00007FF7AF224C58 <failed to resolve symbol: Attempt to access invalid address.

#5 00007FF7AF22574D <failed to resolve symbol: Attempt to access invalid address.

#6 00007FF7AF478940 <failed to resolve symbol: Attempt to access invalid address.

#7 00007FF96CB32784 BaseThreadInitThunk
#8 00007FF96F110C31 RtlUserThreadStart
the stack trace for the exception filter call is:
#0 00007FF96F16D4C4 memset
#1 00007FF96F156386 _C_specific_handler
#2 00007FF96F169FDD _chkstk
#3 00007FF96F0F51C8 RtlLookupFunctionEntry
#4 00007FF96F0F0DD1 RtlRaiseException
#5 00007FF96B8156B8 RaiseException
#6 00007FF948B242CD CxxThrowException
#7 00007FF7AF185710 <failed to resolve symbol: Attempt to access invalid address.

#8 00007FF7AF210AA5 <failed to resolve symbol: Attempt to access invalid address.

#9 00007FF7AF213862 <failed to resolve symbol: Attempt to access invalid address.

#10 00007FF7AF224C58 <failed to resolve symbol: Attempt to access invalid address.

#11 00007FF7AF22574D <failed to resolve symbol: Attempt to access invalid address.

#12 00007FF7AF478940 <failed to resolve symbol: Attempt to access invalid address.

#13 00007FF96CB32784 BaseThreadInitThunk
#14 00007FF96F110C31 RtlUserThreadStart
@fanzeyi
Copy link
Member

fanzeyi commented Jul 16, 2020

This looks like the same issue in #830

@wez
Copy link
Contributor

wez commented Jul 16, 2020

What version of Windows are you running?

@karimhekal
Copy link
Author

karimhekal commented Jul 16, 2020 •
edited
Loading

What version of Windows are you running?

I was on windows 8.1 then installed windows 10 ,
same issue on both

@wez
Copy link
Contributor

wez commented Jul 17, 2020

Please try this build:
https://github.com/facebook/watchman/suites/917211165/artifacts/11161515
which is from this commit with slightly better logging: 23dfe53

It will probably also be helpful to capture a trace for watchman.exe using Process Monitor
https://docs.microsoft.com/en-us/sysinternals/downloads/procmon
so that we can learn more about what is happening on that system.

@karimhekal
Copy link
Author

Same message ,
Captured this
Watchman.zip

@ibrahim019
Copy link

ibrahim019 commented Jul 21, 2020 •
edited
Loading

Please try this build:
https://github.com/facebook/watchman/suites/917211165/artifacts/11161515
which is from this commit with slightly better logging: 23dfe53

It will probably also be helpful to capture a trace for watchman.exe using Process Monitor
https://docs.microsoft.com/en-us/sysinternals/downloads/procmon
so that we can learn more about what is happening on that system.

I am on windows 8.1 and suddenly watchman isn't working at all. Tried re-installing watchman couple of times and tried this build

Added trace for watchman.exe using Process Monitor

Logfile_watchman.zip
https://drive.google.com/file/d/1dtUuonn8gu8PHSxrUb7BSAZJgX74c_dT/view?usp=sharing

Loading dependency graph...2020-07-22T00:46:57,898: [cli] unable to talk to your watchman on \.\pipe\watchman-ibrahim019! (No such file or directory)

Watchman: watchman --no-pretty get-sockname returned with exit code=1, signal=null, stderr= 2020-07-22T00:46:57,898: [cli] unable to talk to your watchman on \.\pipe\watchman-ibrahim019! (No such file or directory)

2020-07-22T00:43:07,714: [listener] Watchman 20200715.003534.0 23dfe53 starting up on ibrahim
2020-07-22T00:43:07,721: [listener] failed to parse json from C:/Users/ibrahim019/AppData/Local/watchman/state: unable to open C:/Users/ibrahim019/AppData/Local/watchman/state: No such file or directory
2020-07-22T00:43:07,866: [listener] Unhandled win32 exception code=3765269347. Fatal error detected at:
#0 00007FFDE88642CD CxxThrowException
#1 00007FF643775320 <failed to resolve symbol: Attempt to access invalid address.

#2 00007FF643800845 <failed to resolve symbol: Attempt to access invalid address.

#3 00007FF643803622 <failed to resolve symbol: Attempt to access invalid address.

#4 00007FF643814A18 <failed to resolve symbol: Attempt to access invalid address.

#5 00007FF64381550D <failed to resolve symbol: Attempt to access invalid address.

#6 00007FF643A65830 <failed to resolve symbol: Attempt to access invalid address.

#7 00007FFDF6431412 BaseThreadInitThunk
#8 00007FFDF6BA54F4 RtlUserThreadStart
the stack trace for the exception filter call is:
#0 00007FFDF6C2F173 memset
#1 00007FFDF6C11DD6 _C_specific_handler
#2 00007FFDF6C2345D _chkstk
#3 00007FFDF6BE4937 RtlRaiseException
#4 00007FFDF6BE3B5D RtlRaiseException
#5 00007FFDF3DF7AFC RaiseException
#6 00007FFDE88642CD CxxThrowException
#7 00007FF643775320 <failed to resolve symbol: Attempt to access invalid address.

#8 00007FF643800845 <failed to resolve symbol: Attempt to access invalid address.

#9 00007FF643803622 <failed to resolve symbol: Attempt to access invalid address.

#10 00007FF643814A18 <failed to resolve symbol: Attempt to access invalid address.

#11 00007FF64381550D <failed to resolve symbol: Attempt to access invalid address.

#12 00007FF643A65830 <failed to resolve symbol: Attempt to access invalid address.

#13 00007FFDF6431412 BaseThreadInitThunk
#14 00007FFDF6BA54F4 RtlUserThreadStart

@yangwencan2002
Copy link

@wez Is there a solution to this problem?Looking forward to your reply!

@yangwencan2002 yangwencan2002 mentioned this issue Aug 25, 2020
Open
facebook-github-bot pushed a commit that referenced this issue Aug 27, 2020
@fanzeyi @facebook-github-bot
disable UNIX domain socket support for older Windows versions
404c7b6 
Summary:
Fix for #830
#832

Windows only has UNIX domain socket support for Windows 10 17134+.

Reviewed By: wez

Differential Revision: D23331055

fbshipit-source-id: 11128a80c3dc49a651448be35001778a74a7d8c5
@wez
Copy link
Contributor

wez commented Aug 29, 2020

Please try this build: https://github.com/facebook/watchman/suites/1109228100/artifacts/15576123

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@wez @fanzeyi @yangwencan2002 @karimhekal @ibrahim019