Joshua D. Drake wrote:
> Tom Lane wrote:
>> "Joshua D. Drake" <jd@commandprompt.com> writes:
>>> Yes, unfortunately there isn't much more to be had for another 2
>>> weeks ;)
>>
>> I trust they've got the reboot time and they will know exactly how long
>> from reboot to problem? I'm not all that sold on the "GetTickCount
>> overflow" theory, but certainly we ought not be missing a chance to test
>> or disprove it.
>
> Yes I documented all conversations and disclaimers :)
O.k. further on this.. the crashing is happening quickly now but not
predictably. (as in sometimes a week sometimes 2 days). I just now got
them to send some further logs... Interestingly:
2006-09-28 16:38:37.406 LOG: could not send data to client: An
operation on a socket could not be performed because the system lacked
sufficient buffer space or because a queue was full.
That log entry is the last (of consequence) entry before the machine says:
2006-09-28 16:40:36.921 LOG: received fast shutdown request
2006-09-28 16:40:36.921 LOG: aborting any active transactions
2006-09-28 16:40:36.921 FATAL: terminating connection due to
administrator command
On the ERROR side of things I have a bunch of standard, unique key
violations etc... AND:
postgresql-2006-09-27_000000.log:2006-09-27 23:49:57.671 FATAL: could
not read from statistics collector pipe: No error
I have requested a clean run with entire log at DEBUG2. Hopefully that
will give us more info.
Sincerely,
Joshua D. Drake
>
> Joshua D. Drake
>
>>
>> regards, tom lane
>>
>
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL
solutionssince 1997 http://www.commandprompt.com/
