Subject Re: Coredump from Firebird 1.03 Server
Author Svein Erling Tysvær
In general, Firebird shouldn't crash. I think the most common causes
when it happens will be hardware fault or faulty UDFs (of which
Firebird does not have control).

I have no experience with Firebird crashing, and - excepting Ann
Harrison who fixed InterBase databases for a living - I think very few
have much experience with it (some will have experienced it, but it's
the first time I've heard anyone say 'crashes regularly').

So, a few questions:

Does the Firebird server use UDFs?
Does the Firebird server use events?
How is backup done?
Does any antivirus program run on databases (I doubt this should make
the server crash)?
Are there enough free space available for Firebirds temporary files?
What's the Firebird server doing when it crashes (is it during night
when only gbak is doing it's stuff or does it happen when doing some
particular SQL statements)?

Many of these questions may be irrelevant, but the people with enough
knowledge to pinpoint your problem is better at ignoring excessive
information than to guess required information.


--- In, "Josef Gschwendtner" wrote:
> Hi,
> one of our firebird servers (Firebird 1.03 on a Redhat 7.2 system at
> a customer site) crashes regularly, and the coredump shows the
> following lines:
> Core was generated by '/opt/interbase/bin/ibserver'.
> Program terminated with signal 11, Segmentation fault.
> #0 0x08083d9a in local_fini () at eval.c:41
> Output to /opt/interbase/interbase.log:
> /opt/interbase/bin/ibguard: bin/ibserver terminated abnormally (-1)
> What could we do to chase down this problem?
> Does anybody have any experiance with that?
> Is it a Firebird 1.03 problem?
> Thank you for your help,
> Josef Gschwendtner