search

azukiapp / azk

azk is a lightweight open source development environment orchestration tool. Instantly & safely run any environment on your local machine.
http://azk.io
Apache License 2.0
898 stars 63 forks source link

Unable to start #607

Closed bartekus closed 8 years ago

bartekus commented 8 years ago

So just as per basic instruction I used

git clone git@github.com:azukiapp/azk.git web-app

Then I executed

cd web-app && azk start

This is what I got:

azk: ↑ starting `dind-fedora` system, 1 new instances...
azk: ✓ checking `azukiapp/dind:fedora20` image...
azk: ⇲ downloading `azukiapp/dind:fedora20` image...
azk: ⇲ comparing registry layers and local layers...
azk: ⇲ pulling 10/10 layers.
     [=================================================] 100% 10/10
azk: ✓ completed download of `azukiapp/dind:fedora20`

azk: ⎘ syncing files for `dind-fedora` system...
azk: ↑ starting `dind-ubuntu15` system, 1 new instances...
azk: ✓ checking `azukiapp/dind:ubuntu15` image...
azk: ⇲ downloading `azukiapp/dind:ubuntu15` image...
azk: ⇲ comparing registry layers and local layers...

azk: ✓ completed download of `azukiapp/dind:ubuntu15`

azk: ⎘ syncing files for `dind-ubuntu15` system...
azk: ↑ starting `dind-ubuntu14` system, 1 new instances...
azk: ✓ checking `azukiapp/dind:ubuntu14` image...
azk: ⇲ downloading `azukiapp/dind:ubuntu14` image...
azk: ⇲ comparing registry layers and local layers...

azk: ✓ completed download of `azukiapp/dind:ubuntu14`

azk: ⎘ syncing files for `dind-ubuntu14` system...
azk: ↑ starting `dind-ubuntu12` system, 1 new instances...
azk: ✓ checking `azukiapp/dind:ubuntu12` image...
azk: ⇲ downloading `azukiapp/dind:ubuntu12` image...
azk: ⇲ comparing registry layers and local layers...

azk: ✓ completed download of `azukiapp/dind:ubuntu12`

azk: ⎘ syncing files for `dind-ubuntu12` system...
azk: Skip starting, system `package` does not scale.
azk: ↑ starting `pkg-fedora20-test` system, 1 new instances...
azk: ↑ starting `package` system, 1 new instances...
azk: ⇲ downloading `azukiapp/dind:fedora20` image...
azk: ⇲ comparing registry layers and local layers...

azk: ✓ completed download of `azukiapp/fpm:1.4.0`

azk: ⎘ syncing files for `package` system...
azk: ◴ waiting for `package` system to start, trying connection to port http/tcp...
azk: Run system `package` return: (127), for command: ["/bin/sh","-c","azk nvm ./src/libexec/package-tools/server"]:
azk:  .package [log] >  /usr/bin/env: node: No such file or directory
azk:  .package [log] >

azk: Look for azk start troubleshooting documentation for more info at: http://bit.ly/azk_start_troubleshooting

azk: Due to the above error azk will stop all instances already running.

azk: System `pkg-ubuntu12-test` not running
azk: System `pkg-ubuntu14-test` not running
azk: System `pkg-ubuntu15-test` not running
azk: System `pkg-fedora20-test` not running
azk: Skip stoping, system `package` does not scale.
azk: ↓ stopping `dind-ubuntu12` system, 1 instances...
azk: ↓ stopping `dind-ubuntu14` system, 1 instances...
azk: ↓ stopping `dind-ubuntu15` system, 1 instances...
azk: System `dind-fedora` not running

┌───┬───────────────────┬───────────┬────────────────────────┬─────────────────┬─────────────┬
│   │ System            │ Instances │ Hostname/url           │ Instances-Ports │ Provisioned │
├───┼───────────────────┼───────────┼────────────────────────┼─────────────────┼─────────────┤
│ ↓ │ pkg-ubuntu12-test │ 0         │ dev.azk.io             │ -               │ -           │
├───┼───────────────────┼───────────┼────────────────────────┼─────────────────┼─────────────┤
│ ↓ │ pkg-ubuntu14-test │ 0         │ dev.azk.io             │ -               │ -           │
├───┼───────────────────┼───────────┼────────────────────────┼─────────────────┼─────────────┤
│ ↓ │ pkg-ubuntu15-test │ 0         │ dev.azk.io             │ -               │ -           │
├───┼───────────────────┼───────────┼────────────────────────┼─────────────────┼─────────────┤
│ ↓ │ pkg-fedora20-test │ 0         │ dev.azk.io             │ -               │ -           │
├───┼───────────────────┼───────────┼────────────────────────┼─────────────────┼─────────────┤
│ − │ package           │ 0         │ package.azk.dev.azk.io │ -               │ -           │
├───┼───────────────────┼───────────┼────────────────────────┼─────────────────┼─────────────┤
│ ↓ │ dind-ubuntu12     │ 0         │ dev.azk.io             │ -               │ -           │
├───┼───────────────────┼───────────┼────────────────────────┼─────────────────┼─────────────┤
│ ↓ │ dind-ubuntu14     │ 0         │ dev.azk.io             │ -               │ -           │
├───┼───────────────────┼───────────┼────────────────────────┼─────────────────┼─────────────┤
│ ↓ │ dind-ubuntu15     │ 0         │ dev.azk.io             │ -               │ -           │
├───┼───────────────────┼───────────┼────────────────────────┼─────────────────┼─────────────┤
│ ↓ │ dind-fedora       │ 0         │ dev.azk.io             │ -               │ -           │
└───┴───────────────────┴───────────┴────────────────────────┴─────────────────┴─────────────┘

So I tried again:

azk start

and got this:

azk: ↑ starting `dind-fedora` system, 1 new instances...
azk: ✓ checking `azukiapp/dind:fedora20` image...
azk: ⎘ syncing files for `dind-fedora` system...
azk: ↑ starting `dind-ubuntu15` system, 1 new instances...
azk: ✓ checking `azukiapp/dind:ubuntu15` image...
azk: ⎘ syncing files for `dind-ubuntu15` system...
azk: ↑ starting `dind-ubuntu14` system, 1 new instances...
azk: ✓ checking `azukiapp/dind:ubuntu14` image...
azk: ⎘ syncing files for `dind-ubuntu14` system...
azk: ↑ starting `dind-ubuntu12` system, 1 new instances...
azk: ✓ checking `azukiapp/dind:ubuntu12` image...
azk: ⎘ syncing files for `dind-ubuntu12` system...
azk: Skip starting, system `package` does not scale.
azk: ↑ starting `pkg-fedora20-test` system, 1 new instances...
azk: ↑ starting `package` system, 1 new instances...
azk: ⎘ syncing files for `package` system...
azk: ◴ waiting for `package` system to start, trying connection to port http/tcp...
azk: Run system `package` return: (127), for command: ["/bin/sh","-c","azk nvm ./src/libexec/package-tools/server"]:
azk:  .package [log] >  /usr/bin/env: node: No such file or directory
azk:  .package [log] >

