Bug 122594 - Couldn't create bound network socket
Couldn't create bound network socket
Product: Fedora
Classification: Fedora
Component: Maelstrom (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Karsten Hopp
Depends On:
  Show dependency treegraph
Reported: 2004-05-06 00:46 EDT by Andre Robatino
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-20 09:45:14 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andre Robatino 2004-05-06 00:46:06 EDT
Description of problem:
  Unable to start Maelstrom.  Running it from the command line gives
the error message "Couldn't create bound network socket".

Version-Release number of selected component (if applicable):

How reproducible:
Sometimes (usually works, but when it doesn't, it doesn't work
reproducibly for the duration of the session.  Rebooting fixes it.) 
Presumably the resource is either used up, or Maelstrom makes false
assumptions which limit access to it.

Steps to Reproduce:
1.  Try to run Maelstrom from the command line.
Actual results:
  Error message "Couldn't create bound network socket".

Expected results:
  Maelstrom should run.

Additional info:
  The last few lines from "strace -f Maelstrom" (I saved the whole
thing to a file if that's needed):

open("/home/andre/.Maelstrom-data", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0664, st_size=35, ...}) = 0
0) = 0xbf537000
read(3, "MAEL3\4\23\0\0\0 \0\0\0\21\1\0\0\23\1\0\0\24\1\0\0\t\0"...,
4096) = 35
close(3)                                = 0
munmap(0xbf537000, 4096)                = 0
bind(3, {sa_family=AF_INET, sin_port=htons(44718),
sin_addr=inet_addr("")}, 16) = -1 EADDRINUSE (Address already
in use)
close(3)                                = 0
write(2, "Couldn\'t create bound network so"..., 36Couldn't create
bound network socket) = 36
exit_group(1)                           = ?
Comment 1 Bill Nottingham 2004-05-21 13:47:26 EDT
What's on port 44718 on your system when this fails?
Comment 2 Andre Robatino 2004-05-23 03:21:00 EDT
[andre@localhost andre]$ /usr/sbin/lsof|grep 44718
esd       3465 andre    3u  IPv4      50161                UDP *:44718

  This time it happened immediately after quitting Maelstrom.  The
next time I tried to start it, it was hosed.  I've upgraded to FC2
since creating this bug report so it's still there.  After I killed
the esd process, Maelstrom works again.  It appears that after
exiting, the esd process is supposed to die but sometimes it doesn't.
Comment 3 Karsten Hopp 2004-12-20 09:45:14 EST
Maelstrom uses a hardcoded portnumber which can be already in use when
the game is started. There is no easy way to fix this behaviour because
the clients of the other players (in a network game) have no way of
autodetecting the portnumer of your Maelstrom client if you change the
sources to use the next available free port number.
Btw: The same will happen if any other process takes hold of port 44718
befor Maelstrom starts up, that's not limited to esd. It's expected
behaviour as long as Maelstrom is using a fixed portnumber.
Comment 4 Andre Robatino 2004-12-20 16:34:58 EST
  Is the esd process always supposed to automatically exit when
Maelstrom does?  If so, then that's the core problem here, and this
bug should be reassigned to esound (or whatever the appropriate
package is) instead of just closed.

Note You need to log in before you can comment on or make changes to this bug.