You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When shutting down several DBs for scheduled server maintenance/backup every night, sometimes the fb_smp_server crashes and the log reports "Fatal lock manager error: invalid lock id (0), errno: 0" (it seems similar to CORE3016). Then the guardian seems unable to restart the server process for several times, it attempts to open a wrong named file (see attached firebird.log).
I can't tell if there are open connections to the DBs being shut down, but it seems the -force timeout (300 in my case) has not been reached, although the shutdown process takes one or two minutes when the problem occurs, vs just one or two seconds in normal situations.
This problems never occurred with FB 2.5.1.
The text was updated successfully, but these errors were encountered:
I can't switch to 2.5.3 snapshot here, I'm on a production environment. CORE3817 opens another issue however, so have I to change my shutdown to -force 0? Is there any other workaround to avoid killing possible active connections so brutally?
Also I forgot to mention that, after such crashes, sometimes one of the shutdown DBs becomes inaccessible even after having it online. The only solution I've found by now is to stop and start firebird engine ( /etc/init.d/firebird stop, /etc/init.d/firebird start ), while a simple restart ( /etc/init.d/firebird restart ) doesn't help (tried it several times). This causes severe disservice.
Submitted by: John Franck (bozzy)
Attachments:
firebird.log
When shutting down several DBs for scheduled server maintenance/backup every night, sometimes the fb_smp_server crashes and the log reports "Fatal lock manager error: invalid lock id (0), errno: 0" (it seems similar to CORE3016). Then the guardian seems unable to restart the server process for several times, it attempts to open a wrong named file (see attached firebird.log).
I can't tell if there are open connections to the DBs being shut down, but it seems the -force timeout (300 in my case) has not been reached, although the shutdown process takes one or two minutes when the problem occurs, vs just one or two seconds in normal situations.
This problems never occurred with FB 2.5.1.
The text was updated successfully, but these errors were encountered: