mongodb not able to access from localmachine

It seems the mongodb get bound to 127.0.0.1 and it is not accessible remotely.

Errors upon startup

I tried your VagrantFile, hoping to get a quickstart to MEAN development 8^(
I installed VirtualBox on OSX, did not reboot, installed Vagrant, got 'yer git and got vagrant up.

There were some errors in red in my Terminal, many reproduced below after I did a vagrant halt, rebooted OSX and got vagrant up (and again, after trying to vagrant provision):

--------------------------- There are further details, below this chunk of output ------------------
=> vagrant provision
==> mongodb: Running provisioner: shell...
mongodb: Running: /var/folders/lc/7d_txpmd4h1gpctt18d5gn8hdhxnbb/T/vagrant-shell20140422-1782-qzscnl
stdin: is not a tty
git found.
==> mongodb: Running provisioner: puppet...
Running Puppet with mongo.pp...
stdin: is not a tty
notice: An attempt has been made below to automatically apply your custom
settings to mongodb::server. Please verify this works in a safe test
environment.
notice: /Stage[main]/Mongodb/Notify[An attempt has been made below to automatically apply your custom
settings to mongodb::server. Please verify this works in a safe test
environment.]/message: defined 'message' as 'An attempt has been made below to automatically apply your custom
settings to mongodb::server. Please verify this works in a safe test
environment.'
notice: Finished catalog run in 0.08 seconds
==> appserver: Running provisioner: shell...
appserver: Running: /var/folders/lc/7d_txpmd4h1gpctt18d5gn8hdhxnbb/T/vagrant-shell20140422-1782-1oak0xw
stdin: is not a tty
git found.
==> appserver: Running provisioner: puppet...
Running Puppet with appserver.pp...
stdin: is not a tty
notice: Finished catalog run in 1.61 seconds
==> appserver: Running provisioner: shell...
appserver: Running: /var/folders/lc/7d_txpmd4h1gpctt18d5gn8hdhxnbb/T/vagrant-shell20140422-1782-r8mp2t
stdin: is not a tty
/tmp/vagrant-shell: 14: /tmp/vagrant-shell: express: not found
/tmp/vagrant-shell: 15: cd: can't cd to mytestapp
npm ERR! Failed to parse json
npm ERR! Unexpected end of input
npm ERR! File: /usr/local/src/mean/package.json
npm ERR! Failed to parse package.json data.
npm ERR! package.json must be actual JSON, not just JavaScript.
npm ERR!
npm ERR! This is not a bug in npm.
npm ERR! Tell the package author to fix their package.json file. JSON.parse

npm ERR! System Linux 3.2.0-23-generic
npm ERR! command "/usr/local/node/node-v0.10.26/bin/node" "/usr/local/node/node-default/bin/npm" "link"
npm ERR! cwd /usr/local/src/mean
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! file /usr/local/src/mean/package.json
npm ERR! code EJSONPARSE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /usr/local/src/mean/npm-debug.log
npm ERR! not ok code 0
mkdir: cannot create directory `public/javascripts/vendor': File exists

/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/util/rc.js:54
throw error;
^
Error: Unable to parse /usr/local/src/mean/.bowerrc: Unexpected token {
at parse (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/util/rc.js:47:21)
at json (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/util/rc.js:69:12)
at rc (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/util/rc.js:30:9)
at Config.load (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/Config.js:12:20)
at Function.Config.read (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/Config.js:47:19)
at Object. (/usr/local/node/node-v0.10.26/lib/node_modules/bower/lib/config.js:3:38)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)

/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/util/rc.js:54
throw error;
^
Error: Unable to parse /usr/local/src/mean/.bowerrc: Unexpected token {
at parse (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/util/rc.js:47:21)
at json (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/util/rc.js:69:12)
at rc (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/util/rc.js:30:9)
at Config.load (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/Config.js:12:20)
at Function.Config.read (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/Config.js:47:19)
at Object. (/usr/local/node/node-v0.10.26/lib/node_modules/bower/lib/config.js:3:38)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
chown: cannot access `mytestapp': No such file or directory
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

chmod +x /tmp/vagrant-shell && /tmp/vagrant-shell mytestapp

Stdout from the command:

Stderr from the command:

stdin: is not a tty
/tmp/vagrant-shell: 14: /tmp/vagrant-shell: express: not found
/tmp/vagrant-shell: 15: cd: can't cd to mytestapp
npm ERR! Failed to parse json
npm ERR! Unexpected end of input
npm ERR! File: /usr/local/src/mean/package.json
npm ERR! Failed to parse package.json data.
npm ERR! package.json must be actual JSON, not just JavaScript.
npm ERR!
npm ERR! This is not a bug in npm.
npm ERR! Tell the package author to fix their package.json file. JSON.parse

npm ERR! System Linux 3.2.0-23-generic
npm ERR! command "/usr/local/node/node-v0.10.26/bin/node" "/usr/local/node/node-default/bin/npm" "link"
npm ERR! cwd /usr/local/src/mean
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! file /usr/local/src/mean/package.json
npm ERR! code EJSONPARSE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /usr/local/src/mean/npm-debug.log
npm ERR! not ok code 0
mkdir: cannot create directory `public/javascripts/vendor': File exists

/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/util/rc.js:54
throw error;
^
Error: Unable to parse /usr/local/src/mean/.bowerrc: Unexpected token {
at parse (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/util/rc.js:47:21)
at json (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/util/rc.js:69:12)
at rc (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/util/rc.js:30:9)
at Config.load (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/Config.js:12:20)
at Function.Config.read (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/Config.js:47:19)
at Object. (/usr/local/node/node-v0.10.26/lib/node_modules/bower/lib/config.js:3:38)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)

/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/util/rc.js:54
throw error;
^
Error: Unable to parse /usr/local/src/mean/.bowerrc: Unexpected token {
at parse (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/util/rc.js:47:21)
at json (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/util/rc.js:69:12)
at rc (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/util/rc.js:30:9)
at Config.load (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/Config.js:12:20)
at Function.Config.read (/usr/local/node/node-v0.10.26/lib/node_modules/bower/node_modules/bower-config/lib/Config.js:47:19)
at Object. (/usr/local/node/node-v0.10.26/lib/node_modules/bower/lib/config.js:3:38)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
chown: cannot access `mytestapp': No such file or directory
----------------------- end of vagrant provision ---------------------------------------------------------

After vagrant ssh appserver I got:

---------------------------- NPM logfile is not where it is claimed to be (in above snippet) -----

vagrant@precise64:/usr/local/src/mean$ ls -al
total 20
drwxrwxr-x 3 meandev meandev 4096 Apr 22 21:27 .
drwxr-xr-x 3 root root 4096 Apr 22 21:11 ..
-rw-r--r-- 1 root root 92 Apr 22 21:27 .bowerrc
-rw-r--r-- 1 root root 916 Apr 22 21:27 npm-debug.log
-rw-r--r-- 1 root root 0 Apr 22 21:27 package.json
-rw-r--r-- 1 root root 0 Apr 22 21:14 package_json.orig
drwxr-xr-x 3 root root 4096 Apr 22 21:15 public
------------------------------------- end ----------------------------------------------------------------------

The contents of npm-debug.log follow:

vagrant@precise64:/usr/local/src/mean$ cat ./npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/node/node-v0.10.26/bin/node',
1 verbose cli '/usr/local/node/node-default/bin/npm',
1 verbose cli 'link' ]
2 info using [email protected]
3 info using [email protected]
4 verbose linkPkg /usr/local/src/mean
5 error Failed to parse json
5 error Unexpected end of input
6 error File: /usr/local/src/mean/package.json
7 error Failed to parse package.json data.
7 error package.json must be actual JSON, not just JavaScript.
7 error
7 error This is not a bug in npm.
7 error Tell the package author to fix their package.json file. JSON.parse
8 error System Linux 3.2.0-23-generic
9 error command "/usr/local/node/node-v0.10.26/bin/node" "/usr/local/node/node-default/bin/npm" "link"
10 error cwd /usr/local/src/mean
11 error node -v v0.10.26
12 error npm -v 1.4.3
13 error file /usr/local/src/mean/package.json
14 error code EJSONPARSE
15 verbose exit [ 1, true ]

