--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...> wrote:

> 1. Exactly what does "hang" mean in this context?

I mean that all the C application running on the same machine that are
connected to the database stuck without any feedback. All the
application, not yet connected, trying connecting to the database for
a simple select statement answer with the following messages:
-DB_Attach
-Unable to complete network request to host "localhost".
-Failed to establish a connection.
-Select_SQL/start_trs
-invalid database handle (no active connection)
-Select_SQL/commit
-invalid transaction handle (expecting explicit transaction start)
-DB_Detach/detach_db
-invalid database handle (no active connection)

> 2. What do you see in the firebird.log?

I'll have the log soon. Unfortunately the production machine is in a
remote area and to have the info it takes time. I 'll post it ASAP

> 3. What happens to clients that are already connected?

They stuck without answer.

> >This happens only on RedHat ES4 machines, on
> >similar machines running RedHat 9 and Firebird 1.5.1 we never
> >experienced such trouble.
>
> 4. Are you certain you were previously using Superserver 1.5.1 on RH
> 9, or could it have been Classic?

Yes I'm. on RH 9 is running SuperServer 1.5.1-nptl. I double checked
and also in RH9 there is an old nptl version

> 5. If it was an OS compatibility issue, we would surely know about
> it by now. I'm reasonably sure, anyway, that Alex builds the
> Superserver on FC 4. I can't comment on any traps with that
> hardware, though it doesn't ring any bells.
>
> 6. However, there could be a compatibility issue for any clients
> trying to connect with a mismatched client library.

The client are mainly application running on the same server that use
the libfbclient.so.1.5.3.
But there are windows clients running the gds32.dll coming from
Interbase 6.0. But these client are seldomly used.

> Suspect a configuration issue, e.g. you previously configured
> something in your old firebird.conf and now you are running with the
> unmodified firebird.conf of the new installation? Or you have a
> misconfiguration somewhere in the new network setup? Or your app
> uses events and the engine's requests for random port assignment are
> being denied by the firewall?

Never touched the firebird.conf file, always used the default
installation settings. The trouble happens in 2 different places on
separate server in different local network with the same config and no
firewall installed.

Do you think that inserting the LD_ASSUME_KERNEL=2.2.5 variable as
suggested in the Release note could help ?

Thank you

Alessandro