openvpn-status: BUILD FAILURE ON CENTOS7

below is my cfg.json { “port”: 3013, “bind”: “10.0.0.180”, “servers”: [{“id”: 0,“name”: “Server”}], “ipFile”: “./GeoLite2-City.mmdb” }

when i executed npm run build it got failed with below error logs: `> openvpn-status@4.0.17 build /home/centos/openvpn-status/openvpn-status

node build/build.js

module.js:471 throw err; ^

Error: Cannot find module ‘chalk’ at Function.Module._resolveFilename (module.js:469:15) at Function.Module._load (module.js:417:25) at Module.require (module.js:497:17) at require (internal/module.js:20:19) at Object.<anonymous> (/home/centos/openvpn-status/openvpn-status/build/check-versions.js:2:15) at Module._compile (module.js:570:32) at Object.Module._extensions…js (module.js:579:10) at Module.load (module.js:487:32) at tryModuleLoad (module.js:446:12) at Function.Module._load (module.js:438:3)

npm ERR! Linux 3.10.0-327.10.1.el7.x86_64 npm ERR! argv “/usr/bin/node” “/bin/npm” “run” “build” npm ERR! node v6.12.3 npm ERR! npm v3.10.10 npm ERR! code ELIFECYCLE npm ERR! openvpn-status@4.0.17 build: node build/build.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the openvpn-status@4.0.17 build script ‘node build/build.js’. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the openvpn-status package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node build/build.js npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs openvpn-status npm ERR! Or if that isn’t available, you can get their info via: npm ERR! npm owner ls openvpn-status npm ERR! There is likely additional logging output above. npm WARN Local package.json exists, but node_modules missing, did you mean to install?

npm ERR! Please include the following file with any support request: npm ERR! /home/centos/openvpn-status/openvpn-status/npm-debug.log`

i am attaching the /home/centos/openvpn-status/openvpn-status/npm-debug.log logs.txt

kindly let us know to fix this.

About this issue

  • Original URL
  • State: closed
  • Created 6 years ago
  • Comments: 31 (16 by maintainers)

Most upvoted comments

thanks for support mate. i was able to fix this. to debug the issue i explicitely added the echo statement in status.sh where i found that variable common_name was blank due this JSON schema was not valid. post that i checked the env variables which were creating while client get connect. so the required variable is username. i changed the variable to $username from $common_name. then it worked as expected.

Now i have suggestion regarding modifying the UI and adding the aditional functions in it. would you be interested on this.