Widefs log files

[Vulcan]

Hi Pete,

I'm trying to fault find an FS crash and hope that the Widefs log files will help, before I have to ask you for help :wink:

In the log files are the numbers before each entry the time in milliseconds since the log file was started?

And can you give me an indication of the normal value of max/avg reception achieved please?

Thanks

After a further trial this is a section of the Wideclient log file, do the 'error=' numbers mean anything to you Pete?

17645 New Client Application: "squawkbox" (Id=464)

541608 Timed out response: connection assumed lost!

541608 Ready to try connection again

541628 Attempting to connect now

541638 Connection made okay!

544362 Error on client post-Connection Select() [Error=10053]

Software caused connection abort

544362 Ready to try connection again

544392 Attempting to connect now

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

Connection refused

[Pete Dowson]

I'm trying to fault find an FS crash and hope that the Widefs log files will help

Not sure how WideFS would come into it.

In the log files are the numbers before each entry the time in milliseconds since the log file was started?

Yes.

And can you give me an indication of the normal value of max/avg reception achieved please?

What do you mean by "value of max/avg reception"? I don't understand. WideServer sends out updates for requested data as it changes, normally at a maximum this would be at FS frame rates. The signals should travel along the wires pretty instantaneously. Block sizes will vary, usually quite small, but up to the maximum it allows, but at a typical Ethernet speed of 100Mbps, even a large block or some 4kbytes is only taking something like a half a millisecond to send/receive.

After a further trial this is a section of the Wideclient log file, do the 'error=' numbers mean anything to you Pete?

544362 Error on client post-Connection Select() [Error=10053]

Software caused connection abort

As it tells you, the number 10053 means "Software caused connection abort", at least that's the text from Winsock. Looking it up there's a further expansion "An established connection was aborted by the software in your host machine."

So, where's the host machine log? Only it can tell you why it disconnected.

After this you immediately got: [Error=10061] Connection refused, so whatever it was it didn't come back.

Regards,

Pete

[Vulcan]

>Not sure how WideFS would come into it. <

All I was trying to do is see if the Widefs log file(s) gave me a clue as to when the crash was happening and what was causing it.

From just looking at FS it was not clear exactly when and why to crash happened - mind you I still don't have a clue why it crashes even though I now know when and what app caused the crash :cry:

Rgds