Note that there are some explanatory texts on larger screens.

plurals
  1. POOpenshift + Meteor = listen EACCES?
    text
    copied!<p>I deployed Meteor.js on a Node 0.6 + Mongo 2.2 Openshift cartridge with a custom Node 0.8.24 installed in the data dir (sort of like <a href="https://www.openshift.com/content/add-meteorjs-support#comment-25174" rel="nofollow">this tutorial</a>).</p> <p>I do set the right ports before calling the app. My code in <code>server.js</code> looks like that:</p> <pre><code>// Setup env process.env.ROOT_URL = "http://" + (process.env.OPENSHIFT_APP_DNS || "localhost"); process.env.MONGO_URL = (process.env.OPENSHIFT_MONGODB_DB_URL + process.env.OPENSHIFT_APP_NAME) || "mongodb://localhost:27017/"; process.env.PORT = process.env.OPENSHIFT_NODEJS_PORT || 8000; process.env.IP = process.env.OPENSHIFT_NODEJS_IP || '0.0.0.0'; // Show connection details on startup console.log("MONGO_URL IS: " + process.env.MONGO_URL); console.log("ROOT_URL IS: " + process.env.ROOT_URL); console.log("PORT: " + process.env.PORT); console.log("IP: " + process.env.IP); require(require('path').join(__dirname, 'main.js')); </code></pre> <p>Then, when I <code>rhc app restart myappname</code> the app, I get:</p> <pre><code>&gt; node server.js MONGO_URL IS: mongodb://&lt;login&gt;:&lt;pass&gt;@127.5.x.x:27017/&lt;myapp&gt; ROOT_URL IS: http://&lt;myappname&gt;-&lt;mydomain&gt;.rhcloud.com PORT: 8080 IP: 127.5.x.x events.js:71 throw arguments[1]; // Unhandled 'error' event ^ Error: listen EACCES at errnoException (net.js:770:11) at Server._listen2 (net.js:893:19) at listen (net.js:932:10) at Server.listen (net.js:1006:9) at dns.js:72:18 at process.startup.processNextTick.process._tickCallback (node.js:245:9) npm info &lt;mydomain&gt;@0.0.1 Failed to exec start script npm ERR! weird error 1 npm ERR! not ok code 0 </code></pre> <p><code>main.js</code> is he regular entry point for my Meteor app.</p> <p>The env settings look like the right ones. Why do I keep getting this <code>EACCESS</code>?</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload