Subject Re: [firebird-support] Fatal lock manager error
Author Helen Borrie
At 01:57 AM 5/10/2006, Nick Upson <nick.upson@...> wrote:
>specificly I installed FirebirdCS- downloaded 2 days ago
>On 04/10/06, you wrote:
> > I installed classic 1.5.3 over classic 1.5.1

> > > I installed the 1.5.3 rpm from the ibphoenix website straight over the
> > >existing 1.5.1 installation.

Sounds messy if you used the rpm installer and didn't unininstall
1.5.1 first. The Firebird 1.x rpms don't support the -update switch.

> > >couild this be an installation issue:
> > >
> > > >The firebird entry in xinetd.d was removed and had to be added
> > > >manually (I copied from another server still running 1.5.1)
> > >
> > >
> > > ISC_kill: process fb_lock_mgr couldn't deliver signal 16 to process
> > > (client app running on unix server that executes the SP):
> permission denied
> > >

If the process was an instance of it wouldn't be using
xinetd, it would be directly connected to the database file. Some thoughts:

-- an instance of might have been loaded already when
you overwrote the binaries

-- you didn't reboot after the reinstallation and so the filesystem
is still finding the old libfbembed binary

Unless you've already found a way to resolve this muddle, I'd suggest
exploring your rpm database to find out what Firebird packages are
installed, and uninstall both of them using rpm with the -e switch
(beginning with the earlier package). After that, I'd want to reboot
the machine and do a clean install of the newer package.