Cannot find module 'jws' - single-sign-on

When pushing my app to Bluemix with no local node_modules and adding the passport-idaas-openidconnect dependency I get the following errors, it says the issue is with my app and not npm, but the error is from /home/vcap/app/node_modules/passport-idaas-openidconnect/lib/strategy.js:8:11
ERR module.js:338
ERR;
ERR ^
ERRor: Cannot find module 'jws'
ERR at Function.Module._resolveFilename (module.js:336:15)
ERR at Function.Module._load (module.js:278:25)
ERR at Module.require (module.js:365:17)
ERR at require (module.js:384:17)
ERR at Object.<anonymous> (/home/vcap/app/node_modules/passport-idaas-openidconnect/lib/strategy.js:8:11)
ERR at Module._compile (module.js:460:26)
ERR at Object.Module._extensions..js (module.js:478:10)
ERR at Module.load (module.js:355:32)
ERR at Function.Module._load (module.js:310:12)
ERR at Module.require (module.js:365:17)
ERR at require (module.js:384:17)
ERR! Linux 3.19.0-25-generic
ERR! argv "/home/vcap/app/vendor/node/bin/node" "/home/vcap/app/vendor/node/bin/npm" "start"
ERR! node v0.12.10
ERR! npm v2.14.9
ERR! code ELIFECYCLE
ERR! myapp#0.4.2 start: `node app.js`
ERR! Exit status 1
ERR!
ERR! Failed at the myapp#0.4.2 start script 'node app.js'.
ERR! This is most likely a problem with the myapp package,
ERR! not with npm itself.
ERR! Tell the author that this fails on your system:
ERR! node app.js
ERR! You can get their info via:
ERR! npm owner ls myappe
ERR! There is likely additional logging output above.
ERR! Please include the following file with any support request:
ERR! /home/vcap/app/npm-debug.log
ERR Instance (index 0) failed to start accepting connections


In order to push a Node.js application with SSO capabilities using Bluemix SSO service, you'll need at least the following dependencies in your package.json file:
"dependencies": {
[...]
"cookie-parser": "^1.4.1",
"express": "^4.12.4",
"express-session": "^1.13.0",
"passport": "^0.2.2",
"passport-idaas-openidconnect": "^1.0.0"
[...]
}
Please note that the passport-idaas-openidconnect module works with passport versions 0.1.1 up to 0.3.2. Versions later than 0.3.2 might not work correctly, as reported in Bluemix Single Sign On Docs - Configuring apps.

Related

Error Using ask deploy in Azure DevOps Release