azk: Look for azk start troubleshooting documentation for more info at: http://bit.ly/azk_start_troubleshooting

azk: Due to the above error azk will stop all instances already running.

azk: System `pkg-ubuntu12-test` not running
azk: System `pkg-ubuntu14-test` not running
azk: System `pkg-ubuntu15-test` not running
azk: System `pkg-fedora20-test` not running
azk: Skip stoping, system `package` does not scale.
azk: ↓ stopping `dind-ubuntu12` system, 1 instances...
azk: ↓ stopping `dind-ubuntu14` system, 1 instances...
azk: ↓ stopping `dind-ubuntu15` system, 1 instances...
azk: ↓ stopping `dind-fedora` system, 1 instances...
azk: Error: HTTP code is 500 which indicates error: server error - Cannot stop container 473e8170cbcaaf715071d71a0da03d3fa1b3bf8bcf00b4f5e2dce59579b1de9b: [2] Container does not exist: container destroyed

azk:     at /usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:218:17
azk:     at getCause (/usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:246:7)
azk:     at [object Object].Modem.buildPayload (/usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:217:5)
azk:     at IncomingMessage.<anonymous> (/usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:193:14)
azk:     at IncomingMessage.emit (events.js:117:20)
azk:     at _stream_readable.js:944:16
azk:     at process._tickCallback (node.js:448:13)

I immediately thought that perhaps my $PATH was wrong and since I use .zsh that possibility was compounded. So I've inspected both .zshrc and .bashrc and confirmed that:

export ANDROID_HOME=/usr/local/opt/android-sdk
export GOROOT=$HOME/go 
export PATH=$PATH:$GOROOT/bin
export PATH=$GOPATH/bin:$PATH
export PATH=$PATH:/Users/__YOUR_USER_NAME__
export PATH=“/usr/local/git/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/bin:/sbin:/usr/X11/bin:/$HOME/.rvm/bin:/.node/bin:/elixir/bin:$PATH”

is matching and present in both.

To the next suspect:

azk: Run system `package` return: (127), for command: ["/bin/sh","-c","azk nvm ./src/libexec/package-tools/server"]:
azk:  .package [log] >  /usr/bin/env: node: No such file or directory
azk:  .package [log] >

azk: Look for azk start troubleshooting documentation for more info at: http://bit.ly/azk_start_troubleshooting

azk: Due to the above error azk will stop all instances already running.

azk: System `pkg-ubuntu12-test` not running
azk: System `pkg-ubuntu14-test` not running
azk: System `pkg-ubuntu15-test` not running
azk: System `pkg-fedora20-test` not running
azk: Skip stoping, system `package` does not scale.
azk: ↓ stopping `dind-ubuntu12` system, 1 instances...
azk: ↓ stopping `dind-ubuntu14` system, 1 instances...
azk: ↓ stopping `dind-ubuntu15` system, 1 instances...
azk: ↓ stopping `dind-fedora` system, 1 instances...
azk: Error: HTTP code is 500 which indicates error: server error - Cannot stop container 473e8170cbcaaf715071d71a0da03d3fa1b3bf8bcf00b4f5e2dce59579b1de9b: [2] Container does not exist: container destroyed

azk:     at /usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:218:17
azk:     at getCause (/usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:246:7)
azk:     at [object Object].Modem.buildPayload (/usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:217:5)
azk:     at IncomingMessage.<anonymous> (/usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:193:14)
azk:     at IncomingMessage.emit (events.js:117:20)
azk:     at _stream_readable.js:944:16
azk:     at process._tickCallback (node.js:448:13)

So I look into this more:

azk:     at /usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:218:17

Cellar most often is present with 'brew' installs, but how could that be wrong, I just installed it and even run 'brew update && brew upgrade' hmmm... time to execute:

brew doctor

So this is what I go:

Warning: You have unlinked kegs in your Cellar
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:
    docker-machine

Here I ran:

run 'brew link docker-machine'

thereafter I retried once more but still getting nowhere: 

azk: Run system `package` return: (127), for command: ["/bin/sh","-c","azk nvm ./src/libexec/package-tools/server"]:
azk:  .package [log] >  /usr/bin/env: node: No such file or directory
azk:  .package [log] >

ok it's nvm damn NVM! lol hmm this is interesting... https://github.com/creationix/nvm/issues/855

added 

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh"

to my .zshrc && .bashrc

then restart my shell and got:

nvm is not compatible with the npm config "prefix" option: currently set to "/Users/Bart/npm"
Run `npm config delete prefix` or `nvm use --delete-prefix v5.0.0 --silent` to unset it.

seems obvious what needs to be dont but just to be sure:

nvm deactivate ; nvm debug ; echo $PREFIX ; echo $NPM_CONFIG_PREFIX

Could not find /Users/Bart/.nvm/*/bin in $PATH
Could not find /Users/Bart/.nvm/*/share/man in $MANPATH
$SHELL: /bin/zsh
$NVM_DIR: '$HOME/.nvm'
$PREFIX: ''
$NPM_CONFIG_PREFIX: ''
nvm current: system
which node: /usr/local/bin/node
which iojs: iojs not found
which npm: /usr/local/bin/npm
npm config get prefix: $HOME/npm
npm root -g: $HOME/npm/lib/node_modules

ok now we go with

nvm use --delete-prefix v5.0.0 --silent

then we check it:

nvm deactivate ; nvm debug ; echo $PREFIX ; echo $NPM_CONFIG_PREFIX

/Users/Bart/.nvm/*/bin removed from $PATH
/Users/Bart/.nvm/*/share/man removed from $MANPATH
$SHELL: /bin/zsh
$NVM_DIR: '$HOME/.nvm'
$PREFIX: ''
$NPM_CONFIG_PREFIX: ''
nvm current: system
which node: /usr/local/bin/node
which iojs: iojs not found
which npm: /usr/local/bin/npm
npm config get prefix: /usr/local
npm root -g: /usr/local/lib/node_modules

Trying to run azk start once more, still nothing but... azk is trying to connect on http://192.168.50.4:2375 but I'm pretty sure mines on 192.168.100..... range ok so perhaps this is it then... but how do I change that?

fearenales commented 8 years ago

Hi @Bartekus !

