Cafu Engine Startup Error
Here are the Stack-Logs of our Remote Control Work.
- Attachments
-
- CallStack1.txt
- (1.42KiB)Downloaded 560 times
-
- CallStack2.txt
- (3KiB)Downloaded 544 times
Re: Cafu Engine Startup Error
Thanks for your help and for uploading the files!
For the records, I've filed this as ticket #53 at http://trac.cafu.de/ticket/53
CallStack1.txt above has been produced without catching exceptions first chance,
CallStack2.txt had for this purpose C++ EH exceptions enabled in the Event Filter dialog of WinDbg.
I'll provide a fix asap.
For the records, I've filed this as ticket #53 at http://trac.cafu.de/ticket/53
CallStack1.txt above has been produced without catching exceptions first chance,
CallStack2.txt had for this purpose C++ EH exceptions enabled in the Event Filter dialog of WinDbg.
I'll provide a fix asap.
Best regards,
Carsten
Carsten
Re: Cafu Engine Startup Error
Ok, ticket #53 is fixed now, see r179 for details.
If you use Subversion, just update and recompile.
Otherwise, please download the three modified files from the r179 link above, and copy them over the files in your source code tree.
Note that you should now see a proper, specific error message, not the crash as before.
That is, you should see (do you?) something like:
However, the root of the problem is (probably) still unresolved - the OS doesn't let Cafu have a UDP socket on that port.
I would suspect that most likely some (personal) firewall is active that is configured to block any UDP (as opposed to TCP) connection attempts...
If you use Subversion, just update and recompile.
Otherwise, please download the three modified files from the r179 link above, and copy them over the files in your source code tree.
Note that you should now see a proper, specific error message, not the crash as before.
That is, you should see (do you?) something like:
Code: Select all
class ServerT::InitErrorT
Unable to obtain UDP socket on port 30000.
I would suspect that most likely some (personal) firewall is active that is configured to block any UDP (as opposed to TCP) connection attempts...
Best regards,
Carsten
Carsten
Re: Cafu Engine Startup Error
ok, now I see the error.
For testing, I have deactivate my AntiVir and my Firewall(Windows Firewall), and I have sets the udp and tcp port 30000 on my router "Fritzbox".
No effects. The error is still there.
For testing, I have deactivate my AntiVir and my Firewall(Windows Firewall), and I have sets the udp and tcp port 30000 on my router "Fritzbox".
No effects. The error is still there.
Re: Cafu Engine Startup Error
Hi,
thanks for the feed-back. No need to modify the FritzBox, the problem is on the local system (but it's good to turn off the personal firewalls, at least for testing).
I've created a version of Libs/Network/Network.cpp with additional logging: Please extract this file, overwrite the existing Libs/Network/Network.cpp with it, recompile, and try again (with -log console.txt as before), then post the result of console.txt here (the lines beginning with [Dev] are enough).
It should mention one of the error codes listed at http://msdn.microsoft.com/en-us/library ... 85%29.aspx
thanks for the feed-back. No need to modify the FritzBox, the problem is on the local system (but it's good to turn off the personal firewalls, at least for testing).
I've created a version of Libs/Network/Network.cpp with additional logging: Please extract this file, overwrite the existing Libs/Network/Network.cpp with it, recompile, and try again (with -log console.txt as before), then post the result of console.txt here (the lines beginning with [Dev] are enough).
It should mention one of the error codes listed at http://msdn.microsoft.com/en-us/library ... 85%29.aspx
Best regards,
Carsten
Carsten
Re: Cafu Engine Startup Error
This are both Errors I got:
Code: Select all
[Dev] WinSockT::GetUDPSocket(131): WSAGetLastError() == 0
[Dev] WinSockT::GetUDPSocket(146): WSAGetLastError() == 10048
Re: Cafu Engine Startup Error
Well, according to Microsoft documentation:
?
What does console command output?
Use to see the related program as well (may require admin rights).
Have you tried using another port, e.g.WSAEADDRINUSE 10048 - Address already in use.
Typically, only one usage of each socket address (protocol/IP address/port) is permitted. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket, or a socket that was not closed properly, or one that is still in the process of closing. For server applications that need to bind multiple sockets to the same port number, consider using setsockopt (SO_REUSEADDR). Client applications usually need not call bind at all—connect chooses an unused port automatically. When bind is called with a wildcard address (involving ADDR_ANY), a WSAEADDRINUSE error could be delayed until the specific address is committed. This could happen with a call to another function later, including connect, listen, WSAConnect, or WSAJoinLeaf.
Code: Select all
Cafu -svPort 12345
What does console command
Code: Select all
netstat -a
Use
Code: Select all
netstat -ab
Best regards,
Carsten
Carsten
Re: Cafu Engine Startup Error
So, now the problem is solved!
I searched with "netstat -ab" in the Comand-Line the programm which the UDP-Socket 30000 reserves.
My result: 1&1 Softphone
So I stoped the programm and now there is no error if I start up the Cafu Engine.
So you should fix the problem by using a function that search for a free port to use.
Thank you!
I searched with "netstat -ab" in the Comand-Line the programm which the UDP-Socket 30000 reserves.
My result: 1&1 Softphone
So I stoped the programm and now there is no error if I start up the Cafu Engine.
So you should fix the problem by using a function that search for a free port to use.
Thank you!
Re: Cafu Engine Startup Error
Ahhh! That's good to know, thanks!!rtdds wrote:So, now the problem is solved!
I searched with "netstat -ab" in the Comand-Line the programm which the UDP-Socket 30000 reserves.
My result: 1&1 Softphone
So I stoped the programm and now there is no error if I start up the Cafu Engine.
Sorry, but no, that is not the proper way:So you should fix the problem by using a function that search for a free port to use.
- A server must connect to a "fixed" port that is known to the clients in advance - otherwise how are they supposed to connect? (Unless the server port is explicitly communicated to the clients beside the servers IP address.)
- For clients, the matter is different. The Cafu client currently asks for a fixed port as well, but it's also possible to have the OS pick a suitable one. You can achieve this already by using the command-line paramter (Join a map and use netstat -a to check...)
Code: Select all
-clPort 0
This can also be set permanently by enteringinto file config.lua (near the end of the file).Code: Select all
dlg_clPortNr = 0;
Best regards,
Carsten
Carsten
Re: Cafu Engine Startup Error
LOL. The 'Unhandled exception' error on the loading screen is simply produced by opening more than one instance of Ca3De.
Just close them (maybe you'll need to use the Task Manager).
It happened to me before.
Just close them (maybe you'll need to use the Task Manager).
It happened to me before.
Re: Cafu Engine Startup Error
Thanks for mentioning this!BRabbit wrote:The 'Unhandled exception' error on the loading screen is simply produced by opening more than one instance of Ca3De.
I've opened a new ticket for now (http://trac.cafu.de/ticket/54) and will look into it later.
Best regards,
Carsten
Carsten
Re: Cafu Engine Startup Error
Anyway, i don't think is a problem of Cafu itself, in fact, I have previously developed a LAN chat application, and it wasn't possible to emulate a LAN in a single computer by running two instances (it also used a client-server architecture, the program itself was a server and a client, when there was not server, it created it) of the program (I think because the port is already used). So everytime I wanted to debug the program, I had to open it in 2+ computers...
Re: Cafu Engine Startup Error
Cafu can do that. I've done it before (some of the screenshots were made this way, running Cafu multiple times on the same machine helps getting a sufficient number of players into the game, no matter how late the time of day ).BRabbit wrote:Anyway, i don't think is a problem of Cafu itself
The current problems are really only related to port collisions, somewhat of a leftover of the changes (that were a huge benefit otherwise) we did when porting Cafu to 64-bit Windows.
Best regards,
Carsten
Carsten
Who is online
Users browsing this forum: No registered users and 12 guests