question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Cli wont work, daemon keeps stopping

See original GitHub issue

Current Behavior

When i try to do anything in the nx cli it gives me this error

 NX   Nx Daemon was not able to compute the project graph.

   Log file with the error: C:\Users\vincent\coding\projects-new\node_modules\.cache\nx\d\daemon-error.log
   Please file an issue at https://github.com/nrwl/nx
   Nx Daemon is going to be disabled until you run "nx reset".


 NX   spawn ENAMETOOLONG

C:\Users\vincent\coding\projects-new\node_modules.cache\nx\d\daemon-error.log:

Failed to start the Nx Daemon process.
Messages from the log:

NX   spawn ENAMETOOLONG

More information: C:\Users\vincent\coding\projects-new\node_modules.cache\nx\d\daemon.log

 NX   spawn ENAMETOOLONG

Expected Behavior

I would like the cli to work like normal

Is this a regression?

No

Steps to Reproduce

https://github.com/VincentThomas06/Projects

Failure Logs

 NX   Nx Daemon was not able to compute the project graph.

   Log file with the error: C:\Users\vincent\coding\projects-new\node_modules\.cache\nx\d\daemon-error.log
   Please file an issue at https://github.com/nrwl/nx
   Nx Daemon is going to be disabled until you run "nx reset".


 >  NX   spawn ENAMETOOLONG

C:\Users\vincent\coding\projects-new\node_modules.cache\nx\d\daemon-error.log:

Failed to start the Nx Daemon process.
Messages from the log:

 >  NX   spawn ENAMETOOLONG

More information: C:\Users\vincent\coding\projects-new\node_modules.cache\nx\d\daemon.log

 >  NX   spawn ENAMETOOLONG

Environment

Node : 16.13.1
   OS   : win32 x64
   yarn : 1.22.17

   nx : 13.8.3
   @nrwl/angular : undefined
   @nrwl/cli : 13.8.3
   @nrwl/cypress : 13.8.1
   @nrwl/detox : undefined
   @nrwl/devkit : 13.8.3
   @nrwl/eslint-plugin-nx : 13.8.1
   @nrwl/express : undefined
   @nrwl/jest : 13.8.1
   @nrwl/js : 13.8.1
   @nrwl/linter : 13.8.1
   @nrwl/nest : 13.8.3
   @nrwl/next : undefined
   @nrwl/node : 13.8.1
   @nrwl/nx-cloud : 13.1.4
   @nrwl/react : 13.8.3
   @nrwl/react-native : undefined
   @nrwl/schematics : undefined
   @nrwl/storybook : 13.8.3
   @nrwl/tao : 13.8.3
   @nrwl/web : 13.8.1
   @nrwl/workspace : 13.8.3
   typescript : 4.2.4
   rxjs : 7.5.4
   ---------------------------------------
   Community plugins:

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:2
  • Comments:8 (1 by maintainers)

github_iconTop GitHub Comments

5reactions
slewis30328commented, Feb 25, 2022

I was able to resolve the issue by committing my unsaved changes. Sounds crazy, but that fixed it. I was doing my upgrade in a fresh repo. Have a very large code base and I copied the files over into the new nix workspace after I created the shell for my apps. The files had not been committed and I was trying to run lints, builds, etc. only way to get nx cli to keep going was to commit the files. Not sure if that is considered a “fix”, but it’s definitely a work around that enabled me to keep working.

Sent from my iPhone

On Feb 24, 2022, at 3:57 PM, karelinda @.***> wrote:

So…there is a solution!!!.. Somebody!!!

— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.

0reactions
jwilbur-godaddycommented, Apr 28, 2022

I was able to resolve the issue by committing my unsaved changes. Sounds crazy, but that fixed it. I was doing my upgrade in a fresh repo. Have a very large code base and I copied the files over into the new nix workspace after I created the shell for my apps. The files had not been committed and I was trying to run lints, builds, etc. only way to get nx cli to keep going was to commit the files. Not sure if that is considered a “fix”, but it’s definitely a work around that enabled me to keep working. Sent from my iPhone On Feb 24, 2022, at 3:57 PM, karelinda @.***> wrote:  So…there is a solution!!!.. Somebody!!! — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you commented.

I second this. This made this work for me too. Weird.

Read more comments on GitHub >

github_iconTop Results From Across the Web

start-stop-daemon error - command line - Stack Overflow
Show activity on this post. to ensure that start-stop-daemon is not attempting to interpret any of $ARGS but is instead passing all of...
Read more >
» Cephadm » Troubleshooting - Ceph Documentation
You might need to investigate why a cephadm command failed or why a certain service no longer runs properly. Cephadm deploys daemons as ......
Read more >
Command-Line Interface - Gradle User Manual
Run gradle --status to list running and recently stopped Gradle daemons. Only displays daemons of the same Gradle version. --stop (Standalone command). Run...
Read more >
Command Line Flags - osquery - Read the Docs
The osquery shell and daemon use optional command-line (CLI) flags to control ... Flags that do not control startup settings may be included...
Read more >
Run as a Service - Sonatype Help
If the Nexus Repository process is already stopped, and the service is failing to start, first confirm there is no log output being...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found