Jump to content
The simFlight Network Forums

Wide Client Disconnects


Recommended Posts

I am running two computers for flight simming.

The first is a PC:

Windows XP SP3

AMD Athlon 64x2 Dual Core 5600+ 2.81 GHz

3.50 GB Ram

NVIDIA GeForce 8600GTS

The second is an iMac running Parallels

On the windows side I am running a legal copy of Windows XP SP3

The PC has FS9, FS Realtime, and Flight Environment

The Mac has JeppView, ASA for Weather, and Wide Client.

I also occasionally check the status of VATSIM using VATSpy on the Mac.

The problem is that Wide Client disconnects after a while during flights (an hour more or less) and the only way to re-establish communication is to reboot the Mac, which means I have to reload ASA and JeppView, etc.

The computers are both on a LAN with three other machines. They take their addresses automatically.

Here is the .ini file from Wide Client

[Config]

Port=8002

ServerName=valued-735da7ac

Protocol=TCP

Window=4,4,1686,828

Visible=Yes

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

MailslotTiming=2000,1000

PollInterval=2000

Port2=9002

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

WaitForNewData=500

MaxSendQ=100

OnMaxSendQ=Log

NewSendScanTime=50

Priority=3,1,2

; -----------------------------------------------

[user]

Log=Errors+

[GPSout]

Port=COM3

Speed=19200

Any suggestions you could offer would be greatly appreciated.

Link to comment
Share on other sites

The second is an iMac running Parallels

Not heard of Parallels. Does it emulate Windows completely?

The problem is that Wide Client disconnects after a while during flights (an hour more or less) and the only way to re-establish communication is to reboot the Mac, which means I have to reload ASA and JeppView, etc.

If it requires re-booting, there must be something wrong with the low level networking parts of whatever it is pretending to be Windows Winsock32. Application level programs like Wideclient do not disturb anything lower than their privilege level, so a simple restart is normally the most that is needed. In fact WideClient does its own restarts on timeputs, automatically.

With this occurring after a period of time, it also occurs to me that something on that system is leaking memory or other resources till finally things clog up. Do you have a performance monitor you can check this with, like the one in Windows Task Manager?

Try a process of elimination -- run only one application at a time on the client PC, see which one clobbers things.

Here is the .ini file from Wide Client

The INI file tells me nothing, unless you've been messing with it. The important information is recorded in Log files -- WideClient.log on the client and WideServer.log on the Server.

I also always need to know version numbers -- FSUIPC, WideServer and WideClient. If these are not the latest (check the announcements at the top of this Forum) please try those first.

Regards

Pete

Link to comment
Share on other sites

Thank you for the quick response.

Yes, Parallels is a program designed to complete emulate Windows on a Mac with an Intel chip.

I have FSUIPC v. 3.9.1.6

Wide Server v. 6.7.8.0

Just updated to Wide Client v. 6.7.8.6

I find that I have two Wide Client Logs and Two Wide Server logs. (Is that the problem?)

I hesitate to copy them here, because they are all very long, but the forum won't let me attach them. Here is the gist of them:

Wide Client log:

********* WideClient Log [version 6.784] Class=FS98MAIN *********

Date (dmy): 29/07/09, Time 21:35:08.437: Client name is JUSTINFRIEDA709

562 Opening GPSout port COM3, speed=19200 -- OK!

578 Attempting to connect now

609 Trying TCP/IP host "valued-735da7ac" port 8002 ...

609Okay, IP Address = 192.168.1.103

640 Connection made okay!

10828 New Client Application: "ASA_Exec" (Id=704)

2307515 Received shutdown offset code = ADBC

2307515 FS closing down (param=ADBC), disconnecting

2307515 ********* Interim performance summary *********

2307515 Total time connected so far = 2307 seconds

2307515 Reception maximum so far: 64 frames/sec, 6027 bytes/sec

2307515 Reception average whilst connected so far: 20 frames/sec, 324 bytes/sec

2307515 Transmission maximum so far: 7 frames/sec, 7209 bytes/sec

2307515 Transmission average whilst connected so far: 2 frames/sec, 879 bytes/sec

2307515 Max receive buffer = 2528, Max send depth = 5, Send frames lost = 0

2307515 **************** Individual client application activity ****************

2307515 Client 704 requests: 25207 (Ave 10/sec), Data: 4891164 bytes (2120/sec), Average 194 bytes/Process

2307515 ***********************************************

2307625 Received shutdown offset code = ADBC

2314156 Connection closed by server!

2314187 Attempting to connect now

2314187 Trying TCP/IP host "valued-735da7ac" port 8002 ...

2314187Okay, IP Address = 192.168.1.103

2315109 Error on client pre-Connection Select() [Error=10061] Connection refused

2315109 Ready to try connection again

2316125 Attempting to connect now

2374625 Trying TCP/IP host "valued-735da7ac" port 8002 ...

2374625Okay, IP Address = 192.168.1.103

