[APIGEE] API requests made to apigee server throws exception "scripts.node.runtime.ScriptStillStart

[psvnlsaikumar]

1. The error rate was very high last month. Until there is a restart to the servers, the issue remains.
2. No change was made to the server except for restart, and we have stopped restarting recently, and we are not encountering issue. 
3. This is an intermittent issue which keeps showing up.
4. The nodejs engine that is running is trireme

Any help which would point to this issue would be appreciated. We have added a lot of loggers, and are not able to find the root cause.

error trace :- 

pathtoRegexp (/organization/environment/api/node_modules/path-to-regexp/index.js:101:0),     at Layer (/organization/environment/api/node_modules/express/lib/router/layer.js:45:0),     at use (/organization/environment/api/node_modules/ 
express/lib/router/index.js:464:0),     at /organization/environment/api/node_modules/express/lib/application.js:220:0,     at use (/organization/environment/api/node_modules/express/lib/application.js:217:0),     at /organization/environment/api/app.js:100:0,     at module.js:456:0,     at module.js:474:0,     at module.js:356:0,     at module.js:312:0,     at module.js:497:0,     at startup (trireme.js:142:0),     at trireme.js:923:0, ]

////// 

API response  :- 

<faultstring>Script node is still starting</faultstring><detail><errorcode>scripts.node.runtime.ScriptStillStarting</errorcode></detail></fault>

[dchiesa1]

I suggest you connect with Apigee support to diagnose this.

Whoops! I just realized.... as of July 2021, trireme is no longer supported. So contacting Apigee support will not help you.

If I were dealing with this, the first thing I would do is try to migrate that app from trireme to a native nodejs hosting environment. That will get you to a supported configuration. Also it will be easier to diagnose problems.

If I were a person that DID NOT follow good guidance, then I guess I would have to try to diagnose this myself. If I were that person, I would try these things:

• see if I can duplicate the problem I'm observing if I run the app within trireme, but outside of Apigee. (It is possible to clone the trireme github repo, and then run nodejs apps in trireme outside of Apigee, from a workstation.)
• Determine if it is one particular nodejs app, or if the problem you are experiencing is happening in all nodejs apps. If it is one app, or a few of them, examine them closely to see what they do for initialization and startup. Are they as efficient and effective as they could be?

good luck!