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

Jump to bottom

fbguard.exe doesn't install if there is already another FB installation in the same machine [CORE6372] #6611

Open
firebird-automations opened this issue Jul 27, 2020 · 3 comments
Open

fbguard.exe doesn't install if there is already another FB installation in the same machine [CORE6372] #6611

firebird-automations opened this issue Jul 27, 2020 · 3 comments
Assignees
@reevespaul
Labels
affect-version: 3.0.6 component: guardian component: installation priority: minor type: bug

Comments

@firebird-automations
Copy link
Collaborator

Submitted by: John Franck (bozzy)

I was trying to install FB 3.0.6 in a machine where FB 2.5.9 is already installed as a service in SuperServer mode on port 3050 (default install).

The installer warned me that in this condition the new FB instance will be installed but not configured (no problem, I'll configure it manually later).

After the installation finished, I've edited firebird.conf to change RemoteServicePort to 3051, then run "instsvc.exe i -g -name FB30" from the installation folder to register the new service.

In Services I can see the new "Firebird Guardian - FB30" and "Firebird Server - FB30" next to the previously installed ones for FB 2.5.9, but when trying to start the new guardian, Windows complains that there's no such executable (running the Firebird Server works).

After investigating it appears that the file fbguard.exe wasn't installed at all. Comparing the installation folders of this installation and another one on a fresh machine, the only file that's missing is the fbguard.exe, which seems not to be installed when there's another FB installation on the same machine.

Copying the fbguard.exe from a fresh FB 3.0.6 installation to my multi-instance machine solved the problem with the service not starting.
@firebird-automations
Copy link
Collaborator Author

Modified by: @reevespaul

assignee: Paul Reeves [ paul_reeves ]

@firebird-automations
Copy link
Collaborator Author

Commented by: @reevespaul

I guess this is a bug of some sort but probably a documentation error more than anything.
Basically the configuration page is skipped if there is an existing firebird install. Which means all the defaults apply.
The configuration page allows the option to include the guardian but it is unchecked by default.
The guardian is not needed and hasn't been for a long time so the installer is trying to nudge users away from it.

If you had just ran:

instsvc.exe i -name FB30

the service would have started fine. And if, for some unlikely reason the service ever crashes the O/S service manager will step in and restart the service.

@firebird-automations
Copy link
Collaborator Author

Commented by: John Franck (bozzy)

Ok, thank you for the explanation.
Actually I have a post-it here for remembering me to read more about the guardian and its role in 2020, 'cause I had a feel that it could be left over now.
You just confirmed my thought, so I'll happily go without the -g option.

BTW, maybe it shouldn't even be an option if it's really not needed anymore. Just my 2 cents.

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@reevespaul reevespaul

Labels
affect-version: 3.0.6 component: guardian component: installation priority: minor type: bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@reevespaul @firebird-automations