Bug Report: Silent Fails on Permission Issues

[CobbleVision]

Please also see update and double post below:

Title: "forever start xy.json" silently fails on permission issues

Description: Forever fails without writing any logs or returning any console output when encountering permission issues. This is painful as debugging on servers might be difficult. Permission Errors do not seem to be handled well in logs overall.

File Description / Terminal Output: Forever log remains empty at 0B. Forever start returns something along "Forever processing file 'app.js'".

Fix Suggestion & Possible Source: On first look it seems as if forever is missing some error handlers and functions to cover these scenarios.

Recreate: Try to chmod 700 /usr/bin/env as root and attempt to "forever start" a config file as "ubuntu" user.

[CobbleVision]

Update on 06 - July:

Update Report: I cannot fully account for permission issues. However, sometimes when invoked through bash, the forever script does not launch any node service, does not return any log and does not output any error.

Possible Causes: Maybe there is CPU shortages or similar issues killing forever in the process of starting the service. Due to time constraints I cannot fully replicate the difference between a successful launch and a launch, which does not return any output. I could also assume that conflicts with other services or packages might cause this issue.

[shwq774791378]

``

[shwq774791378]

هلا