Scenario
I am attempting to run ask deploy to deploy an Alexa Skill from a ubuntu-20.04 release agent in Azure DevOps. I'm using an AWS Shell Script task, which according to the description
Runs a shell script in Bash, setting AWS credentials and region
information into the shell environment using the standard environment
keys AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN and
AWS_REGION.
I have the credentials set in DevOps as a Service Connection, so it really does have secure access to those values. So now that this task exposes my access key, secret, and region, I simply added a script to export the final two env vars needed for (I thought) successful execution:
export ASK_REFRESH_TOKEN="$(ASK_REFRESH_TOKEN)"
export ASK_VENDOR_ID="$(ASK_VENDOR_ID)"
Just to make sure that it's working I added ask smapi get-vendor-list to the script and I get the expected output which shows my vendor ID, name, and roles. Cool -- it must be working.
Problem
Now when ask deploy I get the following error:
CliError: Skill package src is not found in ask-resources.json
and I don't seem to be able to circumvent it.
I've Already Tried...
Downloading the build artifact and running ask deploy locally. That works, so I know there's not an issue with the composition of the build or the skill package.
Updating the refresh token
Verifying that the command is invoked from the correct directory
Verifying that the directory contains the right files
Question
How can I solve that error and successfully ask deploy from a release agent?
Reference
I'm on ASK-CLI v2.16.0
Here's my ask-resources.json in case that's useful. The error mentions this file.
{
"askcliResourcesVersion": "2020-03-31",
"profiles": {
"default": {
"skillMetadata": {
"src": "./skill-package"
},
"code": {
"default": {
"src": "./lambda"
}
},
"skillInfrastructure": {
"userConfig": {
"runtime": "nodejs12.x",
"handler": "index.handler",
"templatePath": "./infrastructure/cfn-deployer/skill-stack.yaml",
"awsRegion": "us-east-1"
},
"type": "#ask-cli/cfn-deployer"
}
}
}
}
Release job definition:
Release Log:
####Task Permissions
Permissions for this task to call AWS service APIs depend on the activities in the supplied script.
2020-09-29T12:27:05.4760730Z ==============================================================================
2020-09-29T12:27:05.6858528Z Configuring credentials for task
2020-09-29T12:27:05.6863319Z ...configuring AWS credentials from service endpoint 'redacted'
2020-09-29T12:27:05.6863708Z ...endpoint defines standard access/secret key credentials
2020-09-29T12:27:05.6879415Z Configuring region for task
2020-09-29T12:27:05.6882489Z ...configured to use region us-east-1, defined in task.
2020-09-29T12:27:05.6917304Z [command]/usr/bin/bash /home/vsts/work/_temp/awsshellscript_2266.sh
2020-09-29T12:27:09.2056323Z npm WARN deprecated request#2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
2020-09-29T12:27:15.3303791Z npm WARN deprecated har-validator#5.1.5: this library is no longer supported
2020-09-29T12:27:20.4277268Z /usr/local/bin/ask -> /usr/local/lib/node_modules/ask-cli/bin/ask.js
2020-09-29T12:27:20.4466577Z
2020-09-29T12:27:20.4475010Z > dtrace-provider#0.8.8 install /usr/local/lib/node_modules/ask-cli/node_modules/dtrace-provider
2020-09-29T12:27:20.4476929Z > node-gyp rebuild || node suppress-error.js
2020-09-29T12:27:20.4477558Z
2020-09-29T12:27:20.8448748Z gyp WARN EACCES current user ("nobody") does not have permission to access the dev dir "/root/.cache/node-gyp/12.18.4"
2020-09-29T12:27:20.8507717Z gyp WARN EACCES attempting to reinstall using temporary dev dir "/usr/local/lib/node_modules/ask-cli/node_modules/dtrace-provider/.node-gyp"
2020-09-29T12:27:20.8519281Z gyp WARN install got an error, rolling back install
2020-09-29T12:27:20.8535248Z gyp WARN install got an error, rolling back install
2020-09-29T12:27:20.8551818Z gyp ERR! configure error
2020-09-29T12:27:20.8555760Z gyp ERR! stack Error: EACCES: permission denied, mkdir '/usr/local/lib/node_modules/ask-cli/node_modules/dtrace-provider/.node-gyp'
2020-09-29T12:27:20.8559344Z gyp ERR! System Linux 5.4.0-1025-azure
2020-09-29T12:27:20.8560532Z gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
2020-09-29T12:27:20.8571334Z gyp ERR! cwd /usr/local/lib/node_modules/ask-cli/node_modules/dtrace-provider
2020-09-29T12:27:20.8572691Z gyp ERR! node -v v12.18.4
2020-09-29T12:27:20.8573700Z gyp ERR! node-gyp -v v5.1.0
2020-09-29T12:27:20.8574490Z gyp ERR! not ok
2020-09-29T12:27:20.9460739Z
2020-09-29T12:27:20.9462350Z > ask-cli#2.16.1 postinstall /usr/local/lib/node_modules/ask-cli
2020-09-29T12:27:20.9463103Z > node postinstall.js
2020-09-29T12:27:20.9463477Z
2020-09-29T12:27:20.9839474Z
2020-09-29T12:27:20.9840246Z ================================================================================
2020-09-29T12:27:20.9844532Z ASK CLI collects telemetry to better understand customer needs. You can
2020-09-29T12:27:20.9845738Z OPT OUT and disable telemetry by setting the 'share_usage' key to 'false'
2020-09-29T12:27:20.9846574Z in '~/.ask/cli_config'.
2020-09-29T12:27:20.9846928Z
2020-09-29T12:27:20.9847554Z Learn more: https://developer.amazon.com/docs/alexa/smapi/ask-cli-telemetry.html
2020-09-29T12:27:20.9848513Z ================================================================================
2020-09-29T12:27:20.9848861Z
2020-09-29T12:27:20.9933073Z + ask-cli#2.16.1
2020-09-29T12:27:20.9933710Z added 233 packages from 243 contributors in 13.497s
2020-09-29T12:27:21.2144126Z /home/vsts/work/r1/a/BuildArtifact/drop/projectname
2020-09-29T12:27:21.2154300Z total 44
2020-09-29T12:27:21.2155074Z drwxr-xr-x 6 vsts docker 4096 Sep 29 12:27 .
2020-09-29T12:27:21.2155522Z drwxr-xr-x 3 vsts docker 4096 Sep 29 12:27 ..
2020-09-29T12:27:21.2156597Z drwxr-xr-x 2 vsts docker 4096 Sep 29 12:27 .ask
2020-09-29T12:27:21.2157145Z -rw-r--r-- 1 vsts docker 46 Sep 29 12:27 .gitignore
2020-09-29T12:27:21.2157583Z -rw-r--r-- 1 vsts docker 11358 Sep 29 12:27 LICENSE.txt
2020-09-29T12:27:21.2158041Z -rw-r--r-- 1 vsts docker 537 Sep 29 12:27 ask-resources.json
2020-09-29T12:27:21.2158482Z drwxr-xr-x 3 vsts docker 4096 Sep 29 12:27 infrastructure
2020-09-29T12:27:21.2158917Z drwxr-xr-x 3 vsts docker 4096 Sep 29 12:27 lambda
2020-09-29T12:27:21.2159407Z drwxr-xr-x 4 vsts docker 4096 Sep 29 12:27 skill-package
2020-09-29T12:27:22.9397766Z {
2020-09-29T12:27:22.9398441Z "vendors": [
2020-09-29T12:27:22.9398789Z {
2020-09-29T12:27:22.9399540Z "id": "***",
2020-09-29T12:27:22.9399972Z "name": "redacted",
2020-09-29T12:27:22.9400496Z "roles": [
2020-09-29T12:27:22.9400870Z "ROLE_DEVELOPER"
2020-09-29T12:27:22.9401186Z ]
2020-09-29T12:27:22.9401481Z }
2020-09-29T12:27:22.9402201Z ]
2020-09-29T12:27:22.9402497Z }
2020-09-29T12:27:23.9621180Z [Error]: CliError: Skill package src is not found in ask-resources.json.