Any plans to update to Express 4.x ?

Are there plans to update/upgrade the appserver to use the latest MEAN stack?

error installing librarian puppet

console output.

Building native extensions. This could take a while...

Stderr from the command:

stdin: is not a tty
dpkg-preconfigure: unable to re-open stdin: No such file or directory
ERROR: Error installing librarian-puppet:
ERROR: Failed to build gem native extension.

    /opt/vagrant_ruby/bin/ruby extconf.rb

creating Makefile

make
sh: 1: make: not found

Gem files will remain installed in /opt/vagrant_ruby/lib/ruby/gems/1.8/gems/json
-1.8.1 for inspection.
Results logged to /opt/vagrant_ruby/lib/ruby/gems/1.8/gems/json-1.8.1/ext/json/e
xt/generator/gem_make.out
/tmp/vagrant-shell: 44: /tmp/vagrant-shell: librarian-puppet: not found

Error Message on Vagrant File

I ran vagrant up and it set up for awhile then i got this error message, I can ssh into the machine using vagrant ssh appserver but when I look for this folder /usr/local/src/mean/mytestapp it doesn't exist, prolly because of it not finishing completely

Error Message:

[appserver] Running provisioner: puppet...
Running Puppet with appserver.pp...
stdin: is not a tty
warning: Could not retrieve fact fqdn
Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type wget::fetch at /etc/puppet/modules/nodejs/manifests/install.pp:89 on node precise64
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

