[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #20, bug #24249 (project freeciv): > I wonder if it tries to bind the exactly same thing twice and latter attempt fails because it already got it itself. We've debugged this with chrisk, and this seems to be the case. First it success in binding "127.0.0.1:5557" and then it

[Freeciv-Dev] [bug #24249] client cannot start server

Update of bug #24249 (project freeciv): Category:None => general Status:None => In Progress ___ Follow-up Comment #21: I don't think

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #22, bug #24249 (project freeciv): The patch does not work for me. No change for the matter. OTOH, with the patched revision, I just got a "connection rejected" ("Verbindungsaufbau abgelehnt") in the client, trying to connect to a seperately started server. None of the programs

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #15, bug #24249 (project freeciv): The socket ist opened in sernet.c:1172 (succesfully, can see with netstat) and closed shortly after in 1189/1191. ___ Reply to this item at:

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #18, bug #24249 (project freeciv): So it says that the list size is 2: > bind failure: Address already in use (2 failed) ...but lists only one: > Host: 127.0.0.1, Port: 5557 1) Wasn't there even "Last message repeated 2 times" after this? 2) Are you sure you have a build where

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #17, bug #24249 (project freeciv): > > closed shortly after in 1189/1191. > That's exactly why I would have liked to see the list of all (according to your log: 2) addresses as logged from line 1217. Can you make that LOG_NORMAL for your test, if you can't get the LOG_DEBUG

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #19, bug #24249 (project freeciv): > 1) Wasn't there even "Last message repeated 2 times" after this? no > 2) Are you sure you have a build where you changed LOG_DEBUG to LOG_NORMAL in use? One of them is logged on LOG_NORMAL level outside the loop even without any changes to

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #14, bug #24249 (project freeciv): 1. used revision 31289 with improved logging 2. my compile options: --enable-svnrev --enable-gitrev --enable-xml-registry --with-followtag --enable-dev-save-compat=yes --with-readline

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #16, bug #24249 (project freeciv): > closed shortly after in 1189/1191. That's exactly why I would have liked to see the list of all (according to your log: 2) addresses as logged from line 1217. Can you make that LOG_NORMAL for your test, if you can't get the LOG_DEBUG level

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #11, bug #24249 (project freeciv): Ok, for a very short tine, a single run of ps aux, I see chris28778 0.0 0.1 44012 4024 pts/1R+ 21:58 0:00 freeciv-server -p 5557 --bind localhost -q 1 -e --saves ~/.freeciv/saves --scenarios ~/.freeciv/scenarios -A none

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #12, bug #24249 (project freeciv): I recompiled w/o --enable-ipv6=no and here is the relevant portion of the log: 4: in set_client_page() [update_queue.c::483]: Requested page: PAGE_MAIN. 4: in genhash_new_nbuckets() [genhash.c::214]: New genhash table with 29 buckets 4: in

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #10, bug #24249 (project freeciv): Looks like the server never comes up. I kinda supervised ps and netstat $ while true ; do ps aux ; done | grep freeciv | grep -v grep $ netstat -tanepc and started $ LANG= freeciv-gtk3 --debug 4 --log log1 but got no related level 4

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #13, bug #24249 (project freeciv): This is a very wild guess of mine since I followed this portion of code in passing years I think the server THINKS it cannot use the socket because this piece of information is inherited from the exec call. chrisk

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #9, bug #24249 (project freeciv): After logging that "bind failed: Address already in use", server gives LOG_DEBUG level output about all the addresses in the list of addresses to handle. Can you get that with something like freeciv-server --bind localhost -d 4:netintf.c where

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #7, bug #24249 (project freeciv): don't think so I doublechecked when I read the message and the port was not in use, nor was freeciv-server running. ___ Reply to this item at:

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #1, bug #24249 (project freeciv): maybe ipv6? ./configure --enable-dev-save-compat=yes --enable-svnrev --enable-xml-registry --enable-debug=yes --enable-gprof --enable-freeciv-manual=html --with-readline --with-followtag --enable-mapimg=no --enable-sdl-mixer --enable-ipv6=no

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #3, bug #24249 (project freeciv): Sounds similar to bug #23392. ___ Reply to this item at: ___ Message sent via/by Gna! http://gna.org/

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #5, bug #24249 (project freeciv): Nevermind. It wouldn't give this error about program already running in that port: > 0: bind failed: Address already in use It's one of 1) Client fails to detect that port is already in use 2) Client itself fails to free the port (quickly

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #6, bug #24249 (project freeciv): > Just recording a thought here: Maybe "localhost" gets resolved > as IPv6 address, which then is not supported by freeciv. > Can you test with IPv6 enabled build? the host maybe ipv6 capable, but the local net is all ipv4 and the nameserver

[Freeciv-Dev] [bug #24249] client cannot start server

Update of bug #24249 (project freeciv): Release: trunk => trunk r31265 ___ Reply to this item at: ___ Message

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #4, bug #24249 (project freeciv): > --enable-ipv6=no + > if I replace --bind localhost with --bind 127.0.0.1 Just recording a thought here: Maybe "localhost" gets resolved as IPv6 address, which then is not supported by freeciv. Can you test with IPv6 enabled build?

[Freeciv-Dev] [bug #24249] client cannot start server

Follow-up Comment #8, bug #24249 (project freeciv): For the record: IPv4-only freeciv usually means nothing more than not handling the other half of the network stack, having it's own security implications. In most case I would go by the default given by 'configure' - enable IPv6 support if