Not able to connect to MongoDB using NPM. URI issue?

So, I am not able to connect to MongoDB (Atlas). Feels like I may be going crazy here as logs are about as helpful as an anchor on a sinking boat. Here's what's going on. Thanks for the help.
Here's my server.js file:
'use strict';
const mongodb = require('mongodb');
const http = require('http');
const nconf = require('nconf');
let uri = 'mongodb://USERNAME:PASSWORD#cluster0-w4hci.mongodb.net/test?retryWrites=true&w=majority;';
Here's what console is saying
npm start
> test#1.0.0 start /home/XXXXXXX
> node server.js
mongodb://USERNAME:PASSWORD#cluster0-w4hci.mongodb.net/test?retryWrites=true&w=majority;
/home/XXXXXXX/node_modules/mongodb/lib/mongo_client.js:421
throw err
^
MongoError: failed to connect to server [cluster0-w4hci.mongodb.net:27017] on first connect [MongoError: getaddrinfo ENOTFOUND cluster0-w4hci.mongodb.net cluster0-w4hci.mongodb.net:27017]
at Pool.<anonymous> (/home/XXXXXXX/node_modules/mongodb-core/lib/topologies/server.js:336:35)
at emitOne (events.js:116:13)
at Pool.emit (events.js:211:7)
at Connection.<anonymous> (/home/XXXXXXX/node_modules/mongodb-core/lib/connection/pool.js:280:12)
at Object.onceWrapper (events.js:317:30)
at emitTwo (events.js:126:13)
at Connection.emit (events.js:214:7)
at Socket.<anonymous> (/home/XXXXXXX/node_modules/mongodb-core/lib/connection/connection.js:187:49)
at Object.onceWrapper (events.js:315:30)
at emitOne (events.js:116:13)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! test#1.0.0 start: `node server.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the test#1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/XXXXXXX/.npm/_logs/2020-02-23T15_17_31_259Z-debug.log

