NX Daemon server erroring out after moving to 13.7.1
See original GitHub issueI upgraded our workspace to latest NX version (13.7.1). However, I am getting following error with NX Daemon server
> NX Nx Daemon was not able to compute the project graph.
Here is the detailed log:
Messages from the log:
[NX Daemon Server] - 2022-01-31T22:54:54.560Z - Time taken for 'incremental hashing' 0.008351ms
[NX Daemon Server] - 2022-01-31T22:54:54.560Z - Error detected when recomputing project file map: ENOENT: no such file or directory, open '/Users/utsav.kapoor/thoughtspot/node_modules/@nrwl/workspace/presets/npm.json'
[NX Daemon Server] - 2022-01-31T22:54:57.389Z - [WATCHER]: 1 file(s) created or restored, 0 file(s) modified, 1 file(s) deleted
[NX Daemon Server] - 2022-01-31T22:54:57.709Z - Time taken for 'hash changed files from watcher' 118.756722ms
[NX Daemon Server] - 2022-01-31T22:54:57.709Z - Time taken for 'incremental hashing' 0.048084ms
[NX Daemon Server] - 2022-01-31T22:54:57.710Z - Error detected when recomputing project file map: ENOENT: no such file or directory, open '/Users/utsav.kapoor/thoughtspot/node_modules/@nrwl/workspace/presets/npm.json'
[NX Daemon Server] - 2022-01-31T22:55:01.667Z - Time taken for 'init hashing' 3956.459025ms
[NX Daemon Server] - 2022-01-31T22:55:03.502Z - Time taken for 'init hashing' 5791.451747ms
[NX Daemon Server] - 2022-01-31T23:06:33.319Z - [WATCHER]: js/ts-packages/create-ts-app/bin/create-ts-app was modified
[NX Daemon Server] - 2022-01-31T23:06:33.554Z - Time taken for 'hash changed files from watcher' 130.294604ms
[NX Daemon Server] - 2022-01-31T23:06:33.554Z - Time taken for 'incremental hashing' 0.117201ms
[NX Daemon Server] - 2022-01-31T23:06:33.619Z - [REQUEST]: Updated file-hasher based on watched changes, recomputing project graph...
[NX Daemon Server] - 2022-01-31T23:06:34.204Z - Time taken for 'read cache' 150.347964ms
[NX Daemon Server] - 2022-01-31T23:06:34.496Z - Time taken for 'build project graph' 165.5334ms
[NX Daemon Server] - 2022-01-31T23:06:34.516Z - Time taken for 'write cache' 19.723137ms
[NX Daemon Server] - 2022-01-31T23:06:34.516Z - Time taken for 'total execution time for createProjectGraph()' 494.093343ms
[NX Daemon Server] - 2022-01-31T23:06:34.595Z - Time taken for 'serialize graph' 79.272129ms
[NX Daemon Server] - 2022-01-31T23:07:45.573Z - [WATCHER]: Unsubscribed from changes within: /Users/utsav.kapoor/thoughtspot
[NX Daemon Server] - 2022-01-31T23:07:45.573Z - Server stopped because: "Lock file changed"```
Issue Analytics
- State:
- Created 2 years ago
- Reactions:14
- Comments:53
Top Results From Across the Web
Nx Daemon
Turning it Off. As of v13. 6.0, the Nx Daemon is enabled by default when running on your local machine. If you want...
Read more >nx cannot read properties of undefined (reading 'endswith')
I have nx 14.4.3 version in my system. And when I run nx serve it gives me the error :- TypeError: Cannot read...
Read more >MySQL 5.6 Reference Manual
This is the MySQL Reference Manual. It documents MySQL 5.6 through 5.6.51, as well as NDB Cluster releases.
Read more >Thermo ScientificTM AvizoTM Software 9
including but not limited to typographical, arithmetic or listing errors. ... Reading data across the network, for example from a file server, will...
Read more >OpenShift Virtualization OpenShift Container Platform 4.8
Managing config maps, secrets, and service accounts in virtual machines ... Moving a local virtual machine disk to a different node Expand section...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This happens to me after updating nx but only on ubuntu linux (my macos setup is fine). Disabling the nx daemon “fixes” the issue but this should definitely be fixed
Ok, I found some docs on the Daemon: https://nx.dev/guides/nx-daemon
The workaround:
export NX_DAEMON=false;
or in nx.json in tasksRunnerOptions.options you can disable the daemon:"useDaemonProcess": false
.Happy to help debugging this and enable the daemon anytime to tests fixes!