Issue Details (XML | Word | Printable)

Key: CORE-3512
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Alexander Peshkov
Reporter: Alexander Peshkov
Votes: 0
Watchers: 0

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

Server hangs when trace is running

Created: 03/Jun/11 02:05 PM   Updated: 18/Jan/16 05:08 PM
Component/s: Engine
Affects Version/s: 3.0 Initial, 2.5.0
Fix Version/s: 2.5.1, 3.0 Alpha 1

QA Status: No test

 Description  « Hide
Issue reported by Pavel Cisar:

GLDS found a problem with fbtracemgr in 2.5.1 snapshot builds (lock-ups)
on Linux and I confirmed it.

After using interactive fbtracemgr for a few minutes I had another lockup, was not able to connect to any db, one old fb process was still working (i.e. not completely locked up). What happened is that I was running load simulator and started interactive trace manager. It was working fine for a few minutes, then I noticed that load simulator stuck. Checked fb processes on server and they were not working. Ctrl-C'ed fbtracemgr. Tried to connect with embedded isql to that and to different db -- no luck (no response). Killed all fb processes connected to that db. Newest lock file was used only by that old working fb process, other older lock files were not used by any process. Still was not able to connect (stack traces for stuck isql below). Commenting out AuditTraceConfigFile in firebird.conf and undoing fbtrace.conf did not help. Renaming /tmp/firebird/fb_trace.{57CC44CD-3A56-92D4-3CF1-2C10B655CBA1}.0000000 helped, server is alive again.

 All   Comments   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
There are no subversion log entries for this issue yet.