|
PureBytes Links
Trading Reference Links
|
Mitch sent this to the list, but its image made it too large for
posting. I've put the jpg on my ftp site temporarily for those who
are interested; it's at:
[ftp://ftp.eskimo.com/u/j/jimo/1027prob.jpg]
--
jimo@xxxxxxxxxx
maintainer of the omega list
omega-list-request@xxxxxxxxxx
---------forwarded msg:-----------------------------
>From: saxman@xxxxxxxx
>Message-Id: <5.0.2.1.1.20010814101524.009f6b90@xxxxxxxxxxxx>
>To: omega list <omega-list@xxxxxxxxxx>
Hello all:)
An hour and a half ago (8/14, 8:34 am eastern time), I was a victim, once
again, of the dreaded 10/27 bug. I restarted the server when I returned to
the screen, and now have an approx. 30 min data hole.
However, I again noticed, as I have before, that the error seems to occur
after a "midnight system check", that does not happen at midnight! (You
can see this in the 'system status" window.
So, since Omega claims the fault is with BMI, and vice versa, my question
to everyone is: which entity generates the 'midnight system check'? Is it
BMI (I know, I know...Esignal), sending out a bad time (and date) stamp or
does the (4.0) server generate the check?
I have attached a jpg of my system status window from this morning. As you
can see, at 8:33 am, the server ran a midnight system check, and the date
changed to 10/27, where it remained until I manually shutdown at 9:57 and
restarted at 9:58.
I have used TS for moe than 10 years now, and this problem seems odd even
by Omega standards.
I'd appreciate any and all useful comments, either here or
privately. Since this 'system check' correlation has not been mentioned
here before (as far as I can recall), perhaps my observation can help solve
this ridiculous situation.
Thanks in advance.............Mitch
|
