Jump to content
The simFlight Network Forums

WideFS problem


Recommended Posts

I started to experience this problem these 2 days

Not sure what i've done wrong, but WideFS would stop transmitting data to my 2nd PC during flight..

I'm suspecting there's some problem with the Server side

some how the buffer runs out a while after i started FS

It's very frustrating when i uses SB3 and the ATC would just see me standing still at a spot while i told him that i had been flying miles away from that position...

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

Blocksize guide = 2048 (double allowed)

Date (dmy): 21/11/05, Time 13:42:10.953: Server name is LAWRENX1

92859 Initialising TCP/IP server

92859 Initialising IPX/SPX server

92875 ServerNode=0.0.1792.2368.34157

94046 Broadcasting service every 1 mSecs

104046 Incoming connection Accepted ok (skt=3012)

104640 Incoming connection Accepted ok (skt=2832)

164062 Incoming connection Accepted ok (skt=2704)

164671 Incoming connection Accepted ok (skt=3068)

224046 Incoming connection Accepted ok (skt=3136)

224656 Incoming connection Accepted ok (skt=2676)

284046 Incoming connection Accepted ok (skt=3116)

284640 Incoming connection Accepted ok (skt=3112)

344046 Incoming connection Accepted ok (skt=3088)

344640 Incoming connection Accepted ok (skt=2448)

404062 Incoming connection Accepted ok (skt=3048)

404640 Incoming connection Accepted ok (skt=3144)

464046 Incoming connection Accepted ok (skt=3152)

464656 Incoming connection Accepted ok (skt=1700)

524062 Incoming connection Accepted ok (skt=3160)

524656 Incoming connection Accepted ok (skt=3184)

584046 Incoming connection Accepted ok (skt=3208)

584250 Incoming read: no buffer available! (skt=3208)

584640 Incoming connection Accepted ok (skt=3200)

584843 Incoming read: no buffer available! (skt=3200)

644062 Incoming connection Accepted ok (skt=3228)

644234 Incoming read: no buffer available! (skt=3228)

644656 Incoming connection Accepted ok (skt=3224)

644828 Incoming read: no buffer available! (skt=3224)

704062 Incoming connection Accepted ok (skt=3260)

704234 Incoming read: no buffer available! (skt=3260)

704640 Incoming connection Accepted ok (skt=3252)

704828 Incoming read: no buffer available! (skt=3252)

764062 Incoming connection Accepted ok (skt=404)

764234 Incoming read: no buffer available! (skt=404)

764640 Incoming connection Accepted ok (skt=3276)

764828 Incoming read: no buffer available! (skt=3276)

824062 Incoming connection Accepted ok (skt=3308)

824234 Incoming read: no buffer available! (skt=3308)

824656 Incoming connection Accepted ok (skt=3292)

824828 Incoming read: no buffer available! (skt=3292)

884062 Incoming connection Accepted ok (skt=3316)

884250 Incoming read: no buffer available! (skt=3316)

884640 Incoming connection Accepted ok (skt=3324)

884828 Incoming read: no buffer available! (skt=3324)

944046 Incoming connection Accepted ok (skt=3368)

944234 Incoming read: no buffer available! (skt=3368)

944640 Incoming connection Accepted ok (skt=3080)

944843 Incoming read: no buffer available! (skt=3080)

974609 Closing down now ...

Memory managed: Offset records: 0 alloc, 0 free

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

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

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

wideserver.ini setting: (it used to be having no problem at all)

[Config]

AdvertiseService=Yes

AutoRestart=0

AutoUpdateTime=13

MaximumBlock=4096

NoStoppedRestarts=Yes

Port=8002

RestartTime=10

SendTimeout=15

TCPcoalesce=No

[ClientNames]

1=LAWRENX2

I can't figure it out..

Link to comment
Share on other sites

I'm suspecting there's some problem with the Server side

some how the buffer runs out a while after i started FS

The reason may be on the Client side, or at least it may be logged there. There is no error logged by the Server. Look:

104046 Incoming connection Accepted ok (skt=3012)

104640 Incoming connection Accepted ok (skt=2832)

164062 Incoming connection Accepted ok (skt=2704)

164671 Incoming connection Accepted ok (skt=3068)

224046 Incoming connection Accepted ok (skt=3136)

224656 Incoming connection Accepted ok (skt=2676)

284046 Incoming connection Accepted ok (skt=3116)

284640 Incoming connection Accepted ok (skt=3112)

344046 Incoming connection Accepted ok (skt=3088)

