Koozali.org: home of the SME Server
Obsolete Releases => SME 9.x Contribs => Topic started by: tdbsoft on December 31, 2016, 08:07:09 AM
-
Hoping someone may have an answer on the correct way to start the Firebird SuperServer
This is the environment - I installed a clean version of SME 9.x (latest) then run a full update etc
Then followed the Firebird wiki at https://wiki.contribs.org/Firebird (https://wiki.contribs.org/Firebird) on how to install Firebird Superserver for 9.x
All seemed to install with out error.
I then ran the post install commands
config set firebird service status enabled
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S99firebird
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc1.d/S01firebird
service firebird start
Found that these are not working as the run command file is /etc/init.d/firebird-superserver not firebird
so adjusted the above to
config set firebird service status enabled
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S99firebird-superserver
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc1.d/S01firebird-superserver
service firebird-superserver start
This seems to work apart from the start command which returns [OFF]
Stop, restart and status work as they should but start just returns [OFF]
I think this is to do with the runlevel as in SME 8 it was 7 now in SME 9 it is defaulted to runlevel 4
As a work-around for the moment I have used
ln -s /etc/init.d/firebird-superserver /etc/rc7.d/S99firebird-superserver
Anyone know correct command to use or point me to a solution?
Not really that important minor issue when you run the service it yields
# service firebird-superserver start
Starting Firebird server [default] /usr/bin/dirname: extra operand `-daemon'
Try `/usr/bin/dirname --help' for more information.
Found to solution to this at http://tracker.firebirdsql.org/browse/CORE-5069 (http://tracker.firebirdsql.org/browse/CORE-5069)
-
instead of using
config set firebird service...
you have to use
config set firebird-superserver service status enabled
and create the same links as above, naming them SXXfirebird-superserver
-
Alternatively you can keep everything with firebird and just create a link in init.t called firebird pointing to frebird-uperserver
-
instead of using
config set firebird service...
you have to use
config set firebird-superserver service status enabled
and create the same links as above, maning them SXXfirebird-suerserver
Thanks Stefano, I am building a new test server so will give it a try and an let you know.
If it works I will add to the wiki to help others that use Firebird.
Thanks again for you help.
Cheers, Trevor
-
Alternatively you can keep everything with firebird and just create a link in init.t called firebird pointing to frebird-uperserver
Thanks Jean-Philippe, I will give it a try on a new test server if it works will add to the wiki as an alternative way to fix the issue.
Will post back to in a few days and let all know what worked.
Cheers, Trevor
-
After testing I have gone with Stefano's answer as it would seem to be the best solution.
IE Post installation of Firebird Superserver
config set firebird-superserver service status enabled
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc7.d/S99firebird-superserver
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc1.d/S01firebird-superserver
ln -s /etc/rc.d/init.d/e-smith-service /etc/rc4.d/S99firebird-superserver
service firebird-superserver start
Jean-Philippe's solution will likely work but would require some extra work to implement.
Alternatively you can keep everything with firebird and just create a link in init.t called firebird pointing to frebird-uperserver
When you install firebird superserver and run the command
config set firebird service status enabled
it still create links with KXXfirebird-superserver and SXXfirebird-superserver not as you would expect KXXfirebird and SXXfirebird
Anyway thanks to all - I will update the wiki to hopefully help others
Cheers, Trevor