Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed attach to database not traced [CORE6272] #6514

Closed
firebird-issue-importer opened this issue Mar 30, 2020 · 7 comments
Closed

Failed attach to database not traced [CORE6272] #6514

firebird-issue-importer opened this issue Mar 30, 2020 · 7 comments

Comments

@firebird-issue-importer

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).

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Mar 30, 2020

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Mar 30, 2020

Modified by: @AlexPeshkoff

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 4.0 Beta 2 [ 10888 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 4, 2020

Modified by: @pavel-zotov

status: 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.
Sent letter to Alex et al, 04.04.2020 10:19

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 7, 2020

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.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 7, 2020

Commented by: @pavel-zotov

I always start trace using remote protocol.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 8, 2020

Modified by: @pavel-zotov

status: 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.
Sent letter to Alex et al, 04.04.2020 10:19

=>

Currently can be reproduced only when call fbsvcmgr using local protocol, i.e. without "localhost:" prefix (see Alex's note here).

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Apr 8, 2020

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants