fbserver.exe: terminated abnormally (4294967295) FB Superserver 2.5.2 x64

[Roland Turcan]

Hello firebird-***@yahoogroups.com!

When I make an backup then server restarts. It happens when it writes
"finishing and going home". Also when I try to restore that backup it
makes during finalization server restart.

SERVER1 (Client) Tue Feb 19 21:52:55 2013
"C:\Program Files\Firebird\Firebird_2_5\bin\fbserver.exe": terminated abnormally (4294967295)

Then I try to check it using gfix:

gfix -v -full -user SYSDBA -password masterkey exekutor.fdb
gfix -v -n -user SYSDBA -password masterkey exekutor.fdb
gfix -v -n -i -user SYSDBA -password masterkey exekutor.fdb

no error is shown.

I also tried to use IBFirstAid 2.5 diagnose I can see the only strange
thing about "Found 6757 undefined pages".

21:55:18 INFO: Analyzing database low-level structures...
21:55:18 INFO: Process database file #1 of 1 files.
22:08:48 INFO: Actual PageCount: 1838521 found in database
22:08:48 INFO: Found 6757 undefined pages.
22:08:48 INFO: ====== DATABASE IS READY FOR DIAGNOSING AND REPAIRING. ====
22:08:48 INFO: ====== Now choose "Diagnose" or "Repair". ====

What can I do to find out the reason for server crash?

Thanks in advance.

[Roland Turcan]

I have got the actual error message from gbak -b -v -i

gbak:closing file, committing, and finishing. 11815776768 bytes written
gbak: ERROR:connection lost to database
gbak:Error closing database, but backup file is OK
gbak: ERROR:Error writing data to the connection

and of course server restarted.


<<< 19. 2. 2013 22:56 - Roland Turcan "***@rotursoft.sk" >>>
RT> Hello firebird-***@yahoogroups.com!
RT>
RT> When I make an backup then server restarts. It happens when it writes
RT> "finishing and going home". Also when I try to restore that backup it
RT> makes during finalization server restart.
RT>
RT> SERVER1 (Client) Tue Feb 19 21:52:55 2013
RT> "C:\Program Files\Firebird\Firebird_2_5\bin\fbserver.exe":
RT> terminated abnormally (4294967295)
RT>
RT> Then I try to check it using gfix:
RT>
RT> gfix -v -full -user SYSDBA -password masterkey exekutor.fdb
RT> gfix -v -n -user SYSDBA -password masterkey exekutor.fdb
RT> gfix -v -n -i -user SYSDBA -password masterkey exekutor.fdb
RT>
RT> no error is shown.
RT>
RT> I also tried to use IBFirstAid 2.5 diagnose I can see the only strange
RT> thing about "Found 6757 undefined pages".
RT>
RT> 21:55:18 INFO: Analyzing database low-level structures...
RT> 21:55:18 INFO: Process database file #1 of 1 files.
RT> 22:08:48 INFO: Actual PageCount: 1838521 found in database
RT> 22:08:48 INFO: Found 6757 undefined pages.
RT> 22:08:48 INFO: ====== DATABASE IS READY FOR DIAGNOSING AND REPAIRING. ====
RT> 22:08:48 INFO: ====== Now choose "Diagnose" or "Repair". ====
RT>
RT> What can I do to find out the reason for server crash?
RT>
RT> Thanks in advance.

[Alexey Kovyazin]

Hi Roland,

Terminated abnormally is indication of the server crash, not database
corruption (though it can be some relation).
First of all, you need to look at UDFs you are using.
Did you migrate recently from 32 bit version, and one UDFs is 32 bit?
Did you add new UDFs recently?

Then, if UDF are Ok (or, better, no UDFs at all) try to reproduce crash
with metadata only backup.
If it constantly repeats, this can be sign of some internal bug in
Firebird. In this case you need to add bug into tracker.firebirdsql.org
with test case (zip and attach there metadata backup).

Post by Roland Turcan
I also tried to use IBFirstAid 2.5 diagnose I can see the only strange
thing about "Found 6757 undefined pages".

It's not stange - in 2.1+ Firebird allocates additional undefined pages
in the end of the database file for performance and safety reason.