Turns out my node.js driver was a different version than what I thought. Once I selected the correct version from Atlas, the URI worked and I am not connected!

Why is my node-red app returning 404 route error in ibm-cloud?

My node-red app in bluemix was working, but now it doesn't let me access the route. It worked before and I have not modified it.
I am getting this error:
404 Not Found: Requested route ('route.mybluemix.net') does not exist.
The recent logs are:
2018-04-16T09:37:46.60-0300 [CELL/0] OUT Creating container
2018-04-16T09:37:47.42-0300 [CELL/0] OUT Successfully created container
2018-04-16T09:37:54.32-0300 [CELL/0] OUT Starting health monitoring of container
2018-04-16T09:37:55.41-0300 [APP/PROC/WEB/0] OUT > node-red-bluemix#0.8.0 start /home/vcap/app
2018-04-16T09:37:55.41-0300 [APP/PROC/WEB/0] OUT > node --max-old-space-size=180 index.js --settings ./bluemix-settings.js -v
2018-04-16T09:37:55.62-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:37:55 - Starting Node-RED on IBM Cloud bootstrap
2018-04-16T09:37:55.62-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:37:55 - Loading bluemix-settings.js
2018-04-16T09:37:55.72-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:37:55 - Using Cloudant service: /^NodeRed.cloudantNoSQLDB/ : NodeRed
2018-04-16T09:37:56.08-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:37:56 - Loading application settings
2018-04-16T09:37:56.22-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:37:56 - Using runtime settings for adminAuth
2018-04-16T09:37:56.77-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:37:56 - [info]
2018-04-16T09:37:56.77-0300 [APP/PROC/WEB/0] OUT Welcome to Node-RED
2018-04-16T09:37:56.77-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:37:56 - [info] Linux 4.4.0-109-generic x64 LE
2018-04-16T09:37:56.77-0300 [APP/PROC/WEB/0] OUT ===================
2018-04-16T09:37:56.77-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:37:56 - [info] Node-RED version: v0.18.2
2018-04-16T09:37:56.77-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:37:56 - [info] Node.js version: v6.12.3
2018-04-16T09:37:57.25-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:37:57 - [info] Loading palette nodes
2018-04-16T09:37:59.99-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:37:59 - [warn] Missing node modules:
2018-04-16T09:37:59.99-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:37:59 - [warn] - node-red-contrib-telegrambot (2.7.3): telegram bot, telegram receiver, telegram command, telegram callback_query, telegram sender, telegram reply
2018-04-16T09:37:59.99-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:37:59 - [warn] - node-red-contrib-play-audio (2.2.4): play audio
2018-04-16T09:37:59.99-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:37:59 - [warn] - node-red-contrib-browser-utils (0.0.5): fileinject, microphone, camera
2018-04-16T09:38:00.00-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:38:00 - [info] Installing module: node-red-contrib-play-audio, version: 2.2.4
2018-04-16T09:37:59.99-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:37:59 - [info] Installing module: node-red-contrib-telegrambot, version: 2.7.3
2018-04-16T09:38:00.21-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:38:00 - [info] Installing module: node-red-contrib-browser-utils, version: 0.0.5
2018-04-16T09:38:00.30-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:38:00 - [info] Settings file : /home/vcap/app/bluemix-settings.js
2018-04-16T09:38:00.30-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:38:00 - [info] HTTP Static : /home/vcap/app/public
2018-04-16T09:38:00.44-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:38:00 - [info] Server now running at http://127.0.0.1:8080/red/
2018-04-16T09:38:00.60-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:38:00 - [info] Waiting for missing types to be registered:
2018-04-16T09:38:00.60-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:38:00 - [info] - telegram bot
2018-04-16T09:38:00.60-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:38:00 - [info] - telegram receiver
2018-04-16T09:38:00.60-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:38:00 - [info] - telegram sender
2018-04-16T09:38:00.60-0300 [APP/PROC/WEB/0] OUT 16 Apr 12:38:00 - [info] - microphone
2018-04-16T09:38:00.92-0300 [CELL/0] OUT Container became healthy
2018-04-16T09:38:03.47-0300 [APP/PROC/WEB/0] ERR Killed
2018-04-16T09:38:03.49-0300 [APP/PROC/WEB/0] ERR npm ERR! Linux 4.4.0-109-generic
2018-04-16T09:38:03.49-0300 [APP/PROC/WEB/0] ERR npm ERR! argv "/home/vcap/app/vendor/node/bin/node" "/home/vcap/app/vendor/node/bin/npm" "start"
2018-04-16T09:38:03.49-0300 [APP/PROC/WEB/0] ERR npm ERR! node v6.12.3
2018-04-16T09:38:03.49-0300 [APP/PROC/WEB/0] ERR npm ERR! npm v3.10.10
2018-04-16T09:38:03.49-0300 [APP/PROC/WEB/0] ERR npm ERR! code ELIFECYCLE
2018-04-16T09:38:03.49-0300 [APP/PROC/WEB/0] ERR npm ERR! node-red-bluemix#0.8.0 start: `node --max-old-space-size=180 index.js --settings ./bluemix-settings.js -v`
2018-04-16T09:38:03.49-0300 [APP/PROC/WEB/0] ERR npm ERR! Exit status 137
2018-04-16T09:38:03.49-0300 [APP/PROC/WEB/0] ERR npm ERR!
2018-04-16T09:38:03.49-0300 [APP/PROC/WEB/0] ERR npm ERR! Failed at the node-red-bluemix#0.8.0 start script 'node --max-old-space-size=180 index.js --settings ./bluemix-settings.js -v'.
2018-04-16T09:38:03.49-0300 [APP/PROC/WEB/0] ERR npm ERR! Make sure you have the latest version of node.js and npm installed.
2018-04-16T09:38:03.49-0300 [APP/PROC/WEB/0] ERR npm ERR! If you do, this is most likely a problem with the node-red-bluemix package,
2018-04-16T09:38:03.49-0300 [APP/PROC/WEB/0] ERR npm ERR! not with npm itself.
2018-04-16T09:38:03.49-0300 [APP/PROC/WEB/0] ERR npm ERR! Tell the author that this fails on your system:
2018-04-16T09:38:03.50-0300 [APP/PROC/WEB/0] ERR npm ERR! node --max-old-space-size=180 index.js --settings ./bluemix-settings.js -v
2018-04-16T09:38:03.50-0300 [APP/PROC/WEB/0] ERR npm ERR! You can get information on how to open an issue for this project with:
2018-04-16T09:38:03.50-0300 [APP/PROC/WEB/0] ERR npm ERR! npm bugs node-red-bluemix
2018-04-16T09:38:03.50-0300 [APP/PROC/WEB/0] ERR npm ERR! Or if that isn't available, you can get their info via:
2018-04-16T09:38:03.50-0300 [APP/PROC/WEB/0] ERR npm ERR! npm owner ls node-red-bluemix
2018-04-16T09:38:03.50-0300 [APP/PROC/WEB/0] ERR npm ERR! There is likely additional logging output above.
2018-04-16T09:38:03.53-0300 [APP/PROC/WEB/0] ERR npm ERR! Please include the following file with any support request:
2018-04-16T09:38:03.53-0300 [APP/PROC/WEB/0] ERR npm ERR! /home/vcap/app/npm-debug.log
2018-04-16T09:38:03.61-0300 [APP/PROC/WEB/0] OUT Exit status 1 (out of memory)
Before I didn't have all this errors, I have not modified my nodes.