344640 Incoming connection Accepted ok (skt=2448)

404062 Incoming connection Accepted ok (skt=3048)

404640 Incoming connection Accepted ok (skt=3144)

464046 Incoming connection Accepted ok (skt=3152)

464656 Incoming connection Accepted ok (skt=1700)

524062 Incoming connection Accepted ok (skt=3160)

524656 Incoming connection Accepted ok (skt=3184)

584046 Incoming connection Accepted ok (skt=3208)

584250 Incoming read: no buffer available! (skt=3208)

I've never actually seen the "no buffer" message, but it will have occurred only because there are already the maximum number of connections (Sockets) allowed in your network settings. If you count them there are 16 before the 17th one fails. Probably 16 sockets is the maximum allowed by default on your Server.

Although you can probably increase that, it isn't the problem. The problem appears to be that the Client is not actually seeing any notification that its connection has been accepted. So it tries again. It is doing two attempts every 60 seconds, if you notice.

What was in the WideClient log? That may be more helpful. According to this log you never actually got properly connected at all, though you say

WideFS would stop transmitting data to my 2nd PC during flight.

This log shows no successful connection at all -- there was no transmission to be stopped!

Regards,

Pete

Link to comment
Share on other sites

unfortunately... the problem still exist :(

even though the client recognized the server

data could not pass through... the buffer problem is still there... im still thinking if it's the problem at the server side...

here's the log of both server and client from my last run(3 hrs log is kinda long..)

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 21/11/05, Time 19:34:55.734: Server name is LAWRENX1

159031 Initialising TCP/IP server

159031 Initialising IPX/SPX server

159047 ServerNode=0.256.1792.2368.34157

160047 Broadcasting service every 1 mSecs

161562 Incoming connection Accepted ok (skt=3040)

161625 Connected to computer "LAWRENX2" running WideClient version 6.500 (skt=3040)

174906 Incoming connection Accepted ok (skt=3056)

175484 Incoming connection Accepted ok (skt=3064)

234937 Incoming connection Accepted ok (skt=2652)

235484 Incoming connection Accepted ok (skt=3284)

294906 Incoming connection Accepted ok (skt=3124)

295531 Incoming connection Accepted ok (skt=2700)

356172 Incoming connection Accepted ok (skt=3308)

356172 Incoming connection Accepted ok (skt=3316)

356172 Unknown return on accept msg [Event=32] (skt=3308)

414937 Incoming connection Accepted ok (skt=3532)

415531 Incoming connection Accepted ok (skt=3456)

474922 Incoming connection Accepted ok (skt=3464)

475500 Incoming connection Accepted ok (skt=3480)

534906 Incoming connection Accepted ok (skt=3496)

535484 Incoming connection Accepted ok (skt=3504)

594922 Incoming connection Accepted ok (skt=3520)

595500 Incoming connection Accepted ok (skt=3528)

597312 Incoming read: no buffer available! (skt=3040)

613328 Incoming connection Accepted ok (skt=3544)

613406 Incoming read: no buffer available! (skt=3544)

631484 Incoming connection Accepted ok (skt=3560)

631531 Incoming read: no buffer available! (skt=3560)

649609 Incoming connection Accepted ok (skt=3568)

649687 Incoming read: no buffer available! (skt=3568)

654906 Incoming connection Accepted ok (skt=3580)

655094 Incoming read: no buffer available! (skt=3580)

.

. (omitted repeated lines..)

.

3295500 Incoming connection Accepted ok (skt=6452)

3295672 Incoming read: no buffer available! (skt=6452)

3297484 Incoming connection Accepted ok (skt=6464)

3297515 Incoming read: no buffer available! (skt=6464)

3315609 Incoming connection Accepted ok (skt=6476)

3315640 Incoming read on unconnected socket -- Ignored! (skt=6476)

3333734 Incoming connection Accepted ok (skt=6488)

3333797 Incoming read on unconnected socket -- Ignored! (skt=6488)

.

.

.

11994890 Incoming connection Accepted ok (skt=4492)

11995094 Incoming read on unconnected socket -- Ignored! (skt=4492)

11995484 Incoming connection Accepted ok (skt=2740)

11995703 Incoming read on unconnected socket -- Ignored! (skt=2740)

12047297 Closing down now ...

Memory managed: Offset records: 31 alloc, 31 free

Throughput maximum achieved: 1 frames/sec, 107 bytes/sec

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

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

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

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

Date (dmy): 21/11/05, Time 11:28:31.461: Client name is LAWRENX2

160 Attempting to connect now

510 Server = LAWRENX1

510 Trying TCP/IP host "LAWRENX1" port 8002 ...

510Okay, IP Address = 192.168.1.8

520 Connection made okay!

19938 New Client Application: "squawkbox" (Id=2684)

359617 Timed out response: connection assumed lost!

359617 Ready to try connection again

359667 Timed out response: connection assumed lost!

359667 Attempting to connect now

359677 Connection made okay!

377723 Timed out response: connection assumed lost!

377723 Ready to try connection again

377773 Timed out response: connection assumed lost!

377783 Attempting to connect now

377783 Connection made okay!

382670 Error on client post-Connection Select() [Error=10053] Software caused connection abort

382670 Connection closed by server!

382670 The connection was terminated due to a time-out or other failure!

382680 Ready to try connection again

382700 Attempting to connect now

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

383641 Ready to try connection again

383661 Attempting to connect now

393706 Giving up server, looking for another!

394707 Failed to connect: waiting to try again

395719 Attempting to connect now

395719 Giving up server, looking for another!

437278 Trying to locate server: TCP/IP needs ServerName or IP address!

438290 Giving up server, looking for another!

481562 Trying to locate server: TCP/IP needs ServerName or IP address!

482573 Giving up server, looking for another!

525846 Trying to locate server: TCP/IP needs ServerName or IP address!

526857 Giving up server, looking for another!

549029 Server = LAWRENX1

549029 Trying TCP/IP host "LAWRENX1" port 8002 ...

549029Okay, IP Address = 192.168.1.8

549039 Connection made okay!

1000739 Timed out response: connection assumed lost!

1000749 Ready to try connection again

1000799 Timed out response: connection assumed lost!

1000799 Attempting to connect now

1000809 Connection made okay!

1018905 Timed out response: connection assumed lost!

1018915 Ready to try connection again

1018965 Timed out response: connection assumed lost!

.

. (omitted repeat)

.

12354845 Timed out response: connection assumed lost!

12354845 Ready to try connection again

12354895 Timed out response: connection assumed lost!

12354895 Attempting to connect now

12354905 Connection made okay!

12372961 Timed out response: connection assumed lost!

12372971 Ready to try connection again

12373011 Timed out response: connection assumed lost!

12373021 Attempting to connect now

12373021 Connection made okay!

12386581 ****** End of session performance summary ******

12386581 Total time connected = 12189 seconds

12386581 Reception maximum: 1 frames/sec, 111 bytes/sec

12386581 Reception average whilst connected: 0 frames/sec, 1 bytes/sec

12386581 Transmission maximum: 6 frames/sec, 293 bytes/sec

12386581 Transmission average whilst connected: 1 frames/sec, 55 bytes/sec

12386581 Max receive buffer = 225, Max send depth = 14, Send frames lost = 13

12386581 **************** Individual client application activity ****************

12386581 Client 2684 requests: 60145 (Ave 4/sec), Data: 3441118 bytes (282/sec), Average 57 bytes/Process

12386581 ********* Log file closed (Buffers: MaxUsed 14, Alloc 62414 Freed 62414 Refused 0) *********

Link to comment
Share on other sites

unfortunately... the problem still exist :(

even though the client recognized the server

data could not pass through... the buffer problem is still there...

The "buffer problem" is not the problem, as I said -- that is merely the result of all those failing attempts to connect. The Windows sockets available are getting all used up. On my systems that would take 128 tries, on yours only 16. But it is a symptom not a cause.

Your WideClient log is odd:

359617 Ready to try connection again

359667 Timed out response: connection assumed lost!

The timing out of the response is occurring only 50 mSecs after the attempt to connect. Have you been changing parameters in the WideClient.INI file by any chance? Show me, or, probably best, delete the INI file and start again.

Regards,

Pete

Link to comment
Share on other sites

I have tried deleting the wideclient.ini

however, the same problem is still here....

all i've added in it was either the servername or the servernode(before)

nothing else has been changed..

like that:

[Config]

ButtonScanInterval=20

ClassInstance=0

NetworkTiming=5,1

PollInterval=2000

Port=8002

ResponseTime=18

ApplicationDelay=0

TCPcoalesce=No

UseTCPIP=Yes

WaitForNewData=500

MaxSendQ=100

OnMaxSendQ=Log

NewSendScanTime=50

Priority=3,1,2

Window=75,81,593,489

ServerName=LAWRENX1

Link to comment
Share on other sites

I have tried deleting the wideclient.ini

however, the same problem is still here....

all i've added in it was either the servername or the servernode(before)

nothing else has been changed..

Okay then.

Sorry, I'm all out of ideas as far as my software is concerned. it is only reacting to what it is told by Windows.

Something is not right, but it looks like it is between the Network driver/card/cable at each end. Possibly uninstalling the network hardware in both PCs and reinstalling (so it reinstalls drivers and restores itself) should be the first step. If it is hardware playing up it doesn't look like it, and unless you have alternative Network cards/connections it isn't so easy to check.

Regards

Pete

Link to comment
Share on other sites

First of all, thank you very much, Pete

reinstallng the drivers didn't work either :(

i notice one thing...

the socket which was connected by the client would run out of buffer first

And i've done some testing.. The timing match, when the "no buffer" problem hit the socket connected, the data transmission stopped...

I'm not sure it's normal.....

let me show u another log

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

Blocksize guide = 4096 (double allowed)

Date (dmy): 22/11/05, Time 11:31:13.984: Server name is LAWRENX1

47141 Initialising TCP/IP server

47157 Initialising IPX/SPX server

47157 ServerNode=0.0.1792.2368.34157

47532 Incoming connection Accepted ok (skt=2988)

47625 Connected to computer "LAWRENX2" running WideClient version 6.500 (skt=2988)

48016 Broadcasting service every 1 mSecs

70000 Incoming connection Accepted ok (skt=384)

70610 Incoming connection Accepted ok (skt=444)

130016 Incoming connection Accepted ok (skt=568)

130610 Incoming connection Accepted ok (skt=2764)

185922 Error 10054: client socket disconnected at Client: removing (skt=2988)

190000 Incoming connection Accepted ok (skt=2988)

190610 Incoming connection Accepted ok (skt=2888)

198719 Incoming connection Accepted ok (skt=3004)

198766 Connected to computer "LAWRENX2" running WideClient version 6.500 (skt=3004)

250000 Incoming connection Accepted ok (skt=2964)

250594 Incoming connection Accepted ok (skt=2976)

310000 Incoming connection Accepted ok (skt=2936)

310610 Incoming connection Accepted ok (skt=2940)

370000 Incoming connection Accepted ok (skt=3148)

370594 Incoming connection Accepted ok (skt=3156)

430000 Incoming connection Accepted ok (skt=3188)

430594 Incoming connection Accepted ok (skt=3204)

490016 Incoming connection Accepted ok (skt=3208)

490594 Incoming connection Accepted ok (skt=3220)

491422 Incoming read: no buffer available! (skt=3004)

527516 Incoming connection Accepted ok (skt=3232)

527563 Incoming read: no buffer available! (skt=3232)

552000 Incoming connection Accepted ok (skt=3296)

552000 Incoming connection Accepted ok (skt=3284)

552000 Incoming read: no buffer available! (skt=3296)

552000 Incoming connection Accepted ok (skt=3280)

552000 Unknown return on accept msg [Event=32] (skt=3284)

552000 Incoming read: no buffer available! (skt=3284)

552000 Unknown return on accept msg [Event=32] (skt=3280)

552000 Incoming read: no buffer available! (skt=3280)

556954 Closing down now ...

Memory managed: Offset records: 26 alloc, 26 free

Throughput maximum achieved: 1 frames/sec, 112 bytes/sec

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

Average receive rate from "LAWRENX2": 0 frames/sec, 16 bytes/sec

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

Link to comment
Share on other sites

And i've done some testing.. The timing match, when the "no buffer" problem hit the socket connected, the data transmission stopped...

I'm not sure it's normal.....

Sorry, I don't understand what you are saying.

The reason your are running out of buffers is because the maximum number of sockets are being opened. But none of those (or only one or maybe two in some of your logs) are ever actually connecting suffuciently well for any data transmission.

Look:

47532 Incoming connection Accepted ok (skt=2988)

47625 Connected to computer "LAWRENX2" running WideClient version 6.500 (skt=2988)

This shows a socket (2988) which is connected correctly and which had at least the initial exchanges successfully completed -- hence the Server knows the Client's name.

But:

70000 Incoming connection Accepted ok (skt=384)

70610 Incoming connection Accepted ok (skt=444)

130016 Incoming connection Accepted ok (skt=568)

130610 Incoming connection Accepted ok (skt=2764)

190000 Incoming connection Accepted ok (skt=2988)

190610 Incoming connection Accepted ok (skt=2888)

198719 Incoming connection Accepted ok (skt=3004)

198766 Connected to computer "LAWRENX2" running WideClient version 6.500 (skt=3004)

Of all those connections the only one which got as far as one simply data exchange (for that is all it needs to identify the client PC's name) was the last, socket 3004.

Then:

250000 Incoming connection Accepted ok (skt=2964)

250594 Incoming connection Accepted ok (skt=2976)

310000 Incoming connection Accepted ok (skt=2936)

310610 Incoming connection Accepted ok (skt=2940)

370000 Incoming connection Accepted ok (skt=3148)

370594 Incoming connection Accepted ok (skt=3156)

430000 Incoming connection Accepted ok (skt=3188)

430594 Incoming connection Accepted ok (skt=3204)

490016 Incoming connection Accepted ok (skt=3208)

490594 Incoming connection Accepted ok (skt=3220)

491422 Incoming read: no buffer available! (skt=3004)

None of these connections ever resulted in any data exchanges! The only reason you get the "no buffer" is because Windows Sockets has used them all up is supplying all those inactive (failing) sockets!

And the repeated opening of new sockets is due, simply, to the Client's attempts at getting some response from the server. The Client log will show that (the timeouts). Unfortunately, if the Server doesn't get any data from the Client then the latter won't get stuff from the Server either. It's a two-way thing. It isn't possibly to say, from the logs, who is responsible. there are no actual errors being reported by windows in either case. It is merely doing nothing that is the problem.

This woeful lack of data exchange is reflected in the summary at the end:

Memory managed: Offset records: 26 alloc, 26 free

Throughput maximum achieved: 1 frames/sec, 112 bytes/sec

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

Average receive rate from "LAWRENX2": 0 frames/sec, 16 bytes/sec

I'm sorry, but I have never seen anything like any of this before, and WideFS has been going string now for 8 years or so (well before FSUIPC was even thought of, in fact). If I were faced with what you are seeing I'd be going through a provess of elimination to find where the problems were in my systems. I'd start by replacing (or finding alternatives for) each Network adapter/card, the cable, the hub or switch if you are using one. Then, after that I'd certainly consider reinstalling Windows in either or both PCs. You are using Windows XP I take it? Is it up to date? If not try updating to SR2 in both systems.

I am afraid I am not a Windows or a Networking expert. All the Networking part of the code in WideFS is lifted straight out of Microsoft examples. Everything I've learned is in the WideFS DOC and much of what is in there has come from users. If you would like to go through all the Network settings on both PCs and write them down and show them, I'd be happy to compare them to some of mine, but I'm not sure where that would lead. We could try changing some, but there are thousands of WideFS users happy with default Windows settings, so I don't hold out a lot of hope (unless you've been changing things yourself?).

As a final attempt to try to see what is going on you can enable more logging in both Client and Server. First please download the very latest interim test versions from the announcement above, near the top of the Forum. Install both the Client and the Server parts. This will ensure we are both working from the same page. Then, before running anything do this:

in the Client INI change the Log= option to:

Log=Debugall

and in the Server INI change it to

Log=Debug

Then run the system FOR A SHORT TIME -- just long enough to see the problem.

The Log files will get huge very very quickly. Be sure to ZIP them both up, and send them to me at petedowson@btconnect.com.

Regards

Pete

Link to comment
Share on other sites

Just resetup the windows for my server PC, the problem is gone! no more buffer problem now! i guess it must have been some network problem with my windows...

but now im in pain resetting up my flight sim... the setup has overwritten much of my scenery and settings... GAH! :?

Anyway, thank you very very much for looking at my problem!

i surely hope it won't happen again.. :D

Link to comment
Share on other sites

Just resetup the windows for my server PC, the problem is gone! no more buffer problem now! i guess it must have been some network problem with my windows...

Yes, a corruption in some settings, somewhere, I assume. It gets horribly complicated. I'm glad you solved it.

but now im in pain resetting up my flight sim... the setup has overwritten much of my scenery and settings... GAH! :?

If you effectively regenerated the registry then those FS add-ons which like to have their installation data in the registry may need re-installing, but this isn't usually necessary. For FS itself there are only a few entries needed in the Registry I think. One way to get them in is to rename your current FS folder (so it doesn't get messed up), install FS again, then delete the new installation (just delete its folder) and rename the original folder back. This is what I usually do.

The settings for FS itself are in FS9.CFG, and shouldn't have been lost by only reinstalling Windows.

Regards,

Pete

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • 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.