Post by Roland Turcan
21:55:18 INFO: Analyzing database low-level structures...
21:55:18 INFO: Process database file #1 of 1 files.
22:08:48 INFO: Actual PageCount: 1838521 found in database
22:08:48 INFO: Found 6757 undefined pages.
22:08:48 INFO: ====== DATABASE IS READY FOR DIAGNOSING AND REPAIRING. ====
22:08:48 INFO: ====== Now choose "Diagnose" or "Repair". ====

Did you run Diagnose after that?
Though, since you was able to make backup, and problem at restore level,
I doubt that FBFirstAID will show anything.

Regards,
Alexey Kovyazin
IBSurgeon






[Non-text portions of this message have been removed]

[Roland Turcan]

Sorry I sent one answer accidentally unfinished.

Post by Alexey Kovyazin
Hi Roland,

Hi Alexey,

Post by Alexey Kovyazin
Terminated abnormally is indication of the server crash, not
database corruption (though it can be some relation).
First of all, you need to look at UDFs you are using.
Did you migrate recently from 32 bit version, and one UDFs is 32
bit? Did you add new UDFs recently?

I have been using FB 2.5.1 x64 since beginning on this server. UDFs
are working fine and I didn't have any problem with UDFs for years.
UDFs are written Pascan and compiled in FreePascal 2.6.

Post by Alexey Kovyazin
Then, if UDF are Ok (or, better, no UDFs at all) try to reproduce
crash with metadata only backup.

OK, I will do this, but I cannot, because the database is in use 5/8. I will try it in the evening.

Post by Alexey Kovyazin
If it constantly repeats, this can be sign of some internal bug in
Firebird. In this case you need to add bug into
tracker.firebirdsql.org with test case (zip and attach there metadata
backup).

I have also tried to update to FB 2.5.2 x64, but the issue remained
the same.

Post by Alexey Kovyazin

Post by Roland Turcan
I also tried to use IBFirstAid 2.5 diagnose I can see the only strange
thing about "Found 6757 undefined pages".
It's not stange - in 2.1+ Firebird allocates additional undefined
pages in the end of the database file for performance and safety reason.
21:55:18 INFO: Analyzing database low-level structures...
21:55:18 INFO: Process database file #1 of 1 files.
22:08:48 INFO: Actual PageCount: 1838521 found in database
22:08:48 INFO: Found 6757 undefined pages.
22:08:48 INFO: ====== DATABASE IS READY FOR DIAGNOSING AND REPAIRING. ====
22:08:48 INFO: ====== Now choose "Diagnose" or "Repair". ====

Did you run Diagnose after that?
Though, since you was able to make backup, and problem at restore
level, I doubt that FBFirstAID will show anything.

Yes, I have full protocol, would you like to see it? Maybe I sent it to you directly?
BTW: I was using the free version of FBFirstAID only.

Thanks.

[Roland Turcan]

Hello Alexey and others,

I have done today the following:

1. gbak -b -v -m ---- no problem
2. used fbcopy (thanks to M.Babuskov) to copy data to healthy DB
3. gbak -b -v on new database ---- no problem.

Sooo, once again thanks to all of you at least for reading my emails.
Of course especially to Alexey who spent his valuable time to help me
and to M.Babushov for FBCopy utility.

TRoland;

<<< 20. 2. 2013 8:28 - Alexey Kovyazin "***@ib-aid.com" >>>
AK> Hi Roland,

AK> Terminated abnormally is indication of the server crash, not
AK> database corruption (though it can be some relation).
AK> First of all, you need to look at UDFs you are using.
AK> Did you migrate recently from 32 bit version, and one UDFs is 32
AK> bit? Did you add new UDFs recently?

AK> Then, if UDF are Ok (or, better, no UDFs at all) try to reproduce
AK> crash with metadata only backup.
AK> If it constantly repeats, this can be sign of some internal bug
AK> in Firebird. In this case you need to add bug into
AK> tracker.firebirdsql.org with test case (zip and attach there metadata backup).


