View Single Post
  #8  
Unread 15th October, 2007, 09:25 AM
Art_illery Art_illery is offline
Killing Spree
 
Join Date: Oct 2007
Posts: 24
Default

Same here on Gentoo Linux 2007.0 64 Bit OS.

I already sent logs of the Process to EPIC staff yesterday. This is pretty annoying. The Process itself runs on neatly, and when you send the Process a SIGTERM, it shuts down itself properly. But every client gets booted.

Here are my logs from the last Hang-up.

NetComeGo: Open TheWorld 82.93.192.253:49361
Log: Client netspeed is 10000
Log: UTPlayerController_32 got player TcpipConnection_22
Warning: Login failed: Server is already at capacity.
NetComeGo: Open TheWorld 82.93.192.253:49361
NetComeGo: Close TcpipConnection_19 69.112.94.120:49688
NetComeGo: Open TheWorld 81.15.33.174:20946
Log: Client netspeed is 10000
NetComeGo: Open TheWorld 81.15.33.174:20946
NetComeGo: Close TcpipConnection_21 217.87.99.109:4292
NetComeGo: Close TcpipConnection_16 84.153.42.234:3117
NetComeGo: Close TcpipConnection_20 89.80.28.9:2270
NetComeGo: Close TcpipConnection_2 217.237.107.224:4363
NetComeGo: Close TcpipConnection_6 87.175.198.74:33253
NetComeGo: Close TcpipConnection_3 89.244.240.193:49276
NetComeGo: Close TcpipConnection_13 91.64.108.231:33000
NetComeGo: Close TcpipConnection_22 86.216.25.140:1083
NetComeGo: Close TcpipConnection_1 84.57.41.61:3484
NetComeGo: Close TcpipConnection_12 91.64.108.190:49350
NetComeGo: Close TcpipConnection_15 87.171.128.211:62977
NetComeGo: Close TcpipConnection_0 80.130.46.151:28862
NetComeGo: Close TcpipConnection_4 82.93.238.161:58112
ScriptLog: LiftCenter_2 drifted!!!
NetComeGo: Close TcpipConnection_24 82.93.192.253:49361
NetComeGo: Close TcpipConnection_26 81.15.33.174:20946
Log: appRequestExit(0)

Success - 0 error(s), 0 warning(s)

Execution of commandlet took: 2450.80 seconds
Exit: Preparing to exit.
Exit: Game engine shut down
Exit: closesocket error (11)
Exit: UTcpNetDriver shut down
Exit: Object subsystem successfully closed.
Log: Shutting down FaceFX...
Log: FaceFX shutdown.
Exit: Exiting.
Exit: Name subsystem shutting down

---------------------------------------------------------------------------------------------------------------------------------
The only odd thing i can see, is the error message,when the Serverprocess shuts down "Exit: closesocket error (11)".

Ingame on the CLient side the hang-up would announce itself by some serious lags (teleporting-style) for 2-3 Seconds in which everybody lags around alot, but still able to fire or move, then suddenly, firing your weapons won´t be shown, and that´s it then.
Only way to remedy is to kill the Process and restart the Server.

On my System, we always play one map, which runs fine, then after a mapswitch 2-5 minutes into the next map, KAzoom --> Hang-up.

Last edited by Art_illery : 15th October, 2007 at 09:30 AM.
Reply With Quote