Firebird Server hangs
---------------------
Key: CORE-3603
URL: http://tracker.firebirdsql.org/browse/CORE-3603
Project: Firebird Core
Issue Type: Bug
Components: Engine
Affects Versions: 2.1.1
Environment: Firebird 2.2.1 17910, Classic Server, Page Size 4096,
Pages allocated 259894, DB File Size 1015 MB, Client Libray gds32.dll Version
6.3.3. 18185
2x Intel Xeon 3400 MHz, 4096 MB DDR, Fujitsu Siemens Primergy RX200S2, WIN 2003
Server Standard SP2
Reporter: Christian Masberg
Priority: Critical
Hi there!
We are using Firebird server software for 5 years and have been experienced
just a few problems. Since appr. 3 years the server hung from time to time
(once every half year). It was something that was ok and bearable.
In the recent half year the deadlocks of the whole db got more frequent. The
last few weeks the server hung once a week making it a real problem.
The majority of the incidents happened during a backup process handled by the
FIBS Service (Firebird/Interbase Backup Scheduler) which uses the gbak.exe for
remote and scheduled backups, but there were also deadlocks during normal
business and while executing rather huge queries.
In these cases neither a db shutdown and a following bring online nor a restart
of firebird service is solving the problem. Only a restart of the physical
server brings the db back to normal life.
I have now read a lot of issues and did some web research and I want to setup
Dr. Watson on our server to create a hopefully siginificant dump file after the
next crash. As a following step I would then update the server to 2.1.4, but
beforehand I would like to invest some time to maybe discover the cause of the
problem.
Concerning the setup I have some questions.
After some searching I found the corresponding debug version to our server
which is 2.1.1 build 17910. What are the differences of the debug version from
the standard one? Is it safe to implement it in productive or is it just for
testing environments? Is it slowing down the perfomrance in any kind? If we
update to version 2.1.4 is it advisable to install the debug versio by default
for the case that the problem is not resolved? Are there any further tips or
hints for seting up the debug environment?
I would be very grateful if any of you could spare some experiences in this
issue! Thank you very much in advance.
Christian
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://tracker.firebirdsql.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