When Node-RED restarts in the IBM Cloud it has to check if it still has all the extra nodes added via the palette manager. That is because those nodes don't get added to the stored application image so are lost on a restage.
If it finds anything is missing, Node-RED will then dynamically reinstall them. You can see in the log it kicking off three reinstalls. This is where the problem is.
By installing these nodes in parallel, the application is most likely running out of memory and getting killed. For a lite account, you only have 256Mb to play with - which is not much.
You have two possible workarounds:
enable the continuous delivery feature (last I looked, bottom right on the applications IBM Cloud dashboard page). That will give you a git repository you can edit the source in. Edit the package.json file to include these additional node modules under the dependencies section. That will ensure the nodes are installed as part of the application image and won't need reinstalling on restart.
upgrade to a standard account where you'll be able to up your application to 512Mb of memory for free.
Since the Lite account was introduced with its 256Mb memory limit, we see this scenario more often. We will have to look at the reinstall code to see about making the installs happen sequentially rather than in parallel. It'll take longer, but should minimise the memory usage.

IBM Cloud Node-Red error (APP/PROC/WEB: Exited with status 1)

Good day to all. I have an app in the IBM Cloud running with using the Internet of Things Platform Starter. Since I installed a resource, i.e. API Connect, and made the connection to my app, my app is then not running anymore.
Even I deleted the API Connect and disconnected with my app, my app still cannot work anymore. But the design and information in this app are important for me.
The following is the log for running my app.
2018-02-22T16:24:18.91+0800 [CELL/0] OUT Creating container2018-02-22T16:24:21.13+0800 [CELL/0] OUT Successfully created container
2018-02-22T16:24:46.68+0800 [CELL/0] OUT Starting health monitoring of container
2018-02-22T16:24:47.93+0800 [APP/PROC/WEB/0] ERR /home/vcap/app/node_modules/node-red/node_modules/fs-extra/lib/index.js:3
2018-02-22T16:24:47.93+0800 [APP/PROC/WEB/0] ERR const assign = require('./util/assign')
2018-02-22T16:24:47.93+0800 [APP/PROC/WEB/0] ERR ^^^^^
2018-02-22T16:24:47.93+0800 [APP/PROC/WEB/0] ERR SyntaxError: Use of const in strict mode.
2018-02-22T16:24:47.93+0800 [APP/PROC/WEB/0] ERR at exports.runInThisContext (vm.js:73:16)
2018-02-22T16:24:47.93+0800 [APP/PROC/WEB/0] ERR at Module._compile (module.js:443:25)
2018-02-22T16:24:47.93+0800 [APP/PROC/WEB/0] ERR at Object.Module._extensions..js (module.js:478:10)
2018-02-22T16:24:47.93+0800 [APP/PROC/WEB/0] ERR at Module.load (module.js:355:32)
2018-02-22T16:24:47.93+0800 [APP/PROC/WEB/0] ERR at Function.Module._load (module.js:310:12)
2018-02-22T16:24:47.93+0800 [APP/PROC/WEB/0] ERR at Module.require (module.js:365:17)
2018-02-22T16:24:47.93+0800 [APP/PROC/WEB/0] ERR at require (module.js:384:17)
2018-02-22T16:24:47.93+0800 [APP/PROC/WEB/0] ERR at Object. (/home/vcap/app/node_modules/node-red/red.js:26:10)
2018-02-22T16:24:47.93+0800 [APP/PROC/WEB/0] ERR at Module._compile (module.js:460:26)
2018-02-22T16:24:47.93+0800 [APP/PROC/WEB/0] ERR at Object.Module._extensions..js (module.js:478:10)
2018-02-22T16:24:47.96+0800 [APP/PROC/WEB/0] OUT Exit status 1
2018-02-22T16:24:47.97+0800 [CELL/0] OUT Exit status 0
2018-02-22T16:24:48.02+0800 [CELL/0] OUT Stopping instance f426c44a-11b6-4373-453d-577f
2018-02-22T16:24:48.02+0800 [CELL/0] OUT Destroying container
2018-02-22T16:24:50.77+0800 [CELL/0] OUT Successfully destroyed container
2018-02-22T16:24:54.02+0800 [API/4] OUT Process has crashed with type: "web"
2018-02-22T16:24:54.15+0800 [API/4] OUT App instance exited with guid 54f30301-ef43-4476-9ba6-261ca1c47aae payload: {"instance"=>"f426c44a-11b6-4373-453d-577f", "index"=>0, "reason"=>"CRASHED", "exit_description"=>"APP/PROC/WEB: Exited with status 1", "crash_count"=>67, "crash_timestamp"=>1519287887997896126, "version"=>"8915be08-78b2-4717-808c-aea8b227afe4"}
Please help me and many thanks to you all.

