vxsync setup error Section 3. Step viii

[bciv]

Under Windows 10 as the guest OS ~Upon running step viii. Run 'sudo npm install' an error related to SYMLINKS that occurs in a vagrant environment is thrown:

npm ERR! UNKNOWN, symlink '../esprima/bin/esvalidate.js'

The fix for this is to execute 'sudo npm install --no-bin-link

OUTPUT FOLLOWS:

vagrant@vagrant-ubuntu-precise-64:/vagrant/ehmp/product/production/vx-sync$ sudo npm install

• core-util-is@1.0.2 node_modules/mongodb/node_modules/readable-stream/node_modules/core-util-is
• process-nextick-args@1.0.6 node_modules/mongodb/node_modules/readable-stream/node_modules/process-nextick-args
• string_decoder@0.10.31 node_modules/mongodb/node_modules/readable-stream/node_modules/string_decoder
• util-deprecate@1.0.2 node_modules/mongodb/node_modules/readable-stream/node_modules/util-deprecate
  vx-sync@0.0.1 /vagrant/ehmp/product/production/vx-sync
  └─┬ mongodb@1.4.40
  └── readable-stream@2.0.5

npm ERR! Linux 3.2.0-97-virtual
npm ERR! argv "node" "/usr/bin/npm" "install"
npm ERR! node v0.10.41
npm ERR! npm v3.5.3
npm ERR! path ../esprima/bin/esvalidate.js
npm ERR! code UNKNOWN
npm ERR! errno -1

npm ERR! UNKNOWN, symlink '../esprima/bin/esvalidate.js'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues
npm ERR! Linux 3.2.0-97-virtual
npm ERR! argv "node" "/usr/bin/npm" "install"
npm ERR! node v0.10.41
npm ERR! npm v3.5.3
npm ERR! path npm-debug.log.2581865522
npm ERR! code ETXTBSY
npm ERR! errno 62

npm ERR! ETXTBSY, rename 'npm-debug.log.2581865522'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! https://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request:
npm ERR! /vagrant/ehmp/product/production/vx-sync/npm-debug.log

REMEDIATION:
vagrant@vagrant-ubuntu-precise-64:/vagrant/ehmp/product/production/vx-sync$ sudo npm install --no-bin-link
vx-sync@0.0.1 /vagrant/ehmp/product/production/vx-sync
├─┬ mongodb@1.4.40
│ └─┬ readable-stream@2.0.5
│ ├── core-util-is@1.0.2
│ ├── process-nextick-args@1.0.6
│ ├── string_decoder@0.10.31
│ └── util-deprecate@1.0.2
├─┬ multer@0.1.8
│ └─┬ busboy@0.2.12
│ └─┬ readable-stream@1.1.13
│ ├── core-util-is@1.0.2
│ └── string_decoder@0.10.31
├─┬ nyc@5.3.0 (git://github.com/isaacs/nyc.git#b43f1dbef1892af89dfa2f9a9e662381cddb2d1f)
│ └─┬ istanbul@0.4.2
│ ├── async@1.5.2
│ ├── esprima@2.7.1
│ └─┬ handlebars@4.0.5
│ └── async@1.5.2
├─┬ request@2.48.0
│ └─┬ bl@0.9.5
│ └─┬ readable-stream@1.0.33
│ ├── core-util-is@1.0.2
│ └── string_decoder@0.10.31
├─┬ statman@0.1.3
│ ├─┬ nodeunit@0.8.8
│ │ └─┬ tap@5.1.1
│ │ ├─┬ coveralls@2.11.6
│ │ │ ├─┬ js-yaml@3.0.1
│ │ │ │ ├─┬ argparse@0.1.16
│ │ │ │ │ ├── underscore@1.7.0
│ │ │ │ │ └── underscore.string@2.4.0
│ │ │ │ └── esprima@1.0.4
│ │ │ ├── minimist@1.2.0
│ │ │ └─┬ request@2.67.0
│ │ │ ├── aws-sign2@0.6.0
│ │ │ ├─┬ bl@1.0.1
│ │ │ │ └── readable-stream@2.0.5
│ │ │ ├── caseless@0.11.0
│ │ │ ├─┬ combined-stream@1.0.5
│ │ │ │ └── delayed-stream@1.0.0
│ │ │ ├── forever-agent@0.6.1
│ │ │ ├─┬ form-data@1.0.0-rc3
│ │ │ │ └── async@1.5.2
│ │ │ ├─┬ hawk@3.1.3
│ │ │ │ ├── boom@2.10.1
│ │ │ │ ├── cryptiles@2.0.5
│ │ │ │ ├── hoek@2.16.3
│ │ │ │ └── sntp@1.0.9
│ │ │ ├── http-signature@1.1.0
│ │ │ ├── mime-types@2.1.9
│ │ │ ├── oauth-sign@0.8.0
│ │ │ └── qs@5.2.0
│ │ ├─┬ js-yaml@3.5.2
│ │ │ └── esprima@2.7.1
│ │ └── readable-stream@2.0.5
│ └── underscore@1.6.0
└─┬ tap-mocha-reporter@0.0.22
├─┬ js-yaml@3.5.2
│ └── esprima@2.7.1
├─┬ readable-stream@1.1.13
│ ├── core-util-is@1.0.2
│ └── string_decoder@0.10.31
└─┬ tap-parser@1.2.2
└─┬ readable-stream@2.0.5
├── process-nextick-args@1.0.6
└── util-deprecate@1.0.2

vagrant@vagrant-ubuntu-precise-64:/vagrant/ehmp/product/production/vx-sync$

[bciv]

Using Windows 10 as the guest OS ~After getting vx-sync to run, the verification step does not give the correct response:

vagrant@vagrant-ubuntu-precise-64:/vagrant/ehmp/product/production/vx-sync$ curl -X GET http://192.168.33.10:9080/statusod/34C5
{"apiVersion":"1.0","error":{"code":404,"errors":[{"message":"No data on file","reason":229}],"message":"Bad Request","r
equest":"GET /statusod/34C5 "}}vagrant@vagrant-ubuntu-precise-64:/vagrant/ehmp/product/production/vx-sync$

[khollida]

We are actively looking into these issues. Also in response to the vx-sync responses, try moving into the Vx-Sync directory and running the following command: node tools/rpc/rpc-unsubscribe-all --host 192.168.33.10 --port 9430

[khollida]

Following that try rerunning the operational data sync with "curl -I http://192.168.33.12:8088/data/doLoad?sites=34C5" and "curl -X GET http://192.168.33.10:9080/statusod/34C5"