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

Can't connect to Firebird SuperServer on OSX 10.7 Lion [CORE3572] #3926

Closed
firebird-automations opened this issue Aug 11, 2011 · 7 comments
Closed

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: Guilherme Bradasch (guimas)

I can't make clients connect to Firebird SuperServer 2.1.4 in OSX Lion. In firebird.log I get a "INET/inet_error: connect errno = 61". As suggested in the support list, I tried to run "/Library/StartupItems/Firebird/Firebird start", and it gives me the same error. I tried the i386, x86_64 and the "lipo" builds, and all showed the same problem.

The connection strings are correct, using the host and the database name (or an alias), and I tried to connect using flamerobin and a Java app I develop.

Also, The SuperServer version worked without problems in Snow Leopard, in the same machine. After the upgrade to Lion that the SuperServer stopped working. This issue happens in my desktop iMac and in my MacBook.

The ClassicServer version works as expected.

@firebird-automations
Copy link
Collaborator Author

Commented by: @paulbeach

Fixed for 2.5.1 - due to be released soon. In the meantime please read this.
http://paulbeachsblog.blogspot.com/2011/07/firebird-25-superserver-and-macosx-107.html

@firebird-automations
Copy link
Collaborator Author

Modified by: @paulbeach

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

resolution: Fixed [ 1 ]

Fix Version: 2.5.1 [ 10333 ]

assignee: Paul Beach [ pbeach ]

@firebird-automations
Copy link
Collaborator Author

Commented by: Guilherme Bradasch (guimas)

Thanks,

My concern is for the 2.1 version. Is this going to be backported?

@firebird-automations
Copy link
Collaborator Author

Commented by: @paulbeach

No the fix is not going to be back ported, because the problem does not affect 2.1.x

@firebird-automations
Copy link
Collaborator Author

Modified by: @pcisar

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

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

QA Status: No test

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

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

QA Status: No test => Cannot be tested

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

No branches or pull requests

2 participants