Issue Details (XML | Word | Printable)

Key: CORE-3935
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Alexander Peshkov
Reporter: Pavel Zotov
Votes: 0
Watchers: 2

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

Could not connect to production via TCP after delete from mon$attachments issued on *different* database on the same machine

Created: 24/Sep/12 11:29 AM   Updated: 18/Jan/16 03:55 PM
Component/s: None
Affects Version/s: None
Fix Version/s: 3.0 Alpha 1, 2.5.3

File Attachments: 1. Zip Archive (60 kB)

Issue Links:

QA Status: No test

 Description  « Hide
I`ve run some heavy query on auxiliary (NON-production) database that is placed on same machine as our production. This query was running too long and I decided to kill it:
isql production_alias
SQL>delete from mon$attachments; quit;

Immediatelly after it we detected that no more new connections to production can be established via TCP. Connections to production via local protocol were avaliable.
The firebird.log does NOT contains any interesting info - only messages with errno=-104.
I could create backtrace of fb_smp_server process when we could not to connect (see attach #1) and after restart linux and restoring common workload of out users (see attach #2).
Unfortunatelly I could NOT make log of fb_lock_print -d /var/db/firebird/production.fdb -a -m -c >fb_lock_print_dead.txt because log file has been created with zero size.

SQL> show version;
ISQL Version: LI-V2.5.2.26448 Firebird 2.5 // SUPERCLASSIC
Server version:
Firebird/linux AMD64 (access method), version "LI-V2.5.2.26448 Firebird 2.5"
on disk structure version 11.2
SQL> show database;
Database: kuntsevomain
        Owner: SYSDBA
Number of DB pages allocated = 1888000
Sweep interval = 0
Forced Writes are OFF
Transaction - oldest = 218095653
Transaction - oldest active = 218307431
Transaction - oldest snapshot = 218307431
Transaction - Next = 218365577
ODS = 11.2
Default Character set: WIN1251

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