Issue Details (XML | Word | Printable)

Key: CORE-4042
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Dmitry Yemanov
Reporter: John Franck
Votes: 0
Watchers: 4

If you were logged in you would be able to see more operations.
Firebird Core

"Fatal lock manager error: invalid lock id (0), errno: 0" when shutting down database with "gfix -shut full -force nnn"

Created: 05/Feb/13 04:26 PM   Updated: 06/Feb/13 09:49 AM
Component/s: Engine, GFIX, Guardian
Affects Version/s: 2.5.2
Fix Version/s: None

File Attachments: 1. Text File firebird.log (4 kB)

Environment: SuSE Linux Enterprise Server 11 SP1 (x86_64 kernel 2.6.32), Firebird 2.5.2 SuperClassic

 Description  « Hide
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 CORE-3016). 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.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
John Franck added a comment - 05/Feb/13 04:27 PM
Log of the crash situation

Dmitry Yemanov added a comment - 05/Feb/13 06:37 PM
Just for the record, forced shutdown with a non-zero timeout is known to not work at all in Classic / SuperClassic, see CORE-3817.

Alexander Peshkov added a comment - 06/Feb/13 05:48 AM
Probably worth trying 2.5.3 snapshot? At least one bug, that caused invalid lock id (0), is fixed in it.

John Franck added a comment - 06/Feb/13 09:49 AM
I can't switch to 2.5.3 snapshot here, I'm on a production environment. CORE-3817 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.