At 01:03 AM 7/10/2006, you wrote:

>Thanks again ./heLen
>
>Followed this advice and more, unfortunately each not any more
>helpful than previously:
>-RPM'd the NPTL version
>-turned off multithreading in BIOS under 'advanced chipset options'
>-followed advice in release notes under' NTPL problems on higher
>Linuxen' eg in /etc/init.d/firebird --> LD_ASSUME_KERNEL=2.2.5
>export LD_ASSUME_KERNEL

You are not supposed to do *both*. Read again what I wrote -
succinctly, either use the NPTL build (and go with the new threading
model that is the default with that kernel) or *disable* it by the
environment setting (which then makes the kernel use the old
threading model). With the NPTL build and old threading you're in
the same hole as before except this time you are head-down instead of
feet-down! :-)

>The funny thing is that I can simultaneously connect to each of
>these 2 databases on the Centos server (192.168.2.10) using
>different GUI programs on the worksation (192.168.2.15 -ib_sql to
>connect to one database and ibaccess for another), with connection
>info viewable on the server:
> IPV4 TCP 0u Listening on port gds_db
> IPV4 TCP 1u 192.168.2.10:gds_db -> 192.168.2.15:2854 ESTABLISHED
> IPV4 TCP 7u 192.168.2.10:gds_db -> 192.168.2.15:2904 ESTABLISHED
>
>*BUT* when I try to run my workstation's clinical app which requires
>a connection to BOTH of the same database, it persistently refuses
>to connect to a particular one of these databases and the program
>exits!

I think you'll find all these anomalies will disappear when you
eventually have the server engine and the OS using the same threading model.

>If you or anyone has any ideas it would be most helpful
>
>Rgds
>very_compused

Well, I'll leave your reposting of my original message for you to
read over. Oh, OK, I'll share a tip with you, since you insist! If
you ever buy a 4-thread overlocker, thread it up according to the
manual the first time you ever use it and then leave it threaded forever. :-)

./hb

> > Rather, considering the office has Red Hat 8 (old threading model)
> > and home has Centos 4.3 (2.6.9+ kernel, which has the new/native
> > threading library (NPTL). Try either doing a full uninstall of
>the
> > old threading version of the v.1.5.3 rpm and replacing it with the
> > NPTL version; or study the piece in the installation section of
>the
> > release notes about setting up your Linux to force it to use the
>old
> > threading model.
> >
> > ./heLen
> > Misinformation Technology Autodidact
> >
> >
> >
> > >Regards
> > >Michael
> > >
> > >Pastes:
> > >1. Centos (at home - database connection problem)
> > >For process /opt/firebird/bin/fbserver (PID 697)
> > >Open network connections
> > >Type Protocol File Descriptor Details
> > >IPV4 TCP 0u Listening on port gds_db
> > >
> > >netstat -an | grep 3050
> > >tcp 0 0 0.0.0.0:3050 0.0.0.0:* LISTEN
> > >
> > >
> > >2. Office computer (firebird working - Red Hat 8)
> > >
> > >For process /opt/firebird/bin/fbserver (PID 697)
> > >Open network connections
> > >Type Protocol File Descriptor Details
> > >IPV4 TCP 0u Listening on port gds_db
> > >IPV4 TCP 1u 127.0.0.1:gds_db -> 127.0.0.1:32772 ESTABLISHED
> > >IPV4 TCP 7u 127.0.0.1:gds_db -> 127.0.0.1:32773 ESTABLISHED
> > >IPV4 TCP 8u 127.0.0.1:gds_db -> 127.0.0.1:32775 ESTABLISHED
> > >IPV4 TCP 9u 192.168.1.111:gds_db -> 192.168.1.21:2625 ESTABLISHED
> > >IPV4 TCP 11u 192.168.1.111:gds_db -> 192.168.1.21:2626 ESTABLISHED
> > >
> > >
> > >netstat -an | grep 3050
> > >tcp 0 0 0.0.0.0:3050 0.0.0.0:*
> > >LISTEN
> > >tcp 0 0 127.0.0.1:3050 127.0.0.1:32775
>ESTABLISHED
> > >tcp 0 0 127.0.0.1:3050 127.0.0.1:32773
>ESTABLISHED
> > >tcp 0 0 127.0.0.1:3050 127.0.0.1:32772
>ESTABLISHED
> > >tcp 0 0 127.0.0.1:32773 127.0.0.1:3050
>ESTABLISHED
> > >tcp 0 0 127.0.0.1:32772 127.0.0.1:3050
>ESTABLISHED
> > >tcp 0 0 127.0.0.1:32775 127.0.0.1:3050
>ESTABLISHED
> > >
> > > > I don't know. There are no clues here regarding
>authentication,
> > >though.
> > > >
> > > > The firebird.log file doesn't get written to during
> > > > installation. However, the gethostbyname clue says that a
>client
> > > > asked to connect to host by the name of asterisk1.local and the
> > > > network couldn't find a mapping for it. Apparently it's the
> > > > hard-coded server name the application is trying to connect to,
> > >not
> > > > the IP address you put in your ini file.
> > > >
> > > > Look in the /etc/hosts file and see what's there for that IP
> > > > address....if necessary, add an entry:
> > > > 192.168.2.10 asterisk1.local
> > > >
> > > > (case-sensitive on Linux) and see whether the app has any
>better
> > > > success at connecting.
> > > >
> > > > Might need a similar entry in the $windir$\system32
> > >\drivers\etc\hosts
> > > > file on the client, as well.
> > > >
> > > > ./heLen
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > >
> > >Visit http://www.firebirdsql.org and click the Resources item
> > >on the main (top) menu. Try Knowledgebase and FAQ links !
> > >
> > >Also search the knowledgebases at http://www.ibphoenix.com
> > >
> > >++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> > >
> > >Yahoo! Groups Links
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
>
>
>
>
>
>
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>Visit http://www.firebirdsql.org and click the Resources item
>on the main (top) menu. Try Knowledgebase and FAQ links !
>
>Also search the knowledgebases at http://www.ibphoenix.com
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>Yahoo! Groups Links
>
>
>
>
>
>
>