| Subject | Re: [firebird-support] Re: Windows 2003 - Abnormal Termination |
|---|---|
| Author | Helen Borrie |
| Post date | 2004-12-19T01:22:33Z |
At 08:12 PM 18/12/2004 +0000, you wrote:
You eliminated that from the conditions, I think.
What you don't seem to have determined is what the server was doing when
the OS detected the memory incursion. For the server to be "faulting", it
would have to have been doing something, i.e. have made an extraordinary
request that the OS couldn't satisfy and that the server could not handle.
If there is genuinely no attachment to the server and you are certain that
no background process is going on (like GC or a sweep) then you have
something illogical there. All the log is telling you is that the server
crashed and Guardian tried to restart it.
Someone you don't know about altered the configuration of the
service. Maybe that's not all he did. The server won't crash without help
-- it's designed not to. If a regular weekly crash is occurring, all I can
suggest is to monitor what's really happening around there and see what's
going on if it occurs again.
Check that all clients use the correct client library. Ensure that there
are spare ports open in the firewall if you have apps that use events -
dedicate one if necessary by configuring RemoteAuxPort in firebird.conf and
restarting the server. Make sure there is enough temp space configured to
accommodate sorts if the server is short of RAM.
You didn't respond to this one:
is on the main page).
./heLen
>Hi HelenYes; and as (I think) Salvatore mentioned, this is usually a misbehaving UDF.
>
>Thanks for the ideas. Unfortunately none has provided any clue to what
>has happened.
>
>The Firebird log is boring - nothing really happening. No squawks from
>users so I take it nobody was connected. There was no kind of backup
>going on. Shadowing is disabled. No careless cleaners. The only app on
>the machine is my own and it is running fine on other servers with
>InterBase. No power cut. No stress.
>
>The Windows log described Firebird as a faulting application. What
>could this mean? Trying to access something which it shouldn't?
You eliminated that from the conditions, I think.
What you don't seem to have determined is what the server was doing when
the OS detected the memory incursion. For the server to be "faulting", it
would have to have been doing something, i.e. have made an extraordinary
request that the OS couldn't satisfy and that the server could not handle.
If there is genuinely no attachment to the server and you are certain that
no background process is going on (like GC or a sweep) then you have
something illogical there. All the log is telling you is that the server
crashed and Guardian tried to restart it.
Someone you don't know about altered the configuration of the
service. Maybe that's not all he did. The server won't crash without help
-- it's designed not to. If a regular weekly crash is occurring, all I can
suggest is to monitor what's really happening around there and see what's
going on if it occurs again.
Check that all clients use the correct client library. Ensure that there
are spare ports open in the firewall if you have apps that use events -
dedicate one if necessary by configuring RemoteAuxPort in firebird.conf and
restarting the server. Make sure there is enough temp space configured to
accommodate sorts if the server is short of RAM.
You didn't respond to this one:
> 2. Have you looked at the 1.5.2 point release notes to see whetherthere is something in there that could give a clue? (Notes are on-line, link
is on the main page).
./heLen