turborepo: [turborepo] failed to contact turbod/timed out waiting for initial fsevents cookie: filewatching failed to start
What version of Turborepo are you using?
1.9.1
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Describe the Bug
Per @nathanhammond’s request here, opening a new issue. See environmental details in “To Reproduce.”
When running a command, I get:
WARNING failed to contact turbod. Continuing in standalone mode: connection to turbo daemon process failed. Please ensure the following:
- the process identified by the pid in the file at /var/folders/7t/8fc_x2f96k3fq2w07f_y19xh0000gp/T/turbod/9ad75a386d6cc29e/turbod.pid is not running, and remove /var/folders/7t/8fc_x2f96k3fq2w07f_y19xh0000gp/T/turbod/9ad75a386d6cc29e/turbod.pid
- check the logs at /Users/myuser/Library/Application Support/turborepo/logs/9ad75a386d6cc29e-mfe-utilities.log
- the unix domain socket at /var/folders/7t/8fc_x2f96k3fq2w07f_y19xh0000gp/T/turbod/9ad75a386d6cc29e/turbod.sock has been removed
You can also run without the daemon process by passing --no-daemon
Daemon process/socket folder doesn’t exist (right after running the turbo command). But if I run turbo daemon start it creates a folder there, but it is empty.
Status:
> turbo daemon status
ERROR daemon is not running
Then:
> turbo daemon start
ERROR timeout while watchin directory: deadline has elapsed
> turbo daemon
2023-04-17T12:29:24.780-0400 [ERROR] turbod: error watching /Volumes/Code/Repos/Org/my-repo: timed out waiting for initial fsevents cookie: filewatching failed to start
Turbo error: watching /Volumes/Code/Repos/Org/my-repo: timed out waiting for initial fsevents cookie: filewatching failed to start
Note: This is on a secondary APFS (Case-sensitive) volume called Code. (I do this to avoid issues I’ve seen in past where code only breaks on server that is case sensitive.) Someone on the other issue mentioned this as well (and others after mentioned similar).
As suggested, tried npx create-turbo@latest with same results.
Log:
2023-04-17T12:34:33.127-0400 [ERROR] turbod: error watching /Volumes/Code/Repos/Org/my-turborepo: timed out waiting for initial fsevents cookie: filewatching failed to start
2023-04-17T12:34:34.124-0400 [ERROR] turbod: error watching /Volumes/Code/Repos/Org/my-turborepo: timed out waiting for initial fsevents cookie: filewatching failed to start
2023-04-17T12:34:35.122-0400 [ERROR] turbod: error watching /Volumes/Code/Repos/Org/my-turborepo: timed out waiting for initial fsevents cookie: filewatching failed to start
2023-04-17T12:34:51.350-0400 [ERROR] turbod: error watching /Volumes/Code/Repos/Org/my-turborepo: timed out waiting for initial fsevents cookie: filewatching failed to start
If I run the same on my primary partition, all is hunky dory. It creates the folder and the .pid and .sock are there.
Unsurprisingly (perhaps), both locations resolve to same:
> which turbo
/Users/ambrose.little/Library/pnpm/turbo
> turbo --version
1.9.1
Tried pnpm remove -g turbo and re-install. Same result. Running sudo turbo daemon start also fails the same way.
Expected Behavior
Should work/run the daemon without error. 😃
To Reproduce
OS + Version: 13.3.1 (22E261)
turbo version: 1.9.1 (also saw on 1.8.3/8)
pnpm: 8.1.1 (also with 7.31.0)
Shell: see same results in VS Code and Warp, using oh my zsh
Repository contents: can repro with npx create-turbo@latest
Repo filesystem permissions (on both the primary partition that works and secondary that doesn’t):
drwxrwxr-x ambrose.little staff
The only distinction I can see is that it’s on the external partition.
Reproduction Repo
No response
About this issue
- Original URL
- State: open
- Created 4 years ago
- Reactions: 8
- Comments: 17 (4 by maintainers)
bump
Here from https://github.com/vercel/turbo/issues/7413.
v2.0.0 of the VS Code LSP extension isn’t working for me on Windows 11.
Whenever I enable it I get these errors.
Same problem here
I’m on 1.11.2 now. Tried again.
Immediately after that:
Building is faster as noted before (even w/o the no daemon flag), but get warnings as below.
See a few of these (per package):
WARNING Failed to check if we can skip restoring outputs for @built/core-utility#build: GrpcFailure(DeadlineExceeded). Proceeding to check cacheFailed to mark outputs as cached for @built/core-utility#build: GrpcFailure(DeadlineExceeded)@mehulkar, let me know if you want me to try anything.
@mehulkar It seems to have fixed the reported issue. I now see this when building for each package:
Failed to mark outputs as cached for @mypkg/my-utility#build: rpc error: code = DeadlineExceeded desc = failed to load filewatching in timeWill duplicate my comment from related issue (might be helpful) https://github.com/vercel/turbo/issues/2034#issuecomment-1501195480
MacOS Ventura 13.2.1 Looks like permissions issue. I can start the daemon with
sudo. Without thesudo- no success.Another weird thing. Running
turbofrom nested project directory (no sudo) throwsERROR timeout while watchin directory: deadline has elapsederror:But running it from “home” directory gives no error:
Demon pid is diffrrent from the first example (tmp folder)
Same errors and console output here. Win10 64bit
I’m still getting all of this erors when using Turborepo LSP ext for vscode.
I use it under WSL2.
Hey @tyleralbee I can fix at least one of those. Will push a release of the LSP in the next hour or so, and ask you to try again. Thanks for being so detailed!
Any update? I am facing same problem on WSL2 Ubuntu environment.