2435015 Trying TCP/IP host "valued-735da7ac" port 8002 ...

2435015Okay, IP Address = 192.168.1.103

2495640 Trying TCP/IP host "valued-735da7ac" port 8002 ...

2495640Okay, IP Address = 192.168.1.103

2556078 Trying TCP/IP host "valued-735da7ac" port 8002 ...

2556078Okay, IP Address = 192.168.1.103

2616703 Trying TCP/IP host "valued-735da7ac" port 8002 ...

2616703Okay, IP Address = 192.168.1.103

2677328 Trying TCP/IP host "valued-735da7ac" port 8002 ...

2677328Okay, IP Address = 192.168.1.103

2737890 Trying TCP/IP host "valued-735da7ac" port 8002 ...

2737890Okay, IP Address = 192.168.1.103

2798453 Trying TCP/IP host "valued-735da7ac" port 8002 ...

2798453Okay, IP Address = 192.168.1.103

2859078 Trying TCP/IP host "valued-735da7ac" port 8002 ...

2859078Okay, IP Address = 192.168.1.103

2919578 Trying TCP/IP host "valued-735da7ac" port 8002 ...

2919578Okay, IP Address = 192.168.1.103

2980140 Trying TCP/IP host "valued-735da7ac" port 8002 ...

2980140Okay, IP Address = 192.168.1.103

3017078 Connection made okay!

3042281 Received shutdown offset code = ADBC

3042281 FS closing down (param=ADBC), disconnecting

3042281 ********* Interim performance summary *********

3042281 Total time connected so far = 2330 seconds

3042281 Reception maximum so far: 64 frames/sec, 6027 bytes/sec

3042281 Reception average whilst connected so far: 20 frames/sec, 322 bytes/sec

3042281 Transmission maximum so far: 7 frames/sec, 7209 bytes/sec

3042281 Transmission average whilst connected so far: 2 frames/sec, 871 bytes/sec

3042281 Max receive buffer = 2528, Max send depth = 5, Send frames lost = 0

Wide Client0 log

********* WideClient Log [version 6.784] Class=FS98MAIN *********

Date (dmy): 29/07/09, Time 21:27:02.875: Client name is JUSTINFRIEDA709

859 Opening GPSout port COM3, speed=19200 -- OK!

875 Attempting to connect now

3265 Trying TCP/IP host "valued-735da7ac" port 8002 ...

3265 Error on client gethostbyname() [Error=11001] Host not found

9125 ****** End of session performance summary ******

9125 Total time connected = 0 seconds

9125 Reception maximum: 0 frames/sec, 0 bytes/sec

9125 Transmission maximum: 0 frames/sec, 0 bytes/sec

9125 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

9125 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

Wide Server Log

********* WideServer.DLL Log [version 6.78] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 30/07/09, Time 11:54:52.406: Server name is VALUED-735DA7AC

290516 Initialising TCP/IP server

290531 Initialising IPX/SPX server

290531 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family

290531 Failed to start IPX/SPX Server

290531 Initialising UDP/IP server

290531 Broadcasting service every 1000 mSecs

301485 Restarting service due to total lack of use

301500 Failed to start IPX/SPX Server

428031 Closing down now ...

Memory managed: Offset records: 0 alloc, 0 free

Read buffer usage: 0 alloc, 0 free, max in session: 0

Write buffer usage: 0 alloc, 0 free, max in session: 0

Throughput maximum achieved: 0 frames/sec, 0 bytes/sec

Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec

********* Log file closed *********

Wide Server0 log:

********* WideServer.DLL Log [version 6.78] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 29/07/09, Time 22:24:26.921: Server name is VALUED-735DA7AC

63328 Initialising TCP/IP server

63359 Initialising IPX/SPX server

63359 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family

63359 Failed to start IPX/SPX Server

63359 Initialising UDP/IP server

63656 Incoming connection Accepted ok (skt=2720) TCP

63844 Connected to computer "JUSTINFRIEDA709" running WideClient version 6.784 (skt=2720) TCP

63844 Client capabilities: 04 (GPSout=Y) (skt=2720) TCP

64015 Broadcasting service every 1000 mSecs

94390 Close signalled to clients

95484 Closing down now ...

Memory managed: Offset records: 19 alloc, 19 free

Read buffer usage: 13 alloc, 13 free, max in session: 1

Write buffer usage: 97 alloc, 97 free, max in session: 1

Throughput maximum achieved: 8 frames/sec, 379 bytes/sec

Throughput average achieved for complete session: 0 frames/sec, 8 bytes/sec

Average receive rate from "JUSTINFRIEDA709": 0 frames/sec, 14 bytes/sec

********* Log file closed *********

As I said, I just updated the Wide Client app after your first response.

Thank you again.

Thank you again.

Link to comment
Share on other sites

I find that I have two Wide Client Logs and Two Wide Server logs. (Is that the problem?)

If you mean there's one with a numerical suffix as well as a simply named one, then, no, it is't a problem. The numbered one is the previous one. The logging system is designed to allow folks to restart after a problem and THEN still retrieve the details of the problem which caused them to restart.

I hesitate to copy them here, because they are all very long, but the forum won't let me attach them.

I think there's no problem attaching if you ZIP them, but embodying complete text files in a message is okay provided you bracket them using the "Code" button. that provides them with both a scroll bar for browsing and a "select all" facility so they can be grabbed and saved.

The first log shows no disconnection until you closed FS, or at least transmitted the close down signal, after 2307 seconds (38 minutes):

2307515 Received shutdown offset code = ADBC

2307515 FS closing down (param=ADBC), disconnecting

...

2307625 Received shutdown offset code = ADBC

2314156 Connection closed by server!

It then continually tried to reconnect, to a server which appears to have been closed (as the "closing down" indication confirmed, in fact):

2314187 Attempting to connect now

2314187 Trying TCP/IP host "valued-735da7ac" port 8002 ...

2314187Okay, IP Address = 192.168.1.103

2315109 Error on client pre-Connection Select() [Error=10061] Connection refused

2315109 Ready to try connection again

2316125 Attempting to connect now

until , 701 seconds (nearly 12 minutes!) later, it reconnects:

3017078 Connection made okay!

Only to be told, just 25 seconds later, that the server is shutting down again:

3042281 Received shutdown offset code = ADBC

3042281 FS closing down (param=ADBC), disconnecting

Your WideServer log, the one corresponding time-wise with the WideClient log I've just analysed, shows you only ran it for 428 secons (7 minutes)!

428031 Closing down now ...

Sorry, all these logs show is WideClient being told that the server is closing, and the Server log confirming it. You need to keep FS running if you want WideClient to stay connected to it.

Regards

Pete

Link to comment
Share on other sites

Pete,

These logs are from last night, when I started a flight from JFK to Halifax. About an hour into the flight, Wide Client disconnected and nothing I could do would get it reconnected until I rebooted the Mac computer, restarted JeppView and ASA, then restarted Wide client, which then reconnected to FS9 on the PC. The connection remained stable until I was parked at the gate, when I did shut down the FS9 App.

I guess the best thing to do is to do another flight, and send you the logs of the next disconnect.

I thank you for your patience, and the the great contribution that you make to my hobby.

Justin

Link to comment
Share on other sites

These logs are from last night, when I started a flight from JFK to Halifax. About an hour into the flight, Wide Client disconnected and nothing I could do would get it reconnected until I rebooted the Mac computer ...

The logs show none of that. These must be the wrong files -- though there are only ever two logs -- "WideClient.log" is the current one, and the other is the one before.

The complete time shown in the first is only 50 minutes, and that includes a 12 minute gap whilst the Server (WideServer) was closed, having specifically signalled a shutdown to the Client. 25 seconds after is reconnected it was closed again. The actual end of the log, showing WideClient closing, wasn't included, so I don't know how much longer you continued this cycle -- if your client's system clock is correct the log goes up to 22:26 on the 29th.

The older, saved log, is for a short session immediately before that one, from 21:27, only lasting 91 seconds. It never connected due to this error:

3265 Trying TCP/IP host "valued-735da7ac" port 8002 ...

3265 Error on client gethostbyname() [Error=11001] Host not found

meaning the Client PC had no idea how to find the IP address of "valued-735da7ac". You must have done something to correct that before re-running WideClient at 21:35.

... restarted JeppView and ASA, then restarted Wide client, which then reconnected to FS9 on the PC. The connection remained stable until I was parked at the gate, when I did shut down the FS9 App.

The fact that you have to re-boot the PC does really indicate something serious wrong with the Networking set up on that computer. I'd check it out more thoroughly if i were you. Maybe a re-install is called for.

Incidentally, coincidence, I've just read a message on the FSX Forum at AVSIM from a happy iMac user with WideFS running really well on it with lots of apps. "Right now, I'm typing this in Firefox on the Mac. Thunderbird is also open. XP is running with ASA, WideFS, FS Commander, FS Flightkeeper and Dreamweaver MX all open. On the FS PC I'm currently in the CS757 with FS Passengers, flying across China".

See http://forums1.avsim.net/index.php?showtopic=255641 , scroll down to the message from Dean_EGTC!

So it isn't the Mac per se. Something's wrong.

Sorry I can't tell anything from these logs as they don't seem to tie in. Whether full matching logs would help much I can't say -- but please, only the current logs -- ones actually called WideServer.log and WideClient.log, and only after both FS and the Client programs are closed down. Else we don't get the full picture.

If files are really too big -- and they certainly shouldn't be unless there's a lot going wrong (!) - ZIP them and send them as attachments to me at petedowson@btconnect.com. If you post them here use the "Code" button to envelope them, else they make the message too long and incoherent.

Regards

Pete

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.