| Subject | Re: Multiple instances of fbserver.exe |
|---|---|
| Author | marklamberton |
| Post date | 2010-09-09T07:57:50Z |
Many thanks for the replies. FB was installed as SuperServer.
Apologies for not being more explicit. The system is Windows 2003 now running under a VMWARE VM. The physical server on which this was running was virtualised in its entirety - FB was not reinstalled. I was not involved in this exercise...
When I refer to extra copies of fbserver.exe, I mean that if you look at the running tasks, there are often several instances of fbserver.exe running simultaneously - that is, 'something' has started fbserver multiple times. It is installed as a SYSTEM SERVICE so why the Service Manager thinks it needs to restart is a mystery.
When this occurs, if a user has logged-off, they can't log back on until the 'extra' instances of fbserver have been manually terminated. Users who have not logged off retain their connections OK. Clearly the extra running copies block access to the port.
So 'something' is starting fbserver but so far, I can't see what is doing it.
I realise that this is not an FB problem per se, but I thought it was worth a shot to see if anyone else has run into it. If (when!) I track down the cause, I'll let y'all know.
Mark
Apologies for not being more explicit. The system is Windows 2003 now running under a VMWARE VM. The physical server on which this was running was virtualised in its entirety - FB was not reinstalled. I was not involved in this exercise...
When I refer to extra copies of fbserver.exe, I mean that if you look at the running tasks, there are often several instances of fbserver.exe running simultaneously - that is, 'something' has started fbserver multiple times. It is installed as a SYSTEM SERVICE so why the Service Manager thinks it needs to restart is a mystery.
When this occurs, if a user has logged-off, they can't log back on until the 'extra' instances of fbserver have been manually terminated. Users who have not logged off retain their connections OK. Clearly the extra running copies block access to the port.
So 'something' is starting fbserver but so far, I can't see what is doing it.
I realise that this is not an FB problem per se, but I thought it was worth a shot to see if anyone else has run into it. If (when!) I track down the cause, I'll let y'all know.
Mark
--- In firebird-support@yahoogroups.com, Helen Borrie <helebor@...> wrote:
>
>
> >> Does anyone know (or can speculate) what might be instantiating extra
> >> copies of fbserver.exe?
>
> At 06:35 PM 9/09/2010, PenWin wrote:
>
> >To be honest, I can't quite imaging what you mean by "extra copies" or
> >"multiple instances" of fbserver.exe.
>
> Nor I; so I wonder whether Classic was installed in the new VM by mistake and he's really seeing multiple fb_inet_server.exe instances.
>
> >But maybe I can help you anyway: It is perfectly possible to run
> >multiple Firebird servers, even in different versions, on the same
> >machine. It is happening right now at the computer I am using. The
> >process of accomplishing it is described in
> >{FIREBIRD}\doc\install_windows_manually.txt.
>
> Or read the whole of Chapter 9 in the Fb 1.5 release notes, "Configuring the Port Service on Client and Server".
>
> ./hb
>