We've noticed you tried to run azk source code using azk itself. That's not how azk is supposed to be used, so may I ask you where did you get those instructions from?

$ git clone git@github.com:azukiapp/azk.git web-app
$ cd web-app && azk start

azk is a command line tool that orchestrates your development environment, helping you to install and safely run any application in your machine. It's not a web app, so you cannot start it using an azk command.

Besides that, looks like you have azk properly installed, so no worries about it. Now, you can use it to run other projects. Take a look in our gallery and try it out.

If you are interested in running your own application using azk, you'll have to have an Azkfile so that azk will be able to run it. Check our docs out: http://docs.azk.io/en/getting-started/configs-project.html

bartekus commented 8 years ago

I'm sorry, I tend to get lost in my own mind, and I've seen that command run on the front-page gif that you have on azk.io as I was thinking about something else and for no apparent reason other than curiosity I just typed it and wen't with it. I was a little bit surprised as I've run your awesome environment before so I figured that I must of screw something up with my last docker update so I started to investigate. One thing led to other and as I combed thru every aspect of my systems configuration I found numerous little thing that weren't 100% and in process fix my entire machine, all while learn the details of a few things I never before care to learn, yet I'm glad I did. However now I've returned to my program yet it seems it still wants to connect to http://192.168.50.4:2375 but I'm fairly certain that my docker runs on 192.168.99.100.

This is my Azkfile:

/**
 * Documentation: http://docs.azk.io/Azkfile.js
 */
// Adds the systems that shape your system
systems({
  r3stack: {
    // Dependent systems
    depends: [],
    // More images:  http://images.azk.io
    image: {"docker": "azukiapp/node"},
    // Steps to execute before running instances
    provision: [
      "npm install",
    ],
    workdir: "/azk/#{manifest.dir}",
    shell: "/bin/bash",
    command: ["npm run quickstart"],
    wait: {"retry": 20, "timeout": 1000},
    mounts: {
      '/azk/#{manifest.dir}': sync("."),
      '/azk/#{manifest.dir}/node_modules': persistent("./node_modules"),
    },
    scalable: {"default": 1},
    http: {
      domains: [ "#{system.name}.#{azk.default_domain}" ]
    },
    ports: {
      // exports global variables
      http: "3000/tcp",
    },
    envs: {
      // Make sure that the PORT value is the same as the one
      // in ports/http below, and that it's also the same
      // if you're setting it in a .env file
      NODE_ENV: "development",
      PORT: "3000",
    },
  },
  rethinkdb: {
    image: { docker: 'rethinkdb' },
    shell: '/bin/bash',
    scalable: false,
    command: 'rethinkdb --bind all --directory ./rethinkdb',
    wait: {'retry': 20, 'timeout': 1000},
    mounts: {
      '/rethinkdb': persistent('rethinkdb-#{manifest.dir}'),
    },
    ports: {
      http: '8080',
      data: '28015',
    },
    http: {
      domains: [ '#{system.name}.#{azk.default_domain}' ],
    },
    export_envs: {
      "DATABASE_URL": 'rethinkdb://#{net.host}:#{net.port.data}',
    }
  }
});

this isthe script part of my package.json

"scripts": {
    "start": "NODE_ENV=development node ./src/server/server.babel.js",
    "prod": "NODE_ENV=production node ./src/server/server.babel.js",
    "build": "rimraf build && concurrent \"npm run build:client\" \"npm run build:server\"",
    "bs": "rimraf build && concurrent \"npm run build:client\" \"npm run build:server\" \"npm run prod\"",
    "quickstart": "rimraf build && concurrent \"npm run build:db\" \"npm run build:client\" \"npm run build:server\" \"npm run prod\"",
    "build:client": "NODE_ENV=production webpack --colors --config ./webpack/prod.babel.js",
    "build:server": "NODE_ENV=production webpack --colors --config ./webpack/server.babel.js",
    "build:db": "node ./src/server/database/setupDB.babel.js",
    "test": "NODE_ENV=testing ava ./src/**/__tests___/**/*.js --verbose",
    "lint": "xo src/**/*.js --plugin=react --env node --env browser --esnext --space --fix",
    "profile": "NODE_ENV=production webpack --config ./webpack/prod.babel.js --profile --json > stats.json"
  },
 azk start && azk logs --follow                       ✓  10002  11:48:26