puppet apply --manifestdir /tmp/vagrant-puppet/manifests --detailed-exitcodes /tmp/vagrant-puppet/manifests/appserver.pp || [ $? -eq 2 ]

Stdout from the command:

warning: Could not retrieve fact fqdn

Stderr from the command:

stdin: is not a tty
Puppet::Parser::AST::Resource failed with error ArgumentError: Invalid resource type wget::fetch at /etc/puppet/modules/nodejs/manifests/install.pp:89 on node precise64

Quick Question

Hi Cmoudy -

I hope it's ok for me to ask this here. I'm sure this is a somewhat basic question, but I am getting started with setting this up, so forgive me if it is.

I have Vagrant installed, and have gotten as far as your third step to ssh into my app server ( vagrant ssh appserver ). It opens the standard vagrant ssh just fine, and I see only postinstall.sh there.

However, your next step, to launch the app server, from mytestapp directory confused me. Do you mean that I should do this from the directory on my mac where I installed this vagrant box, or should I be able to load node app.js from the vagrant ssh? Do I need to have loaded some other files onto the server already?

One thing to note, I had to change my vagrant setup file to use 10.0.0.1, and 10.0.0.2 instead of your 192.168... config because I was already using that for my local config.

Any thought appreciated, but I understand if this is too complex for you to try and troubleshoot for me here. Thanks regardless.

Jesse

wrong number of arguments error

$ vagrant up
/Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/plugins/kernel_v2/config/vm.rb:254:in provision': wrong number of arguments (2 for 1) (ArgumentError) from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/plugins/kernel_v1/config/vm.rb:149:inblock in upgrade'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/plugins/kernel_v1/config/vm.rb:148:in each' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/plugins/kernel_v1/config/vm.rb:148:inupgrade'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/v2/loader.rb:112:in block in upgrade' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/v2/loader.rb:110:ineach'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/v2/loader.rb:110:in upgrade' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/loader.rb:124:inblock (3 levels) in load'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/loader.rb:118:in upto' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/loader.rb:118:inblock (2 levels) in load'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/loader.rb:98:in each' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/loader.rb:98:inblock in load'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/loader.rb:95:in each' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/config/loader.rb:95:inload'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/vagrantfile.rb:133:in machine_config' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/vagrantfile.rb:45:inmachine'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/environment.rb:412:in machine' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/plugin/v2/command.rb:142:inblock in with_target_vms'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/plugin/v2/command.rb:175:in call' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/plugin/v2/command.rb:175:inblock in with_target_vms'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/plugin/v2/command.rb:174:in map' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/plugin/v2/command.rb:174:inwith_target_vms'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/plugins/commands/up/command.rb:58:in block in execute' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/environment.rb:230:inblock (2 levels) in batch'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/environment.rb:228:in tap' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/environment.rb:228:inblock in batch'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/environment.rb:227:in synchronize' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/environment.rb:227:inbatch'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/plugins/commands/up/command.rb:57:in execute' from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/cli.rb:42:inexecute'
from /Applications/Vagrant/embedded/gems/gems/vagrant-1.5.0/lib/vagrant/environment.rb:244:in cli' from /Applications/Vagrant/bin/../embedded/gems/gems/vagrant-1.5.0/bin/vagrant:147:in

'

appserver www doesn't up on vagrant up after halt.

I'm getting a webpage unvail on http://192.168.1.12:3000/ after I do the initial install, and then vagrant halt, vagrant up. I can vagrant ssh appserver, but I can't get to the address.

cmoudy / mean-vagrant Goto Github PK

mean-vagrant's People

Contributors

Stargazers

Watchers

Forkers

mean-vagrant's Issues

mongodb not able to access from localmachine

Errors upon startup

Any plans to update to Express 4.x ?

error installing librarian puppet

console output.

Error Message on Vagrant File

Quick Question

wrong number of arguments error

appserver www doesn't up on vagrant up after halt.

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent