Application 'appname' failed to start (port 8080 not available) on open shift node app

Question

I have written a node restify server in coffee and I can't seem to get it running.

While deploying I get the following error:

Waiting for application port (8080) become available ...

after which I do get the following error

Application 'appname' failed to start (port 8080 not available)

If coffeescript seems to be the problem is there a work around it. I would not want to change back to js.

My server code is:

restify = require 'restify'
Bunyan = require 'bunyan'

server = restify.createServer
    name: 'APPNAME'
    version: '0.0.1'
    log: Bunyan.createLogger
        name: 'api'
        serializers: 
            req: ()->
                return "bad"

# Usercontroller.access calls a function to process the request
server.post '/user/access', UserController.access

server = create.createServer()
server.listen server_port, ->
    console.log "Http server listening on #{server_port}"
    require('./document')(server.router.mounts, 'restify')
    return

Can we see the code you are using to start your http server? — Preston Van Loon, Jul 11 '15 at 15:59
I believe you can't specify what port you want to use on openshift. try using `process.env.OPENSHIFT_NODEJS_PORT` as your port. — dmlittle, Jul 11 '15 at 16:55
change the port and the ip address to the following but still shows the above error. `server_port = process.env.OPENSHIFT_NODEJS_PORT || 8080 server_ip_address = process.env.OPENSHIFT_NODEJS_IP || '127.0.0.1' ` — philip_nunoo, Jul 11 '15 at 17:23
@dmlittle i've also tried adding the node package cloud-env so i could `config = require 'cloud-env' ` and using `server.listen config.PORT, config.IP, ()->' but still getting the same error — philip_nunoo, Jul 11 '15 at 18:01
the fact that you're getting the same error tells me that `process.env.OPENSHIFT_NODEJS_PORT` is not defined and therefore relying on 8080. try `console.log process.env` to check where openshift is setting the port — dmlittle, Jul 11 '15 at 18:04

score 29 · Answer 1 · edited Feb 27 '16 at 22:23

The very first step that you need to check is look at the log under ~/app-root/logs/nodejs.log

In my case there was no issue with package or any kind of access. The only information that I have got in log is:

Error: listen EACCES at errnoException (net.js:905:11) at Server._listen2 (net.js:1024:19)

If you cannot find any reason apart from the front console says that it is unable to access 8080 then make sure that you have specified IP ADDRESS along with PORT Number.

This is how I have fixed it.

var express = require('express');
var app = express();
var http = require('http');

app.set('port', process.env.OPENSHIFT_NODEJS_PORT || process.env.PORT || 3002);
app.set('ip', process.env.OPENSHIFT_NODEJS_IP || "127.0.0.1");


http.createServer(app).listen(app.get('port') ,app.get('ip'), function () {
    console.log("✔ Express server listening at %s:%d ", app.get('ip'),app.get('port'));
    server();
});

As stated the app.get('ip') is very important when listening. Otherwise, openshift is unable to start your application.

UPDATED:

How to get into log directory:

SSH into your gear with the command rhc ssh
Once you are logged in type cd $OPENSHIFT_LOG_DIR

There you have logs files stored by Openshift environment.

Good call on `~/app-root/logs/nodejs.log`. It hadn't occurred to me that error logs might log errors. :-p — twiz, Aug 22 '15 at 23:52
this didn't work, is there an updated answer, and I can't view the logs either, it says the directory doesn't exist — Rockstar5645, Nov 15 '15 at 06:57

score 6 · Answer 2 · answered Jul 21 '15 at 08:46

6

It can be for a number of reasons. If nodejs does not start correctly, the PaaS seems to be trying to continuously start it. It either creates a collision for the port or the error has nothing to do with the problem itself. In my case there was a dependency missing. The best way to solve your problem is to ssh in the app container and watch the log file: tail -f ~/app-root/logs/nodejs.log

answered Jul 21 '15 at 08:46

Mihai

61
2

This helped me. The log told me exactly what was wrong. Thanks! +1 for including the *nix command for viewing the log, too – Alex311 Sep 17 '15 at 02:14

score 1 · Answer 3 · answered Jul 12 '15 at 17:44

1

solved the issue by setting my mongo db username and password

answered Jul 12 '15 at 17:44

philip_nunoo

920
3
10
21

1

Where did you do that? – Swami Mar 23 '16 at 21:25

Lorna Kelly · Answer 4 · 2015-11-27T18:27:45.497

1

I got the same error and it was to do with the branch I was pointing to on github.

Master was my main branch (first one created) and when I pointed to that it built but I would get the error if I pointed to any other branch.

edited Nov 27 '15 at 18:27

answered Nov 27 '15 at 18:19

Lorna Kelly

99
2
12

score 1 · Answer 5 · edited May 23 '17 at 12:09

Node App on Openshift is a 2 Step process:

Create entry in package.json to how to launch your server(entry point to app):
```
"scripts": {
"start": "node server.js"
},
"main": "server.js"
```

Use OPENSHIFT environment variables to get IP and PORT:

process.env.OPENSHIFT_NODEJS_PORT
process.env.OPENSHIFT_NODEJS_IP

For more details check: OpenShift: "Failed to execute control start" on node application

score 1 · Answer 6 · edited May 23 '17 at 11:46

`rhc app create ... --from-code ...` and getting 8080 not available?

.

Just like Mihai explained in his answer the (port 8080 not available) doesn't need to be related to how you set up your ports - hence it may occur even if you're using the process.env.OPENSHIFT_NODEJS_PORT and process.env.OPENSHIFT_NODEJS_IP correctly.

An advice to look at the ~/app-root/logs/nodejs.log is helping a lot but what if the error happens on rhc app create ... --from-code ...? The app will not get created hence you can't ssh and look at nodejs.log.

Try to push your app in a limited version - comment out as much code as you can.

For me it worked to start with only the express app initialising and listening. Then, once I had the openshift app created, I've been uncommenting code bit by bit, pushing and checking the nodejs.log file.

This way I found that my mongoDb name was "APPNAME_"+process.env.NODE_ENV while openshift created mongoDb database called only APPNAME

.

Apologies for not directly answering the question, but the 8080 not available seems to be caused by all sorts of setup, maybe this will help someone.

score 1 · Answer 7 · answered Jun 07 '16 at 17:12

1

If you using express: app.listen(process.env.OPENSHIFT_NODEJS_PORT, process.env.OPENSHIFT_NODEJS_IP);

Or:

var port = process.env.OPENSHIFT_NODEJS_PORT;
var ip = process.env.OPENSHIFT_NODEJS_IP;
app.listen(port, ip);

answered Jun 07 '16 at 17:12

oxixes

101
1
10

score 0 · Answer 8 · answered Feb 27 '16 at 23:00

In my case I'm getting following error checked using rhc ssh as suggested above.

Unhandled rejection Error: getaddrinfo ENOTFOUND
    at errnoException (dns.js:37:11)
    at Object.onanswer [as oncomplete] (dns.js:124:16)

I get rid of my problem by setting the

mongo_url = process.env.OPENSHIFT_MONGODB_DB_URL;

to mongoose uri.I was trying with following but

mongo_url = "mongodb://admin:pass@$OPENSHIFT_MONGODB_DB_HOST:$OPENSHIFT_MONGODB_DB_PORT/mydbname"

this was not working.

Hope this helps someone.

score 0 · Answer 9 · answered Jun 25 '16 at 13:34

The best way to solve it is checking your logs folder. SSH to your server, find the nodejs.log file, you can use cat nodejs.log to see its content.

The reason could be:

Syntax error in other files
Missing Port environment variable
Missing IP environment variable (These 2 last stated on other answers)

Even though it says "Port 8080 not available", the error could be in a file that couldn't be executed properly, thus you should check the recent changes or just check directly the log and find where the error is.

Application 'appname' failed to start (port 8080 not available) on open shift node app

9 Answers9

`rhc app create ... --from-code ...` and getting 8080 not available?

Linked

Application 'appname' failed to start (port 8080 not available) on open shift node app

9 Answers9

rhc app create ... --from-code ... and getting 8080 not available?

Linked

`rhc app create ... --from-code ...` and getting 8080 not available?