You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First , congrats on 2.5 getting ready for Release.
1) I must always ask a root user to install/deinstall in this case: "FirebirdCS-2.5.0.25920-ReleaseCandidate2.amd64.rpm"
then all in "/opt/firebird/" was owned by root. (prev. version all was automatically owned by "firebird" accept SYSDBA.password file may some other stuff)
so i had it changed to be used by user "firebird" then i could run as "firebird" user.
2) So far the database is working oke in terms of DSQL/PSQL.
3) Here is the problem: firebird.log shows strange errors
eusdlsdbb024.logistics.corp Fri Feb 26 11:46:52 2010
Operating system call pthread_mutex_destroy failed. Error code 16
Submitted by: Derryck welas (welas)
Hi all,
First , congrats on 2.5 getting ready for Release.
1) I must always ask a root user to install/deinstall in this case: "FirebirdCS-2.5.0.25920-ReleaseCandidate2.amd64.rpm"
then all in "/opt/firebird/" was owned by root. (prev. version all was automatically owned by "firebird" accept SYSDBA.password file may some other stuff)
so i had it changed to be used by user "firebird" then i could run as "firebird" user.
2) So far the database is working oke in terms of DSQL/PSQL.
3) Here is the problem: firebird.log shows strange errors
eusdlsdbb024.logistics.corp Fri Feb 26 11:46:52 2010
Operating system call pthread_mutex_destroy failed. Error code 16
eusdlsdbb024.logistics.corp Fri Feb 26 11:46:52 2010
Fatal lock manager error: semop failed (release_shmem), errno: 11
eusdlsdbb024.logistics.corp Fri Feb 26 11:46:52 2010
Shutting down the server with 1 active connection(s) to 1 database(s), 0 active service(s)
eusdlsdbb024.logistics.corp Fri Feb 26 11:46:57 2010
Firebird shutdown is still in progress after the specified timeout
clearly someting is gooing wrong..
cheers,
Derryck
The text was updated successfully, but these errors were encountered: