Failed attach to database not traced [CORE6272] #6514
Comments
Modified by: @AlexPeshkoffassignee: Alexander Peshkov [ alexpeshkoff ] |
Modified by: @AlexPeshkoffstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 Beta 2 [ 10888 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Deferred Test Details: Can not reproduce expected result: still no messages in a trace log when trying to connect to non-existent DB. |
|
Commented by: @AlexPeshkoff Did you start remote (via host:service_mgr with login and password) or system trace (embedded with login SYSDBA)? First case does not work - that's known bug, second works for me with both SS or CS. |
|
Commented by: @pavel-zotov I always start trace using remote protocol. |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: Deferred => Done with caveats Test Details: Can not reproduce expected result: still no messages in a trace log when trying to connect to non-existent DB. => Currently can be reproduced only when call fbsvcmgr using local protocol, i.e. without "localhost:" prefix (see Alex's note here). |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @AlexPeshkoff
In some cases (for example - file does not exist) attach failure is not reported in trace.
firebird.conf:
Providers = Engine13
ServerMode = Classic
fbtrace.conf:
database
{
enabled = true
log_connections = true
}
$ ./fbtracemgr -se service_mgr -sta -conf fbtrace.conf -user sysdba
In other window:
$ ./isql -user sysdba localhost:something # failure reported in trace
$ ./isql -user sysdba nodb # failure not reported in trace (assume nodb does not exist)
Commits: 2db2dc9
====== Test Details ======
Currently can be reproduced only when call fbsvcmgr using local protocol, i.e. without "localhost:" prefix (see Alex's note here).
The text was updated successfully, but these errors were encountered: