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

GBAK "unavailable database" error when both service manager and localhost:db is specified [CORE3236] #3607

Closed
firebird-issue-importer opened this issue Nov 15, 2010 · 9 comments

Comments

@firebird-issue-importer

Submitted by: @pcisar

This doesn't work under 2.5, but works just fine under 2.1:

c:\Program Files\Firebird\Firebird_2_5\bin>gbak -b -se localhost:service_mgr -user sysdba -pas ... localhost:c:\db\employee.fdb c:\db\emp.fbk
gbak: ERROR:unavailable database
gbak:Exiting before completion due to errors

When localhost: is removed from database spec. it works:
c:\Program Files\Firebird\Firebird_2_5\bin>gbak -b -se localhost:service_mgr -user sysdba -pas ... c:\db\employee.fdb c:\db\emp.fbk

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 15, 2010

Commented by: @asfernandes

Isn't because you're using the server as a gateway to another server? AFAIR, this is turned off by security reasons.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 15, 2010

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 15, 2010

Commented by: @AlexPeshkoff

Adriano, agreed - ability to connect to other server from services manager was treated as security problem and turned off. The fact that it worked in 2.1 is sooner bug than feature.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 15, 2010

Commented by: @pcisar

I have no problem if you would resolve this as Won't Fix / As designed, but it should be noted in Release Notes / Fixed bugs.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 15, 2010

Commented by: @AlexPeshkoff

This happened during general review of FB's security architecture. I'm not sure what to add to release notes?

Text like "It's not possible any more to connect to firebird database, locate on another server, using service_mgr"? But it was never documented that it is possible...

Or may be "It was possible to use instead of path of the file of the database a name of firebird database on another server. Fixed in 2.5.0."

Which is better?

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 16, 2010

Commented by: @pcisar

Guess that "It was possible to use instead of path of the file of the database a name of firebird database on another server. Fixed in 2.5.0." added to section related to security would do the trick.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 3, 2010

Commented by: @AlexPeshkoff

Appropriate text is added to Chapter15 of release notes for 2.5.1

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 3, 2010

Modified by: @AlexPeshkoff

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

resolution: Won't Fix [ 2 ]

Fix Version: 2.5.1 [ 10333 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 3, 2010

Modified by: @pcisar

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