[firebird-support] Re: Firebird 3 crashes, unable to capture crash dumps ( terminated abnormally (4294967295) )
Rudi, try to set BugcheckAbort = 1 at firebird.conf Regards, Vlad
Re: [firebird-support] file size and transactions
Hello shg_siste...@yahoo.com.ar, Friday, September 15, 2017, 2:53:19 AM, you wrote: > I read somewhere that the "read only" transactions are absolutelly > harmless to the GC and sweeping. Is that so? It is true for READ ONLY transactions that are started in READ COMMITTED isolation mode. In other isolation modes, long-running transactions in both READ ONLY and READ WRITE will block GC and evade sweeps. Helen
RE: [firebird-support] Firebird 3 crashes, unable to capture crash dumps ( terminated abnormally (4294967295) )
>but did you checked your DB against corruption? >gfix –validate –full >any errors (also in firebird.log)? The server have about 20 db’s, haven’t performed a validate full on each one of them. At the moment Im assuming theres no corruption because all of our clients are fully operational and there are no incidents reported by them. >Did you performed backup/restore process. Yes all db’s were backed up in 2.5 and restored in 3 >Do you use any udf? also system udf? We use quite a few udf’s , mosltly from freeAdhocUdf and some system ones. If an UDF was the culprit of the crash, Im assuming it would always crash at a certain query or function call, is this safe to assume? >Do you have enough free mem, free disk space also for temp files like sorting? Yes I don’t think this firebird installation every got above 2gb of peak ram usage out of 10gb free >Do you have recent Firebird version (which exactly) and also fbclient.dll >version (if you use it or gds32.dll) The latest stable firebird version 3.0.2 march/22 >From what I can tell, we don’t use the client libraries (we do use for >ibexpert but we rarely use ibexpert) We are running apache with php 5.6 on linux machines, connecting to the windows firebird server. The linux machines themselves have no firebird installation, only pure apache and php. What I do know is that the php firebird extension was not updated to work with firebird 3. One thing that I know that doesn’t work, for instance, are the new Boolean fields (we cannot use Boolean fields because php will not be able to read them). So, while php continues to be my number one suspict here, I was unable to capture a single error log which I’m able to recreate the crash. If php was crashing on a certain query, it would be trivial for me to get it from my logs (we log queries prior their execution) and recreate the crash. So, not only that is not happening, but also I can’t seem to get crash dump logs as described initially. This problem have been happening since day 1 of our new servers operating with firebird 3, about 5 months now.
Re: [firebird-support] Firebird 3 crashes, unable to capture crash dumps ( terminated abnormally (4294967295) )
Hi, i do not remember your previous description but did you checked your DB against corruption? gfix –validate –full any errors (also in firebird.log)? Did you performed backup/restore process. Do you use any udf? also system udf? Do you have enough free mem, free disk space also for temp files like sorting? Do you have recent Firebird version (which exactly) and also fbclient.dll version (if you use it or gds32.dll) regards, Karol Bieniaszewski From: Rudi Feijó rudi.fe...@multidadosti.com.br [firebird-support] Sent: Thursday, September 14, 2017 8:26 PM To: firebird-support@yahoogroups.com Subject: [firebird-support] Firebird 3 crashes, unable to capture crash dumps ( terminated abnormally (4294967295) ) Hello It’s been a while since I gave na update on my situation here. To recap, firebird 3 is crashing randomly on my server. It may crash once, twice, or 10 times a day. Or not once during the day. Server load is always minimal during the crashes, and so is the memory usage. With the help of the community, my latest attempts where to change the firebird.conf, and I tried a lot of different combinations, even returning to the default combination, but the problem still happens. Then, I tried to capture the crash dumps. I followed the instructions at Collecting User-Mode Dumps: https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181.aspx However, I’ve had a lot of crashes since I changed the registry, but no crash dumps are collected at all. I’ve made sure the dump directory is writable and readable by everyone (system, admin, user, etc). I also turned off the guardian as required, and created a simple batch file to restart firebird every 5 seconds if needed to act as a guardian. Before turning off the guardian, firebird.log always wrote a terminated abnormally (4294967295) error, not without the guardian it doesn’t write anything at all, it just crashes silently. So this is the status now. I’m thinking on trying to install de debug version and attach Watson to it, if anyone have any other ideas I’d be glad to hear. Specs : Firebird-3.0.2.32703_0_x64 on windows 2012 R2 VM (2 core 2.30gh xeon, 13gb ram) Config : ServerMode = Super GuardianOption = 0 WireCrypt = Enabled TempDirectories = C:\firebird-temp AuthServer = Legacy_Auth, Srp, Win_Sspi AuthClient = Legacy_Auth, Srp, Win_Sspi UserManager = Legacy_UserManager, Srp DefaultDbCachePages = 2 TempBlockSize = 2M TempCacheLimit = 364M LockMemSize = 9M LockHashSlots = 30011 Registry changes made to capture dumps : [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps] "DumpType"=dword:0002 "DumpFolder"=hex(2):63,00,3a,00,5c,00,6c,00,6f,00,63,00,61,00,6c,00,2d,00,64,\ 00,75,00,6d,00,70,00,73,00,00,00 "DumpCount"=dword: "CustomDumpFlags"=dword:
[firebird-support] Firebird 3 crashes, unable to capture crash dumps ( terminated abnormally (4294967295) )
Hello It’s been a while since I gave na update on my situation here. To recap, firebird 3 is crashing randomly on my server. It may crash once, twice, or 10 times a day. Or not once during the day. Server load is always minimal during the crashes, and so is the memory usage. With the help of the community, my latest attempts where to change the firebird.conf, and I tried a lot of different combinations, even returning to the default combination, but the problem still happens. Then, I tried to capture the crash dumps. I followed the instructions at Collecting User-Mode Dumps: https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181.aspx However, I’ve had a lot of crashes since I changed the registry, but no crash dumps are collected at all. I’ve made sure the dump directory is writable and readable by everyone (system, admin, user, etc). I also turned off the guardian as required, and created a simple batch file to restart firebird every 5 seconds if needed to act as a guardian. Before turning off the guardian, firebird.log always wrote a terminated abnormally (4294967295) error, not without the guardian it doesn’t write anything at all, it just crashes silently. So this is the status now. I’m thinking on trying to install de debug version and attach Watson to it, if anyone have any other ideas I’d be glad to hear. Specs : Firebird-3.0.2.32703_0_x64 on windows 2012 R2 VM (2 core 2.30gh xeon, 13gb ram) Config : ServerMode = Super GuardianOption = 0 WireCrypt = Enabled TempDirectories = C:\firebird-temp AuthServer = Legacy_Auth, Srp, Win_Sspi AuthClient = Legacy_Auth, Srp, Win_Sspi UserManager = Legacy_UserManager, Srp DefaultDbCachePages = 2 TempBlockSize = 2M TempCacheLimit = 364M LockMemSize = 9M LockHashSlots = 30011 Registry changes made to capture dumps : [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps] "DumpType"=dword:0002 "DumpFolder"=hex(2):63,00,3a,00,5c,00,6c,00,6f,00,63,00,61,00,6c,00,2d,00,64,\ 00,75,00,6d,00,70,00,73,00,00,00 "DumpCount"=dword: "CustomDumpFlags"=dword:
Re: [firebird-support] file size and transactions
>>Karol, >>I was referring to the default transaction state of snapshot (repeatable >>read) >>Other transaction states will have different effects. In your case >>read commited needs only the newest record version (or record versions >>created by >>the transaction itself) so its not going to block anything. >>Paul Thank You Paul, I asked to confirm if my knowledge is still up to date and luckily it is :) regards, Karol Bieniaszewski
RE: [firebird-support] file size and transactions
> I read somewhere that the "read only" transactions are absolutelly harmless > to the GC and sweeping. Is that so? >>Read only transactions only physically have an impact on the TIP/Header >>page(s), however a long running read only transaction >>will have the same effect as a long running read write transaction in that it >>will block GC and sweeps until it >>commits. <> Karol, I was referring to the default transaction state of snapshot (repeatable read) Other transaction states will have different effects. In your case read commited needs only the newest record version (or record versions created by the transaction itself) so its not going to block anything. Paul
Re: [firebird-support] file size and transactions
> I read somewhere that the "read only" transactions are absolutelly harmless > to the GC and sweeping. Is that so? >>Read only transactions only physically have an impact on the TIP/Header >>page(s), however a long running read only transaction >>will have the same effect as a long running read write transaction in that it >>will block GC and sweeps until it >>commits. >>Paul Hi, may i ask why readonly readcommited transaction block GC? Is this true? regards, Karol Bieniaszewski
RE: [firebird-support] file size and transactions
<> Not really, 2 weeks or 2 months would be a huge time. > I read somewhere that the "read only" transactions are absolutelly harmless > to the GC and sweeping. Is that so? Read only transactions only physically have an impact on the TIP/Header page(s), however a long running read only transaction will have the same effect as a long running read write transaction in that it will block GC and sweeps until it commits. Paul
Re: [firebird-support] file size and transactions
Hello Helen!! THANKS A MILLION FOR YOUR VERY COMPLETE ANSWER I did a simple routine to trap in a TXT log file all the active transactions. I realized that I need to be SYSDBA in order to run a query against MON$TRANSACTIONS. So, every time a user enters or exits from the applitaction I save a log of all the transactions. I found that I had some read/write transactions running for 2 hours. And that is a HUGE time I think! I read somewhere that the "read only" transactions are absolutelly harmless to the GC and sweeping. Is that so? Sergio.
