| Subject | Re: [firebird-support] Windows 2003 - Abnormal Termination |
|---|---|
| Author | Helen Borrie |
| Post date | 2004-12-18T11:34:26Z |
At 03:15 PM 17/12/2004 +0000, you wrote:
(Dead Servers Do Not Talk).
the server crashed?
2. Have you looked at the 1.5.2 point release notes to see whether there is
something in there that could give a clue? (Notes are on-line, link is on
the main page).
3. Did you remember to disable Disk Shadowing on that partition?
4. Can you exclude the possibility that the database file was getting
backed up by a filesystem backup process whilst something was happening in
the database, e.g. a user app left running, a sweep running, garbage
collection running...need to exclude database files from system backups if
you are leaving the server running while its going on.
5. Power cut? no UPS?
6. Night cleaners unplugged the server to plug in the vacuum cleaner ?
(thought I'd ask...one site where I worked had that problem...)
7. Other people installing software and letting the install program reboot
the system?
8. Have you taken a look at the transaction statistics to check whether
applications are behaving nicely?
Sorry, tried to get to 10, couldn't make it.
./hb
>Hi AllOnly the installation script or a human could have done that.
>
>I have Firebird 1.5.1 installed on a Win2003 server. I understood that
>the Guardian was not required for this version of Windows but on 2
>occasions Windows has stopped the Firebird Server. There was nothing
>in the Server Log but in the Event Log Windows described Firebird as a
>faulting application. The control panel applet showed that startup had
>been changed from automatic to manual!
>I then installed the Guardian and a week or so later it had to restartWith guardian running, the server crash would get logged. Without it, not
>Firebird because of an abnormal termination. This time the server log
>had an entry which recorded abnormal termination and the number
>4294967295.
(Dead Servers Do Not Talk).
>Any ideas about what might be happening? This is a fairly recent1. Does the firebird log yield any clues as to what was happening before
>installation with only occasional users at the moment. As far as I can
>tell nobody was actually connected at the time of the shutdowns. There
>does not appear to be any problem with the database.
the server crashed?
2. Have you looked at the 1.5.2 point release notes to see whether there is
something in there that could give a clue? (Notes are on-line, link is on
the main page).
3. Did you remember to disable Disk Shadowing on that partition?
4. Can you exclude the possibility that the database file was getting
backed up by a filesystem backup process whilst something was happening in
the database, e.g. a user app left running, a sweep running, garbage
collection running...need to exclude database files from system backups if
you are leaving the server running while its going on.
5. Power cut? no UPS?
6. Night cleaners unplugged the server to plug in the vacuum cleaner ?
(thought I'd ask...one site where I worked had that problem...)
7. Other people installing software and letting the install program reboot
the system?
8. Have you taken a look at the transaction statistics to check whether
applications are behaving nicely?
Sorry, tried to get to 10, couldn't make it.
./hb