? The agent is not running, would you like to start it? Yes
azk: Please wait, this process may take several minutes
azk: Loading settings and checking dependencies.
azk: Checking version...
azk: azk 0.16.3 detected
azk: Settings loaded successfully.
azk: Removing virtual machine...
azk: Virtual machine has been successfully removed.
azk: Agent is being started...
azk: Installing virtual machine...
azk: Virtual machine has been successfully installed.
azk: Setting the ssh key to vm...
azk: Starting virtual machine...
azk: Waiting for virtual machine boot...
azk: Virtual machine is ready to use.
azk: Mounting the shared folder in virtual machine...
azk: Shared folder has been successfully mounted.
azk: Trying to connect to docker (http://192.168.50.4:2375) (timeout: 20s)...
azk: Starting azk dns service...
azk: Dns service started.
azk: Trying to connect to docker (http://192.168.50.4:2375) (timeout: 20s)...
azk: Starting azk balancer redirect service...
azk: Check if balancer redirect service is up (tcp://192.168.50.4:80) (timeout: 10000s)...
azk: Balancer redirect started.
azk: Starting memcached service...
azk: Memcached service started.
azk: Starting http balancer service...
azk: Http balancer service started.
azk: Agent has been successfully started.
azk: ↑ starting `rethinkdb` system, 1 new instances...
azk: ✓ checking `library/rethinkdb:latest` image...
azk: ◴ waiting for `rethinkdb` system to start, trying connection to port http/tcp...
azk: ↑ starting `r3stack` system, 1 new instances...
azk: ✓ checking `azukiapp/node:latest` image...
azk: ⎘ syncing files for `r3stack` system...
azk: Error: HTTP code is 404 which indicates error: no such container - Cannot start container abed508b4ed1212d8467287660a2bdf9ee3cb88d56efcef2e76f27b7ddb8ec45: [8] System error: exec: "npm run quickstart": executable file not found in $PATH

azk:     at /usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:218:17
azk:     at getCause (/usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:246:7)
azk:     at [object Object].Modem.buildPayload (/usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:217:5)
azk:     at IncomingMessage.<anonymous> (/usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:193:14)
azk:     at IncomingMessage.emit (events.js:117:20)
azk:     at _stream_readable.js:944:16
azk:     at process._tickCallback (node.js:448:13)
azk: Due to the above error azk will stop all instances already running.

azk: System `r3stack` not running
azk: ↓ stopping `rethinkdb` system, 1 instances...
┌───┬───────────┬───────────┬──────────────────────┬─────────────────┬──────────────┐
│   │ System    │ Instances │ Hostname/url         │ Instances-Ports │ Provisioned  │
├───┼───────────┼───────────┼──────────────────────┼─────────────────┼──────────────┤
│ ↓ │ r3stack   │ 0         │ r3stack.dev.azk.io   │ -               │ 17 hours ago │
├───┼───────────┼───────────┼──────────────────────┼─────────────────┼──────────────┤
│ ↓ │ rethinkdb │ 0         │ rethinkdb.dev.azk.io │ -               │ -            │
└───┴───────────┴───────────┴──────────────────────┴─────────────────┴──────────────┘

What should I do?

gullitmiranda commented 8 years ago

@Bartekus, try add the PATH env in your Azkfile:

e.g.:

  envs: {
    // Make sure that the PORT value is the same as the one
    // in ports/http below, and that it's also the same
    // if you're setting it in a .env file
    NODE_ENV: "development",
    PORT: "3000",
    PATH: "//azk/#{manifest.dir}/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin",
  },
bartekus commented 8 years ago

Still nothing, I even tried to reinstall it, but it still tries to connect to the docker on the wrong ip, how do I change that?

Here is the whole process from removal of azk to reinstall and subsequent attempt to start it:

 Bart@Araphel  ~/Dev/BIN/WORK/r3stack   master ●  brew doctor                                                                              ✓  10074  18:03:56
Your system is ready to brew.
 Bart@Araphel  ~/Dev/BIN/WORK/r3stack   master ●  brew update && brew upgrade                                                              ✓  10075  18:04:17
Already up-to-date.
 Bart@Araphel  ~/Dev/BIN/WORK/r3stack   master ●  azk                                                                                      ✓  10076  18:04:32
zsh: command not found: azk
 Bart@Araphel  ~/Dev/BIN/WORK/r3stack   master ●  clear                                                                                127 ↵  10077  18:04:35
 Bart@Araphel  ~/Dev/BIN/WORK/r3stack   master ●  curl -sSL http://azk.io/install.sh | bash                                                ✓  10078  18:05:41
[azk] Checking platform.......................................[ DONE ]
[azk]   Detected platform: darwin, x64
[azk] Checking for VirtualBox installation....................[ DONE ]
[azk]   Virtual Box detected
[azk] Checking for Homebrew installation......................[ DONE ]
[azk]   Homebrew detected
[azk] Installing azk..........................................[ WAIT ]
==> Installing azk from azukiapp/azk
==> Downloading http://repo.azukiapp.com/mac/azk_0.16.3.tar.gz
Already downloaded: /Library/Caches/Homebrew/azk-0.16.3.tar.gz
🍺  /usr/local/Cellar/azk/0.16.3: 11,889 files, 158.4M, built in 11 seconds
[azk] Installing azk..........................................[ DONE ]

[azk] azk has been successfully installed.
 Bart@Araphel  ~/Dev/BIN/WORK/r3stack   master ●  brew update && brew upgrade                                                              ✓  10079  18:06:09
Already up-to-date.
 Bart@Araphel  ~/Dev/BIN/WORK/r3stack   master ●  azk start && azk logs --follow                                                           ✓  10080  18:06:25
? The agent is not running, would you like to start it? Yes
azk: Please wait, this process may take several minutes
azk: Loading settings and checking dependencies.
azk: Checking version...
azk: azk 0.16.3 detected
azk: Settings loaded successfully.
azk: Removing virtual machine...
azk: Virtual machine has been successfully removed.
azk: Agent is being started...
azk: Installing virtual machine...
azk: Virtual machine has been successfully installed.
azk: Setting the ssh key to vm...
azk: Starting virtual machine...
azk: Waiting for virtual machine boot...
azk: Virtual machine is ready to use.
azk: Mounting the shared folder in virtual machine...
azk: Shared folder has been successfully mounted.
azk: Trying to connect to docker (http://192.168.50.4:2375) (timeout: 20s)...
azk: Starting azk dns service...
azk: Dns service started.
azk: Trying to connect to docker (http://192.168.50.4:2375) (timeout: 20s)...
azk: Starting azk balancer redirect service...
azk: Check if balancer redirect service is up (tcp://192.168.50.4:80) (timeout: 10000s)...
azk: Balancer redirect started.
azk: Starting memcached service...
azk: Memcached service started.
azk: Starting http balancer service...
azk: Http balancer service started.
azk: Agent has been successfully started.
azk: ↑ starting `rethinkdb` system, 1 new instances...
azk: ✓ checking `library/rethinkdb:latest` image...
azk: ◴ waiting for `rethinkdb` system to start, trying connection to port http/tcp...
azk: ↑ starting `r3stack` system, 1 new instances...
azk: ✓ checking `azukiapp/node:latest` image...
azk: ⎘ syncing files for `r3stack` system...
azk: Error: HTTP code is 404 which indicates error: no such container - Cannot start container 2791bb9fdc5f2de4d1163e922ddf941afe1e052c5afd8fd7a7384c45e66da821: [8] System error: exec: "npm run quickstart": executable file not found in $PATH

azk:     at /usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:218:17
azk:     at getCause (/usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:246:7)
azk:     at [object Object].Modem.buildPayload (/usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:217:5)
azk:     at IncomingMessage.<anonymous> (/usr/local/Cellar/azk/0.16.3/node_modules/dockerode/node_modules/docker-modem/lib/modem.js:193:14)
azk:     at IncomingMessage.emit (events.js:117:20)
azk:     at _stream_readable.js:944:16
azk:     at process._tickCallback (node.js:448:13)
azk: Due to the above error azk will stop all instances already running.

azk: System `r3stack` not running
azk: ↓ stopping `rethinkdb` system, 1 instances...

┌───┬───────────┬───────────┬──────────────────────┬─────────────────┬─────────────┐
│   │ System    │ Instances │ Hostname/url         │ Instances-Ports │ Provisioned │
├───┼───────────┼───────────┼──────────────────────┼─────────────────┼─────────────┤
│ ↓ │ r3stack   │ 0         │ r3stack.dev.azk.io   │ -               │ 4 days ago  │
├───┼───────────┼───────────┼──────────────────────┼─────────────────┼─────────────┤
│ ↓ │ rethinkdb │ 0         │ rethinkdb.dev.azk.io │ -               │ -           │
└───┴───────────┴───────────┴──────────────────────┴─────────────────┴─────────────┘
 Bart@Araphel  ~/Dev/BIN/WORK/r3stack   master ●                                                                                       127 ↵  10081  18:07:12
gullitmiranda commented 8 years ago

@Bartekus the package rimraf is present in your package.json?

bartekus commented 8 years ago

Yes it is, here is the whole content of package.json:

{
  "name": "r3stack",
  "version": "1.0.0-alpha",
  "description": "react, redux, rethink, babel, webpack, ava",
  "repository": {
    "type": "git",
    "url": "git+https://github.com/Araphel/r3stack.git"
  },
  "bugs": {
    "url": "https://github.com/Araphel/r3stack/issues"
  },
  "main": "index.js",
  "scripts": {
    "start": "NODE_ENV=development node ./src/server/server.babel.js",
    "prod": "NODE_ENV=production node ./src/server/server.babel.js",
    "build": "rimraf build && concurrent \"npm run build:client\" \"npm run build:server\"",
    "bs": "rimraf build && concurrent \"npm run build:client\" \"npm run build:server\" \"npm run prod\"",
    "quickstart": "rimraf build && concurrent \"npm run build:db\" \"npm run build:client\" \"npm run build:server\" \"npm run prod\"",
    "build:client": "NODE_ENV=production webpack --colors --config ./webpack/prod.babel.js",
    "build:server": "NODE_ENV=production webpack --colors --config ./webpack/server.babel.js",
    "build:db": "node ./src/server/database/setupDB.babel.js",
    "test": "NODE_ENV=testing ava ./src/**/__tests___/**/*.js --verbose",
    "lint": "xo src/**/*.js --plugin=react --env node --env browser --esnext --space --fix",
    "profile": "NODE_ENV=production webpack --config ./webpack/prod.babel.js --profile --json > stats.json"
  },
  "author": "Matt Krick <matt.krick@gmail.com>",
  "coauthor": "Bartek Kus <bartekus@gmail.com>",
  "license": "MIT",
  "devDependencies": {
    "assets-webpack-plugin": "3.2.0",
    "ava": "0.10.0",
    "babel-cli": "6.4.0",
    "babel-core": "6.4.0",
    "babel-loader": "6.2.1",
    "babel-plugin-add-module-exports": "0.1.2",
    "babel-plugin-react-transform": "2.0.0",
    "babel-plugin-transform-decorators-legacy": "1.3.4",
    "babel-preset-es2015": "6.3.13",
    "babel-preset-react": "6.3.13",
    "babel-preset-stage-0": "6.3.13",
    "babel-register": "6.4.3",
    "concurrently": "1.0.0",
    "css-loader": "0.23.1",
    "eslint-plugin-react": "3.15.0",
    "extract-text-webpack-plugin": "1.0.1",
    "fake-style-loader": "1.0.0",
    "file-loader": "0.8.5",
    "json-loader": "0.5.4",
    "null-loader": "0.1.1",
    "postcss-loader": "0.8.0",
    "postcss-modules-values": "1.1.1",
    "raw-loader": "0.5.1",
    "react-addons-test-utils": "0.14.6",
    "react-transform-catch-errors": "1.0.1",
    "react-transform-hmr": "1.0.1",
    "redbox-react": "1.2.0",
    "redux-devtools": "3.0.1",
    "redux-devtools-dock-monitor": "1.0.1",
    "redux-devtools-log-monitor": "1.0.2",
    "rimraf": "2.5.0",
    "stats-webpack-plugin": "0.3.0",
    "style-loader": "0.13.0",
    "url-loader": "0.5.7",
    "webpack": "2.0.2-beta",
    "webpack-dev-middleware": "1.4.0",
    "webpack-hot-middleware": "2.6.0",
    "xo": "0.12.1"
  },
  "dependencies": {
    "babel-polyfill": "6.3.14",
    "babel-runtime": "6.3.19",
    "bcrypt": "0.8.5",
    "body-parser": "1.14.2",
    "compression": "1.6.0",
    "cors": "2.7.1",
    "deep-equal": "1.0.1",
    "es6-promisify": "3.0.0",
    "express": "4.13.3",
    "express-jwt": "3.3.0",
    "googleapis": "2.1.7",
    "graphiql": "0.4.5",
    "graphql": "0.4.14",
    "immutable": "3.7.6",
    "isomorphic-fetch": "2.2.1",
    "joi": "7.2.1",
    "jsonwebtoken": "5.5.4",
    "jwt-decode": "1.5.0",
    "material-ui": "0.14.2",
    "node-uuid": "1.4.7",
    "piping": "0.3.0",
    "query-string": "3.0.0",
    "react": "0.14.6",
    "react-dnd": "2.0.2",
    "react-dnd-html5-backend": "2.0.2",
    "react-dom": "0.14.6",
    "react-dom-stream": "0.4.1",
    "react-redux": "4.0.6",
    "react-router": "2.0.0-rc5",
    "react-tap-event-plugin": "0.2.1",
    "redux": "3.0.5",
    "redux-devtools": "3.0.1",
    "redux-devtools-dock-monitor": "1.0.1",
    "redux-devtools-log-monitor": "1.0.2",
    "redux-form": "4.1.3",
    "redux-immutablejs": "0.0.8",
    "redux-logger": "2.3.2",
    "redux-optimistic-ui": "0.3.0",
    "redux-promise": "0.5.0",
    "redux-simple-router": "2.0.3",
    "redux-socket-cluster": "0.5.1",
    "redux-thunk": "1.0.3",
    "reselect": "2.0.2",
    "rethinkdbdash": "2.2.17",
    "socketcluster": "4.1.0",
    "socketcluster-client": "4.1.2",
    "url": "0.11.0"
  }
}

My docker however is telling me this:


                        ##         .
                  ## ## ##        ==
               ## ## ## ## ##    ===
           /"""""""""""""""""\___/ ===
      ~~~ {~~ ~~~~ ~~~ ~~~~ ~~~ ~ /  ===- ~~~
           \______ o           __/
             \    \         __/
              \____\_______/

docker is configured to use the default machine with IP 192.168.99.100
For help getting started, check out the docs at https://docs.docker.com
gullitmiranda commented 8 years ago

try the following commands, stop if an error occurs. there sent me the complete output.

$ azk shell r3stack
$ echo $PATH
$ rimraf build
$ concurrent \"npm run build:db\" \"npm run build:client\" \"npm run build:server\" \"npm run prod\"
bartekus commented 8 years ago

Here is what I get:

 Bart@Araphel  ~/Dev/BIN/WORK/r3stack   master ●  azk shell r3stack                                                                               127 ↵  10014  19:42:16
root@bbbed175209e:/azk/r3stack# echo $PATH
//azk/r3stack/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
root@bbbed175209e:/azk/r3stack# rimraf build
root@bbbed175209e:/azk/r3stack# concurrent \"npm run build:db\" \"npm run build:client\" \"npm run build:server\" \"npm run prod\"
Error occured when executing command: prod"
Error: spawn np ENOENT
    at exports._errnoException (util.js:856:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:179:32)
    at onErrorNT (internal/child_process.js:345:16)
    at nextTickCallbackWith2Args (node.js:455:9)
    at process._tickCallback (node.js:369:17)
    at Function.Module.runMain (module.js:433:11)
    at startup (node.js:141:18)
    at node.js:977:3
Error occured when executing command: prod"
Error: spawn run ENOENT
    at exports._errnoException (util.js:856:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:179:32)
    at onErrorNT (internal/child_process.js:345:16)
    at nextTickCallbackWith2Args (node.js:455:9)
    at process._tickCallback (node.js:369:17)
    at Function.Module.runMain (module.js:433:11)
    at startup (node.js:141:18)
    at node.js:977:3
Error occured when executing command: prod"
Error: spawn build:db" ENOENT
    at exports._errnoException (util.js:856:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:179:32)
    at onErrorNT (internal/child_process.js:345:16)
    at nextTickCallbackWith2Args (node.js:455:9)
    at process._tickCallback (node.js:369:17)
    at Function.Module.runMain (module.js:433:11)
    at startup (node.js:141:18)
    at node.js:977:3
Error occured when executing command: prod"
Error: spawn np ENOENT
    at exports._errnoException (util.js:856:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:179:32)
    at onErrorNT (internal/child_process.js:345:16)
    at nextTickCallbackWith2Args (node.js:455:9)
    at process._tickCallback (node.js:369:17)
    at Function.Module.runMain (module.js:433:11)
    at startup (node.js:141:18)
    at node.js:977:3
Error occured when executing command: prod"
Error: spawn run ENOENT
    at exports._errnoException (util.js:856:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:179:32)
    at onErrorNT (internal/child_process.js:345:16)
    at nextTickCallbackWith2Args (node.js:455:9)
    at process._tickCallback (node.js:369:17)
    at Function.Module.runMain (module.js:433:11)
    at startup (node.js:141:18)
    at node.js:977:3
Error occured when executing command: prod"
Error: spawn build:client" ENOENT
    at exports._errnoException (util.js:856:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:179:32)
    at onErrorNT (internal/child_process.js:345:16)
    at nextTickCallbackWith2Args (node.js:455:9)
    at process._tickCallback (node.js:369:17)
    at Function.Module.runMain (module.js:433:11)
    at startup (node.js:141:18)
    at node.js:977:3
Error occured when executing command: prod"
Error: spawn np ENOENT
    at exports._errnoException (util.js:856:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:179:32)
    at onErrorNT (internal/child_process.js:345:16)
    at nextTickCallbackWith2Args (node.js:455:9)
    at process._tickCallback (node.js:369:17)
    at Function.Module.runMain (module.js:433:11)
    at startup (node.js:141:18)
    at node.js:977:3
Error occured when executing command: prod"
Error: spawn run ENOENT
    at exports._errnoException (util.js:856:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:179:32)
    at onErrorNT (internal/child_process.js:345:16)
    at nextTickCallbackWith2Args (node.js:455:9)
    at process._tickCallback (node.js:369:17)
    at Function.Module.runMain (module.js:433:11)
    at startup (node.js:141:18)
    at node.js:977:3
Error occured when executing command: prod"
Error: spawn build:server" ENOENT
    at exports._errnoException (util.js:856:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:179:32)
    at onErrorNT (internal/child_process.js:345:16)
    at nextTickCallbackWith2Args (node.js:455:9)
    at process._tickCallback (node.js:369:17)
    at Function.Module.runMain (module.js:433:11)
    at startup (node.js:141:18)
    at node.js:977:3
Error occured when executing command: prod"
Error: spawn np ENOENT
    at exports._errnoException (util.js:856:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:179:32)
    at onErrorNT (internal/child_process.js:345:16)
    at nextTickCallbackWith2Args (node.js:455:9)
    at process._tickCallback (node.js:369:17)
    at Function.Module.runMain (module.js:433:11)
    at startup (node.js:141:18)
    at node.js:977:3
Error occured when executing command: prod"
Error: spawn run ENOENT
    at exports._errnoException (util.js:856:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:179:32)
    at onErrorNT (internal/child_process.js:345:16)
    at nextTickCallbackWith2Args (node.js:455:9)
    at process._tickCallback (node.js:369:17)
    at Function.Module.runMain (module.js:433:11)
    at startup (node.js:141:18)
    at node.js:977:3
Error occured when executing command: prod"
Error: spawn prod" ENOENT
    at exports._errnoException (util.js:856:11)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:179:32)
    at onErrorNT (internal/child_process.js:345:16)
    at nextTickCallbackWith2Args (node.js:455:9)
    at process._tickCallback (node.js:369:17)
    at Function.Module.runMain (module.js:433:11)
    at startup (node.js:141:18)
    at node.js:977:3
[11] prod" exited with code -2
root@bbbed175209e:/azk/r3stack#
gullitmiranda commented 8 years ago

apparently is happening a bug in npm run prod. To be sure try the following:

$ azk shell r3stack
$ rimraf build
$ npm run build:db
$ npm run build:client
$ npm run build:server
$ npm run prod
bartekus commented 8 years ago

Here is what I get:

root@0a200e827086:/azk/r3stack# rimraf build
root@0a200e827086:/azk/r3stack# npm run build:db
npm info it worked if it ends with ok
npm info using npm@3.3.12
npm info using node@v5.2.0
npm info lifecycle r3stack@1.0.0-alpha~prebuild:db: r3stack@1.0.0-alpha
npm info lifecycle r3stack@1.0.0-alpha~build:db: r3stack@1.0.0-alpha

> r3stack@1.0.0-alpha build:db /azk/r3stack
> node ./src/server/database/setupDB.babel.js

Creating a pool connected to localhost:28015
Entering slow growth mode
Fail to create a new connection for the connection pool. Error:{"message":"Failed to connect to localhost:28015\nFull error:\n{\"code\":\"ECONNREFUSED\",\"errno\":\"ECONNREFUSED\",\"syscall\":\"connect\",\"address\":\"127.0.0.1\",\"port\":28015}.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"message":"Failed to connect to localhost:28015\nFull error:\n{\"code\":\"ECONNREFUSED\",\"errno\":\"ECONNREFUSED\",\"syscall\":\"connect\",\"address\":\"127.0.0.1\",\"port\":28015}.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"message":"Failed to connect to localhost:28015\nFull error:\n{\"code\":\"ECONNREFUSED\",\"errno\":\"ECONNREFUSED\",\"syscall\":\"connect\",\"address\":\"127.0.0.1\",\"port\":28015}.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"message":"Failed to connect to localhost:28015\nFull error:\n{\"code\":\"ECONNREFUSED\",\"errno\":\"ECONNREFUSED\",\"syscall\":\"connect\",\"address\":\"127.0.0.1\",\"port\":28015}.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"message":"Failed to connect to localhost:28015\nFull error:\n{\"code\":\"ECONNREFUSED\",\"errno\":\"ECONNREFUSED\",\"syscall\":\"connect\",\"address\":\"127.0.0.1\",\"port\":28015}.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"message":"Failed to connect to localhost:28015\nFull error:\n{\"code\":\"ECONNREFUSED\",\"errno\":\"ECONNREFUSED\",\"syscall\":\"connect\",\"address\":\"127.0.0.1\",\"port\":28015}.","isOperational":true}
Fail to create a new connection for the connection pool. Error:{"message":"Failed to connect to localhost:28015\nFull error:\n{\"code\":\"ECONNREFUSED\",\"errno\":\"ECONNREFUSED\",\"syscall\":\"connect\",\"address\":\"127.0.0.1\",\"port\":28015}.","isOperational":true}
^C
root@0a200e827086:/azk/r3stack# npm run build:client
npm info it worked if it ends with ok
npm info using npm@3.3.12
npm info using node@v5.2.0
npm info lifecycle r3stack@1.0.0-alpha~prebuild:client: r3stack@1.0.0-alpha
npm info lifecycle r3stack@1.0.0-alpha~build:client: r3stack@1.0.0-alpha

> r3stack@1.0.0-alpha build:client /azk/r3stack
> NODE_ENV=production webpack --colors --config ./webpack/prod.babel.js

Hash: a19f19da1b055f4aab9a
Version: webpack 2.0.2-beta
Time: 36665ms
                               Asset     Size  Chunks             Chunk Names
37681ed619fcde1be52da659ee7288ff.jpg   243 kB          [emitted]
           0_bc60c6ad279a86d47deb.js  27.6 kB    0, 4  [emitted]
           1_be618267abb21d5f8b9f.js  36.9 kB    1, 4  [emitted]
           2_9077508edbcc1c86d2c1.js   138 kB    2, 4  [emitted]
           3_52028c45d862583d7bbb.js   459 kB    3, 4  [emitted]
    manifest_dbf84eff6deaa906b2ab.js  1.14 kB       4  [emitted]  manifest
         app_f5d1b117bacfd3a66d4f.js   499 kB    5, 4  [emitted]  app
      vendor_28a30fcb97bda3f33e1b.js   504 kB    6, 4  [emitted]  vendor
   [2] multi app 40 bytes {5} [built]
   [3] multi vendor 52 bytes {6} [built]
    + 1119 hidden modules
npm info lifecycle r3stack@1.0.0-alpha~postbuild:client: r3stack@1.0.0-alpha
npm info ok
root@0a200e827086:/azk/r3stack# npm run build:server
npm info it worked if it ends with ok
npm info using npm@3.3.12
npm info using node@v5.2.0
npm info lifecycle r3stack@1.0.0-alpha~prebuild:server: r3stack@1.0.0-alpha
npm info lifecycle r3stack@1.0.0-alpha~build:server: r3stack@1.0.0-alpha

> r3stack@1.0.0-alpha build:server /azk/r3stack
> NODE_ENV=production webpack --colors --config ./webpack/server.babel.js

Hash: b82c433bddb8c239db63
Version: webpack 2.0.2-beta
Time: 25460ms
                               Asset     Size  Chunks             Chunk Names
37681ed619fcde1be52da659ee7288ff.jpg   243 kB          [emitted]
                        prerender.js   987 kB       0  [emitted]  prerender
                       prerender.css  31.1 kB       0  [emitted]  prerender
    + 779 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 3 hidden modules
Child extract-text-webpack-plugin:
        + 5 hidden modules
Child extract-text-webpack-plugin:
        + 3 hidden modules
Child extract-text-webpack-plugin:
        + 3 hidden modules
Child extract-text-webpack-plugin:
        + 3 hidden modules
Child extract-text-webpack-plugin:
        + 3 hidden modules
npm info lifecycle r3stack@1.0.0-alpha~postbuild:server: r3stack@1.0.0-alpha
npm info ok
root@0a200e827086:/azk/r3stack# npm run prod
npm info it worked if it ends with ok
npm info using npm@3.3.12
npm info using node@v5.2.0
npm info lifecycle r3stack@1.0.0-alpha~preprod: r3stack@1.0.0-alpha
npm info lifecycle r3stack@1.0.0-alpha~prod: r3stack@1.0.0-alpha

> r3stack@1.0.0-alpha prod /azk/r3stack
> NODE_ENV=production node ./src/server/server.babel.js

   [Busy] Launching SocketCluster
   >> Broker PID: 104
1453777008515 - Origin: Broker (PID 104)
   [Error] Error: listen EPERM /azk/r3stack/socketcluster/Meatier_4fef3560d7/b0
    at Object.exports._errnoException (util.js:856:11)
    at exports._exceptionWithHostPort (util.js:879:20)
    at Server._listen2 (net.js:1225:19)
    at listen (net.js:1274:10)
    at Server.listen (net.js:1364:5)
    at EventEmitter.self.listen (/azk/r3stack/node_modules/ncom/index.js:139:19)
    at Object.<anonymous> (/azk/r3stack/node_modules/sc-broker/server.js:505:10)
    at Module._compile (module.js:399:26)
    at Object.Module._extensions..js (module.js:406:10)
    at Module.load (module.js:345:32)

One thing to notice here is that the 'npm run build:db' requires database to be up and running for it to execute properly which is also what 'npm run prod' depends on, that build:db has completed the structuring and basic hydration of db.

gullitmiranda commented 8 years ago

then try start rethinkdb before:

$ azk start rethinkdb
$ azk shell r3stack
$ rimraf build
$ npm run build:db
$ npm run build:client
$ npm run build:server
$ npm run prod
bartekus commented 8 years ago

Ok looks very good now:

 Bart@Araphel  ~/Dev/BIN/WORK/r3stack   master ●  azk start rethinkdb                                                             ✓  10023  20:58:58
azk: ↑ starting `rethinkdb` system, 1 new instances...
azk: ✓ checking `library/rethinkdb:latest` image...
azk: ◴ waiting for `rethinkdb` system to start, trying connection to port http/tcp...

┌───┬───────────┬───────────┬─────────────────────────────┬────────────────────────────┬─────────────┐
│   │ System    │ Instances │ Hostname/url                │ Instances-Ports            │ Provisioned │
├───┼───────────┼───────────┼─────────────────────────────┼────────────────────────────┼─────────────┤
│ ↑ │ rethinkdb │ 1         │ http://rethinkdb.dev.azk.io │ 1-http:32777, 1-data:32776 │ -           │
│   │           │           │                             │ 1-29015:32775              │             │
└───┴───────────┴───────────┴─────────────────────────────┴────────────────────────────┴─────────────┘
 Bart@Araphel  ~/Dev/BIN/WORK/r3stack   master ●  azk shell r3stack                                                               ✓  10024  20:59:29
root@f071e1d2fc30:/azk/r3stack# rimraf build
root@f071e1d2fc30:/azk/r3stack# npm run build:db
npm info it worked if it ends with ok
npm info using npm@3.3.12
npm info using node@v5.2.0
npm info lifecycle r3stack@1.0.0-alpha~prebuild:db: r3stack@1.0.0-alpha
npm info lifecycle r3stack@1.0.0-alpha~build:db: r3stack@1.0.0-alpha

> r3stack@1.0.0-alpha build:db /azk/r3stack
> node ./src/server/database/setupDB.babel.js

Creating a pool connected to rethinkdb.dev.azk.io:32776
Draining the pool connected to rethinkdb.dev.azk.io:32776
npm info lifecycle r3stack@1.0.0-alpha~postbuild:db: r3stack@1.0.0-alpha
npm info ok
root@f071e1d2fc30:/azk/r3stack# npm run build:client
npm info it worked if it ends with ok
npm info using npm@3.3.12
npm info using node@v5.2.0
npm info lifecycle r3stack@1.0.0-alpha~prebuild:client: r3stack@1.0.0-alpha
npm info lifecycle r3stack@1.0.0-alpha~build:client: r3stack@1.0.0-alpha

> r3stack@1.0.0-alpha build:client /azk/r3stack
> NODE_ENV=production webpack --colors --config ./webpack/prod.babel.js

Hash: a19f19da1b055f4aab9a
Version: webpack 2.0.2-beta
Time: 36649ms
                               Asset     Size  Chunks             Chunk Names
37681ed619fcde1be52da659ee7288ff.jpg   243 kB          [emitted]
           0_bc60c6ad279a86d47deb.js  27.6 kB    0, 4  [emitted]
           1_be618267abb21d5f8b9f.js  36.9 kB    1, 4  [emitted]
           2_9077508edbcc1c86d2c1.js   138 kB    2, 4  [emitted]
           3_52028c45d862583d7bbb.js   459 kB    3, 4  [emitted]
    manifest_dbf84eff6deaa906b2ab.js  1.14 kB       4  [emitted]  manifest
         app_f5d1b117bacfd3a66d4f.js   499 kB    5, 4  [emitted]  app
      vendor_28a30fcb97bda3f33e1b.js   504 kB    6, 4  [emitted]  vendor
   [2] multi app 40 bytes {5} [built]
   [3] multi vendor 52 bytes {6} [built]
    + 1119 hidden modules
npm info lifecycle r3stack@1.0.0-alpha~postbuild:client: r3stack@1.0.0-alpha
npm info ok
root@f071e1d2fc30:/azk/r3stack# npm run build:server
npm info it worked if it ends with ok
npm info using npm@3.3.12
npm info using node@v5.2.0
npm info lifecycle r3stack@1.0.0-alpha~prebuild:server: r3stack@1.0.0-alpha
npm info lifecycle r3stack@1.0.0-alpha~build:server: r3stack@1.0.0-alpha

> r3stack@1.0.0-alpha build:server /azk/r3stack
> NODE_ENV=production webpack --colors --config ./webpack/server.babel.js

Hash: b82c433bddb8c239db63
Version: webpack 2.0.2-beta
Time: 24081ms
                               Asset     Size  Chunks             Chunk Names
37681ed619fcde1be52da659ee7288ff.jpg   243 kB          [emitted]
                        prerender.js   987 kB       0  [emitted]  prerender
                       prerender.css  31.1 kB       0  [emitted]  prerender
    + 779 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
Child extract-text-webpack-plugin:
        + 3 hidden modules
Child extract-text-webpack-plugin:
        + 5 hidden modules
Child extract-text-webpack-plugin:
        + 3 hidden modules
Child extract-text-webpack-plugin:
        + 3 hidden modules
Child extract-text-webpack-plugin:
        + 3 hidden modules
Child extract-text-webpack-plugin:
        + 3 hidden modules
npm info lifecycle r3stack@1.0.0-alpha~postbuild:server: r3stack@1.0.0-alpha
npm info ok
root@f071e1d2fc30:/azk/r3stack# npm run prod
npm info it worked if it ends with ok
npm info using npm@3.3.12
npm info using node@v5.2.0
npm info lifecycle r3stack@1.0.0-alpha~preprod: r3stack@1.0.0-alpha
npm info lifecycle r3stack@1.0.0-alpha~prod: r3stack@1.0.0-alpha

> r3stack@1.0.0-alpha prod /azk/r3stack
> NODE_ENV=production node ./src/server/server.babel.js

   [Busy] Launching SocketCluster
   >> Broker PID: 173
1453781051150 - Origin: Broker (PID 173)
   [Error] Error: listen EPERM /azk/r3stack/socketcluster/Meatier_4fef3560d7/b0
    at Object.exports._errnoException (util.js:856:11)
    at exports._exceptionWithHostPort (util.js:879:20)
    at Server._listen2 (net.js:1225:19)
    at listen (net.js:1274:10)
    at Server.listen (net.js:1364:5)
    at EventEmitter.self.listen (/azk/r3stack/node_modules/ncom/index.js:139:19)
    at Object.<anonymous> (/azk/r3stack/node_modules/sc-broker/server.js:505:10)
    at Module._compile (module.js:399:26)
    at Object.Module._extensions..js (module.js:406:10)
    at Module.load (module.js:345:32)

Ok at this point everything has been smoothed out but socketcluter... I'm looking into it, please give me few minutes.

bartekus commented 8 years ago

At this point I'll close the ticket as I'm very confident that all the issues as related to azk have been addressed at this point and for that I'd like to deeply and sincerely thank you guys! You are doing amazing work and I'm excited to make it part of the r3stack!

Cheers to our future cooperation!

Thank you again!

gullitmiranda commented 8 years ago

you are welcome. If you need any other help may open issues or even call us in https://gitter.im/azukiapp/azk.