npm ERR during pm2 install

[ninjada]

hello,

im updating some production node servers, moving to using a salt state to install nodejs and then npm install pm2 globally.

the state runs fine, but has some errors during the pm2 install. the salt state seems irrelevant, the same errors occur running the commands normally.

salt command.run that returns errors is:

npm install -g pm2 --unsafe-perm:
  cmd.run

error message:

 ID: npm install -g pm2 --unsafe-perm

    Function: cmd.run

      Result: True

     Comment: Command "npm install -g pm2 --unsafe-perm" run

     Started: 07:31:57.722280

    Duration: 16897.577 ms

     Changes:   

              ----------

              pid:

                  3058

              retcode:

                  0

              stderr:

                  npm ERR! git clone http://ikt.pm2.io/ikt.git undefined

                  npm ERR! git clone http://ikt.pm2.io/ikt.git undefined

                  npm WARN optional dep failed, continuing ikt@git+http://ikt.pm2.io/ikt.git#master

                  npm WARN optional dep failed, continuing fsevents@0.3.6

              stdout:

                  /usr/bin/pm2 -> /usr/lib/node_modules/pm2/bin/pm2

                  /usr/bin/pm2-dev -> /usr/lib/node_modules/pm2/bin/pm2-dev

                  pm2@0.14.2 /usr/lib/node_modules/pm2

                  ├── is-iojs@1.1.0

                  ├── isbinaryfile@2.0.4

                  ├── eventemitter2@0.4.14

                  ├── pidusage@0.1.1

                  ├── safe-clone-deep@1.0.5

                  ├── colors@1.1.0

                  ├── commander@2.8.1 (graceful-readlink@1.0.1)

                  ├── debug@2.2.0 (ms@0.7.1)

                  ├── semver@4.3.6

                  ├── shelljs@0.5.1

                  ├── cli-table@0.3.1 (colors@1.0.3)

                  ├── vizion@0.2.11 (async@0.9.0)

                  ├── pmx@0.3.19 (json-stringify-safe@5.0.1)

                  ├── pm2-multimeter@0.1.2 (charm@0.1.2)

                  ├── chalk@1.0.0 (escape-string-regexp@1.0.3, ansi-styles@2.0.1, supports-color@1.3.1, strip-ansi@2.0.1, has-ansi@1.0.3)

                  ├── coffee-script@1.9.3

                  ├── pm2-deploy@0.1.2 (tv4@1.0.18, async@0.9.2)

                  ├── pm2-axon-rpc@0.3.6 (json-stringify-safe@5.0.1, commander@1.0.5)

                  ├── nssocket@0.5.3 (lazy@1.0.11)

                  ├── async@1.2.1

                  ├── pm2-axon@2.0.8 (amp-message@0.1.2, escape-regexp@0.0.1, amp@0.3.1, configurable@0.0.1, debug@2.0.0)

                  ├── chokidar@1.0.3 (arrify@1.0.0, path-is-absolute@1.0.0, is-glob@1.1.3, glob-parent@1.2.0, async-each@0.1.6, is-binary-path@1.0.1, readdirp@1.3.0, anymatch@1.3.0)

                  ├── pm2-logs@0.1.1 (json-stringify-safe@5.0.1, chalk@0.4.0, pm2-interface@1.1.0, blessed@0.0.36)

                  ├── cron@1.0.9 (moment-timezone@0.3.1)

                  ├── moment@2.10.3

                  └── babel@5.6.14 (slash@1.0.0, path-is-absolute@1.0.0, path-exists@1.0.0, fs-readdir-recursive@0.1.2, convert-source-map@1.1.1, output-file-sync@1.1.1, glob@5.0.12, source-map@0.4.2, lodash@3.9.3, babel-core@5.6.15)

Whats the reason for the git clone warnings? anything to worry about?

[npm-robot]

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining package.community and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.