New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError: Cannot read property 'getsockname' of undefined #3

Open
cyent opened this Issue Sep 2, 2014 · 0 comments

Comments

Projects
None yet
1 participant
@cyent

cyent commented Sep 2, 2014

Hi,

OS:RHEL6.5 x64
kernel: 2.6.32-431.el6.x86_64
docker version:1.1.2


docker run -i -t -v /var/run/docker.sock:/docker.sock shipyard/deploy setup

Using latest tag for Shipyard
This may take a moment while the Shipyard images are pulled...
Starting Redis...
Starting App Router...
Starting Load Balancer...
Starting DB...
Starting Shipyard

Shipyard Stack Deployed

You should be able to login with admin:shipyard at http://:8000
You will also need to setup and register the Shipyard Agent. See http://github.com/shipyard/shipyard-agent for details.


Then, I run docker logs shipyard_router, report below errors without stop!

net.js:943
if (port && handle.getsockname && port != handle.getsockname().port) {
if (port && handle.getsockname && port != handle.getsockname().port) {
^
^
TypeError: Cannot read property 'getsockname' of undefined
at net.js:943:23
at Object.cluster._getServer as 3968:2
at handleResponse (cluster.js:149:41)
at respond (cluster.js:170:5)
at handleMessage (cluster.js:180:5)
at process.EventEmitter.emit (events.js:126:20)
at handleMessage (child_process.js:270:12)
at Pipe.channel.onread (child_process.js:301:11)
TypeError: Cannot read property 'getsockname' of undefined
at net.js:943:23
at Object.cluster._getServer as 3969:2
at handleResponse (cluster.js:149:41)
at respond (cluster.js:170:5)
at handleMessage (cluster.js:180:5)
at process.EventEmitter.emit (events.js:126:20)
at handleMessage (child_process.js:270:12)
at Pipe.channel.onread (child_process.js:301:11)
2 Sep 06:47:04 - Worker died (pid: 8022, suicide: false, exitcode: 1). Spawning a new one.
2 Sep 06:47:04 - Worker died (pid: 8023, suicide: false, exitcode: 1). Spawning a new one.
2 Sep 06:47:04 - Loading config from /etc/shipyard_router.config.json

Why, and How to Solve it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment