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.

Error: Server terminated unexpectedly with code: null signal: SIGTERM

See original GitHub issue

`> @ start C:\mohan\experiments\react\boilerplates\MyApp

babel-node tools/run start

[12:12:57] Starting ‘start’… [12:12:57] Starting ‘clean’… [12:12:58] Finished ‘clean’ after 49 ms [12:12:58] Starting ‘bound copy’… [12:12:58] Finished ‘bound copy’ after 162 ms webpack built 869f3b2ac4a25f52f21e in 9500ms Child Time: 9500ms Asset Size Chunks Chunk Names main.js?869f3b2ac4a25f52f21e 4.19 MB 0 [emitted] main Child Time: 8319ms Asset Size Chunks Chunk Names …/…/server.js 197 kB 0 [emitted] main …/…/server.js.map 213 kB 0 [emitted] main webpack: bundle is now VALID. webpack: bundle is now INVALID. webpack building… webpack built 869f3b2ac4a25f52f21e in 502ms Child Time: 502ms Child Time: 8319ms Asset Size Chunks Chunk Names …/…/server.js 197 kB 0 [emitted] main …/…/server.js.map 213 kB 0 [emitted] main webpack: bundle is now VALID. C:\mohan\experiments\react\boilerplates\MyApp\tools\runServer.js:71 throw new Error(`Server terminated unexpectedly with code: ${ cod ^

Error: Server terminated unexpectedly with code: null signal: SIGTERM at ChildProcess.server.once (runServer.js:53:15) at ChildProcess.g (events.js:286:16) at emitTwo (events.js:106:13) at ChildProcess.emit (events.js:191:7) at Process.ChildProcess._handle.onexit (internal/child_process.js:204

npm ERR! Windows_NT 6.1.7601 npm ERR! argv “C:\Program Files\nodejs\node.exe” "C:\Program Files\n npm ERR! node v6.2.0 npm ERR! npm v3.8.9 npm ERR! code ELIFECYCLE npm ERR! @ start: babel-node tools/run start npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the @ start script ‘babel-node tools/run start’. npm ERR! Make sure you have the latest version of node.js and npm install npm ERR! If you do, this is most likely a problem with the package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! babel-node tools/run start npm ERR! You can get information on how to open an issue for this project npm ERR! npm bugs npm ERR! Or if that isn’t available, you can get their info via: npm ERR! npm owner ls npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request: npm ERR! C:\mohan\experiments\react\boilerplates\MyApp\npm-debug.log`

I am new to react starter kit. Following things i have done

  1. git clone -o react-starter-kit -b master --single-branch https://github.com/kriasoft/react-starter-kit.git MyApp
  2. npm install
  3. npm start [Hed this issue]

Please help.

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Reactions:3
  • Comments:18 (2 by maintainers)

github_iconTop GitHub Comments

4reactions
iDVBcommented, Dec 27, 2016

@pvijeh Woot! FIXED Thanks! You have no idea how much time that likely saved me. I’ve spend about 5 hours trying to get as much as I have working now… only to see that error. It’s my docker first, so I was almost about to ditch docker.

3reactions
pvijehcommented, Dec 27, 2016

@iDVB you can solve this temporarily by commenting out lines 51 through 57 in tools/runServer.js

// if (pending) {
//   server.once('exit', (code, signal) => {
//     if (pending) {
//       throw new Error(`Server terminated unexpectedly with code: ${code} signal: ${signal}`);
//     }
//   });
// }

Im not sure what the root cause of the error is, but commetting these lines out does not seem to have any ill effect and will solve the problem and let you start working again.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Error: Server terminated unexpectedly with code: null signal
You can solve this temporarily by commenting out lines 51 to 57 in tools/sunServer.js. like this: // if (pending) { // server.once('exit', ...
Read more >
Error: Server terminated unexpectedly with code: null signal
Coding example for the question Error: Server terminated unexpectedly with code: null signal: SIGTERM-Reactjs.
Read more >
Process | Node.js v19.3.0 Documentation
import process from 'node:process'; process.on('beforeExit', (code) ... and afterwards, subprocess will report that the process was terminated by signal.
Read more >
SIGKILL: Fast Termination of Linux Containers | Signal 9
Learn how to use SIGKILL and SIGTERM to terminate Unix/Linux processes and K8s ... as Unix signal 9)—kills the process abruptly, producing a...
Read more >
The Death of a Node.js Process - Thomas Hunter II
Some of them are preventable, like when an error is thrown, ... The process.exit(code) approach to process termination is the most ...
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