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.
Error running with forever
See original GitHub issueWhen I run forever start index.js, I get this error and it will not start
warn: --minUptime not set. Defaulting to: 1000ms
warn: --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info: Forever processing file: index.js
Issue Analytics
- State:
- Created a year ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
Error running forever.js on Windows - “'C:\Program' is not ...
I am trying to run forever.js via the Windows command prompt and I get the following output: >npm i -g forever /my-project>forever start ......
Read more >node.js - NodeJS - Keep my App running with Forever
Run you app with pm2 instead of forever. Pm2 will restart the node server even after uncaught exceptions.
Read more >forever: command not found error [Solved] | bobbyhadz
Use npx to solve the error "forever: command not found", e.g. npx forever start app.js or install the package globally by running npm...
Read more >Error Forever Node.js module is not running - IBM
You try to access the Forever log file using the forever list command and receive an error Forever Node.js module is not running....
Read more >foreverjs/forever - Gitter
Hello. Have a question about one specific error. I have a forever running inside docker container and whenever I start it, then at...
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
ok so I fixed the issue nut I had to start with
node .. If I had loginrequired=true, most features do not work properly. when I disable it, it all works. But for some reason, my bot does not stay online. it keeps changing to waiting for restartNo activity.