lisk-sdk: error: Forever detected script was killed by signal: SIGKILL

Received error error: Forever detected script was killed by signal: SIGKILL

While synchronizing with network. Occurs randomly with first release of 0.2 testnet.

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 22 (9 by maintainers)

Commits related to this issue

Merge pull request #75 from LiskHQ/74-Fix_invalid_malformed_data_field Invalid malformed data field value crashes node - Closes #74 — committed to LiskHQ/lisk-sdk by shuse2 6 years ago
Merge pull request #77 from LiskHQ/74-Fix_invalid_malformed_data_field Invalid malformed data field value crashes node - Closes #74 — committed to LiskHQ/lisk-sdk by shuse2 6 years ago
Merge pull request #76 from LiskHQ/74-Fix_invalid_malformed_data_field_1.0.0 Invalid malformed data field value crashes node - Closes #74 — committed to LiskHQ/lisk-sdk by shuse2 6 years ago
Merge pull request #78 from LiskHQ/74-Fix_invalid_malformed_data_field_1.0.0 Invalid malformed data field value crashes node - Closes #74 — committed to LiskHQ/lisk-sdk by shuse2 6 years ago

Most upvoted comments

Just encountered this issue. Dropping the -w flag seems to have fixed it. Hope this gives clues to what could be causing it.

charsi on Apr 11, 2019

Just encountered this issue. Dropping the -w flag seems to have fixed it. Hope this gives clues to what could be causing it.

We were getting this error too and could fix it by dropping -w, but we later realised that we actually did a silly mistake of keeping our Forever logs in the same folder as our project files and obviously Forever started and wrote into log files and that means log file changed and Forever was watching it treating it as a project file so if it changes, it will restart the node. It’s probably a silly mistake but I thought I will mention it here anyways so that others don’t have forever logs or other logs/files which will change when project is running, but it’s not a project file so shouldn’t lead to restarting the node and project itself.

Just came here to say that this was exactly my issue. Consider adding a .foreverignore (identical to .gitignore) to your app directory.

dim-anis on Nov 17, 2022

Just encountered this issue. Dropping the -w flag seems to have fixed it. Hope this gives clues to what could be causing it.

We were getting this error too and could fix it by dropping -w, but we later realised that we actually did a silly mistake of keeping our Forever logs in the same folder as our project files and obviously Forever started and wrote into log files and that means log file changed and Forever was watching it treating it as a project file so if it changes, it will restart the node. It’s probably a silly mistake but I thought I will mention it here anyways so that others don’t have forever logs or other logs/files which will change when project is running, but it’s not a project file so shouldn’t lead to restarting the node and project itself.

palewar on Feb 11, 2020

Hello until now i still meet this error with nodejs: error: Forever detected script was killed by signal: SIGKILL How to fix it?

chhorn on Mar 23, 2018