How to know ionic installed or not

i am bit confused Please help me.Based on this logs ionic installed or not?`
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/dep-graph/-/dep-graph-1.1.0.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/init-package-json/-/init-packag
e-json-1.9.1.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/glob/-/glob-4.0.6.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/d8/-/d8-0.4.4.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/cordova-app-hello-world/-/cordo
va-app-hello-world-3.9.0.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/rc/-/rc-0.5.2.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/npmconf/-/npmconf-0.1.16.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/valid-identifier/-/valid-identi
fier-0.0.1.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm WARN engine cordova-js#4.0.0: wanted: {"node":"~0.10.x"} (current: {"node":"
4.1.2","npm":"2.14.4"})
npm WARN engine npm#1.3.4: wanted: {"node":">=0.6","npm":"1"} (current: {"node":
"4.1.2","npm":"2.14.4"})
npm WARN installMany normalize-package-data was bundled with npm#1.3.4, but bund
led package wasn't found in unpacked tree
npm WARN engine xmlbuilder#2.2.1: wanted: {"node":"0.8.x || 0.10.x"} (current: {
"node":"4.1.2","npm":"2.14.4"})
npm ERR! fetch failed https://registry.npmjs.org/domain-browser/-/domain-browser
-1.1.4.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/htmlescape/-/htmlescape-1.1.0.t
gz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/readable-stream/-/readable-stre
am-1.1.13.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/http-browserify/-/http-browseri
fy-1.7.0.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/resolve/-/resolve-1.1.6.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/https-browserify/-/https-browse
rify-0.0.1.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/insert-module-globals/-/insert-
module-globals-6.6.0.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/shell-quote/-/shell-quote-0.0.1
.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/xtend/-/xtend-4.0.0.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/os-browserify/-/os-browserify-0
.1.2.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/through2/-/through2-1.1.1.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/shasum/-/shasum-1.0.1.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/shallow-copy/-/shallow-copy-0.0
.1.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/punycode/-/punycode-1.3.2.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/vm-browserify/-/vm-browserify-0
.0.4.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/subarg/-/subarg-1.0.0.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/url/-/url-0.10.3.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/JSONStream/-/JSONStream-1.0.6.t
gz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/labeled-stream-splicer/-/labele
d-stream-splicer-1.0.2.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/syntax-error/-/syntax-error-1.1
.4.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/parents/-/parents-1.0.1.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/tty-browserify/-/tty-browserify
-0.0.0.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/util/-/util-0.10.3.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/querystring-es3/-/querystring-e
s3-0.2.1.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/path-browserify/-/path-browseri
fy-0.0.0.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/timers-browserify/-/timers-brow
serify-1.4.1.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/read-only-stream/-/read-only-st
ream-1.1.1.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/module-deps/-/module-deps-3.9.1
.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/process/-/process-0.11.2.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/stream-browserify/-/stream-brow
serify-1.0.0.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/through2/-/through2-1.1.1.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/punycode/-/punycode-1.3.2.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/subarg/-/subarg-1.0.0.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/vm-browserify/-/vm-browserify-0
.0.4.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/querystring-es3/-/querystring-e
s3-0.2.1.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/module-deps/-/module-deps-3.9.1
.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/timers-browserify/-/timers-brow
serify-1.4.1.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/process/-/process-0.11.2.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
npm ERR! fetch failed https://registry.npmjs.org/stream-browserify/-/stream-brow
serify-1.0.0.tgz
npm WARN retry will retry, error on last attempt: Error: connect ETIMEDOUT 103.2
45.222.162:443
global#4.3.0 node_modules\global
├── process#0.5.2
└── min-document#2.17.0 (dom-walk#0.1.1)
ionic#1.6.5 node_modules\ionic
├── underscore#1.7.0
├── proxy-middleware#0.7.0
├── connect-livereload#0.5.2
├── progress#1.1.7
├── open#0.0.5
├── colors#0.6.2
├── q#1.0.1
├── async#0.9.2
├── crc#3.2.1
├── ncp#0.4.2
├── semver#4.3.6
├── shelljs#0.2.6
├── cross-spawn#0.2.3 (lru-cache#2.7.0)
├── cli-table#0.3.1 (colors#1.0.3)
├── form-data#0.1.4 (mime#1.2.11, combined-stream#0.0.7)
├── npm#2.1.3
├── event-stream#3.0.20 (pause-stream#0.0.11, stream-combiner#0.0.4, from#0.1.3,
duplexer#0.1.1, split#0.2.10, through#2.3.8, map-stream#0.0.6)
├── xml2js#0.4.4 (sax#0.6.1, xmlbuilder#3.1.0)
├── opbeat-ionic#1.1.3 (console-log-level#1.1.2, json-stringify-safe#5.0.1, stac
kman#0.2.3, after-all#2.0.2)
├── tiny-lr-fork#0.0.5 (debug#0.7.4, qs#0.5.6, faye-websocket#0.4.4, noptify#0.0
.3)
├── finalhandler#0.2.0 (escape-html#1.0.1, debug#2.0.0)
├── connect#3.1.1 (utils-merge#1.0.0, parseurl#1.3.0, finalhandler#0.1.0, debug#
1.0.4)
├── optimist#0.6.0 (wordwrap#0.0.3, minimist#0.0.10)
├── cheerio#0.19.0 (entities#1.1.1, dom-serializer#0.1.0, css-select#1.0.0, loda
sh#3.10.1, htmlparser2#3.8.3)
├── vinyl-fs#0.3.7 (graceful-fs#3.0.8, lodash#2.4.2, strip-bom#1.0.0, through2#0
.6.5, glob-stream#3.1.18, vinyl#0.4.6, glob-watcher#0.0.6, mkdirp#0.5.1)
├── request#2.51.0 (forever-agent#0.5.2, aws-sign2#0.5.0, caseless#0.8.0, tunnel
-agent#0.4.1, oauth-sign#0.5.0, stringstream#0.0.4, json-stringify-safe#5.0.1, m
ime-types#1.0.2, qs#2.3.3, node-uuid#1.4.3, tough-cookie#2.0.0, hawk#1.1.1, comb
ined-stream#0.0.7, bl#0.9.4, form-data#0.2.0, http-signature#0.10.1)
├── serve-static#1.7.1 (escape-html#1.0.1, utils-merge#1.0.0, parseurl#1.3.0, se
nd#0.10.1)
├── unzip#0.1.9 (setimmediate#1.0.2, readable-stream#1.0.33, match-stream#0.0.2,
pullstream#0.4.1, binary#0.3.0, fstream#0.1.31)
├── gulp#3.8.8 (pretty-hrtime#0.2.2, interpret#0.3.10, deprecated#0.0.1, archy#0
.0.2, minimist#1.2.0, semver#3.0.1, chalk#0.5.1, tildify#1.1.1, orchestrator#0.3
.7, gulp-util#3.0.6, liftoff#0.12.1)
├── prompt#0.2.12 (revalidator#0.1.8, pkginfo#0.3.0, read#1.0.7, winston#0.6.2,
utile#0.2.1)
└── ionic-app-lib#0.3.9 (archiver#0.5.2, vinyl-fs#1.0.0, ionic-cordova-lib#5.1.7
)
`
in cmd line i am given npm it showing:npm#2.14.4 C:\Program Files\nodejs\node_modules\npm
and cordova -v :it showing :5.0.0.i am given ionic it showing :**'ionic' is not recognized as an operable program or batch file.**How to Solve these.
Thanks

Type ionic --version to check version of ionic its return like that
1.7.7
its means install ionic in your system.

You can try ionic info as below
C:>ionic info
Your system information:
cordova CLI: 6.5.0
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.1.7
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 8.1
Node Version: v4.6.0
Xcode version: Not installed
Thank you.

Try below command:
ionic info
You will get the following information:
Cordova CLI: 6.5.0
Ionic CLI Version: 2.2.2
Ionic App Lib Version: 2.2.1
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Linux 4.8
Node Version: v7.9.0
Xcode version: Not installed