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

Monitoring tables do not work after fresh linux install. [CORE1728] #2152

Closed
firebird-issue-importer opened this issue Feb 6, 2008 · 7 comments
Closed

Comments

@firebird-issue-importer
Copy link

@firebird-issue-importer firebird-issue-importer commented Feb 6, 2008

Submitted by: @AlexPeshkoff

The issue was reported by Ivan C Cruz:

I have start testing Firebird 2.1 last week and stumbled in a possible bug:
whenever I select from one of the new monitoring virtual tables I receive
the error:

Statement failed, SQLCODE = -902
operating system directive open failed
-Permission denied

In isql, the error is printed just after the headers. No records are
printed.
In the firebird.log I get this:

IvanAMD32 (Server) Tue Feb 5 23:52:36 2008
Cannot initialize the shared memory region

Tested with both beta(?) 2 and rc 1. OS is Ubuntu 7.10. Firebird is
SuperServer 2.1.0.17735 installed with the script provided in
the tar.gz package. Database was backed up and restored
properly. ODS version is 11.1. Problem only happens with
monitoring tables and everything else looks OK.

Commits: 9d984a9 a8ec4a2

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Feb 6, 2008

Modified by: @AlexPeshkoff

assignee: Alexander Peshkov [ alexpeshkoff ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Feb 6, 2008

Commented by: @pmakowski

Just for information, it seems that it is a Linux Superserver issue only (32 and 64 bits) , I tested Classic under Linux and SuperServer under MacOsx and both are ok

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Feb 6, 2008

Commented by: @AlexPeshkoff

In that case I tend to think that we have incorrect access rights to $FbRoot directory. User firebird should not have write access to it.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Feb 6, 2008

Commented by: @AlexPeshkoff

Create appropriate file at install time (like files for locks, events, etc.)

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Feb 6, 2008

Modified by: @AlexPeshkoff

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

resolution: Fixed [ 1 ]

Fix Version: 2.1 RC2 [ 10250 ]

Fix Version: 2.5 Alpha 1 [ 10224 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Nov 18, 2008

Modified by: @pcisar

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

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Jan 19, 2016

Modified by: @pavel-zotov

QA Status: No test

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