AK>
AK>
AK>
AK>
AK>
AK> I also tried to use IBFirstAid 2.5 diagnose I can
AK> see the only strange
AK> thing about "Found 6757 undefined pages".
AK>
AK>
AK>
AK>
AK>
AK>
AK> It's not stange - in 2.1+ Firebird allocates additional
AK> undefined pages in the end of the database file for
AK> performance and safety reason.
AK>
AK>
AK>
AK>
AK>
AK>
AK> 21:55:18 INFO: Analyzing database low-level structures...
AK> 21:55:18 INFO: Process database file #1 of 1 files.
AK> 22:08:48 INFO: Actual PageCount: 1838521 found in database
AK> 22:08:48 INFO: Found 6757 undefined pages.
AK> 22:08:48 INFO: ====== DATABASE IS READY FOR
AK> DIAGNOSING AND REPAIRING. ====
AK> 22:08:48 INFO: ====== Now choose "Diagnose" or "Repair". ====
AK>
AK>
AK>
AK>
AK>
AK>
AK> Did you run Diagnose after that?
AK> Though, since you was able to make backup, and problem at
AK> restore level, I doubt that FBFirstAID will show anything.
AK>
AK> Regards,
AK> Alexey Kovyazin
AK> IBSurgeon
AK>
AK>
AK>
AK>
AK>
AK>

[Roland Turcan]

Hello all once again,

I have spent quite long time with analyzing firebird.log files on many
different servers I can access today.

All servers I checked are running on Windows 7/2008R2 and they have in
firebird.log very often logged this problem:

"C:\Program Files\Firebird\Firebird_2_5\bin\fbserver.exe": terminated abnormally (4294967295)

I thought if it is really not related to broken UDF, ... but this
crash happens when no one is connected too. Therefore I think it
cannot be related to any part of my database(s).

All servers are in version 2.5.1 or 2.5.2 64bit where customers are
having SuperServer instance and average database size is 8 GB and all
servers are working with the only database all the day.

Do you have any recommendation what to check?

TRoland;

<<< 21. 2. 2013 23:59 - Roland Turcan "***@rotursoft.sk" >>>
RT> Hello Alexey and others,
RT>
RT> I have done today the following:
RT>
RT> 1. gbak -b -v -m ---- no problem
RT> 2. used fbcopy (thanks to M.Babuskov) to copy data to healthy DB
RT> 3. gbak -b -v on new database ---- no problem.
RT>
RT> Sooo, once again thanks to all of you at least for reading my emails.
RT> Of course especially to Alexey who spent his valuable time to help me
RT> and to M.Babushov for FBCopy utility.
RT>
RT> TRoland;
RT>
RT> <<< 20. 2. 2013 8:28 - Alexey Kovyazin "***@ib-aid.com" >>>
AK>> Hi Roland,
RT>
AK>> Terminated abnormally is indication of the server crash, not
AK>> database corruption (though it can be some relation).
AK>> First of all, you need to look at UDFs you are using.
AK>> Did you migrate recently from 32 bit version, and one UDFs is 32
AK>> bit? Did you add new UDFs recently?
RT>
AK>> Then, if UDF are Ok (or, better, no UDFs at all) try to reproduce
AK>> crash with metadata only backup.
AK>> If it constantly repeats, this can be sign of some internal bug
AK>> in Firebird. In this case you need to add bug into
AK>> tracker.firebirdsql.org with test case (zip and attach there metadata backup).
RT>
AK>>
AK>>
AK>>
AK>>
AK>>
AK>> I also tried to use IBFirstAid 2.5 diagnose I can
AK>> see the only strange
AK>> thing about "Found 6757 undefined pages".
AK>>
AK>>
AK>>
AK>>
AK>>
AK>>
AK>> It's not stange - in 2.1+ Firebird allocates additional
AK>> undefined pages in the end of the database file for
AK>> performance and safety reason.
AK>>
AK>>
AK>>
AK>>
AK>>
AK>>
AK>> 21:55:18 INFO: Analyzing database low-level structures...
AK>> 21:55:18 INFO: Process database file #1 of 1 files.
AK>> 22:08:48 INFO: Actual PageCount: 1838521 found in database
AK>> 22:08:48 INFO: Found 6757 undefined pages.
AK>> 22:08:48 INFO: ====== DATABASE IS READY FOR
AK>> DIAGNOSING AND REPAIRING. ====
AK>> 22:08:48 INFO: ====== Now choose "Diagnose" or "Repair". ====
AK>>
AK>>
AK>>
AK>>
AK>>
AK>>
AK>> Did you run Diagnose after that?
AK>> Though, since you was able to make backup, and problem at
AK>> restore level, I doubt that FBFirstAID will show anything.
AK>>
AK>> Regards,
AK>> Alexey Kovyazin
AK>> IBSurgeon