Firebird can't be started or shut down with '/etc/init.d/firebird start/stop', if the SYSDBA password is changed away from the default 'masterkey'. So it's useless to add it to the default runlevel. Starting with 'fbmgr.bin -start -forever -user sysdba -password <newsysdbapassword>', while logged in as user firebird, is possible.
Probable reason: "ISC_PASSWORD=masterkey" in /etc/conf.d/firebird.
Steps to Reproduce:
1.If the firebird server doesn't run, start it.
2.If the SYSDBA password is still 'masterkey', change it, using gsec.
3.Try to stop the server with '/etc/init.d/firebird stop' (as root).
Error message: Your user name and password are not defined. Ask your database administrator to set up a Firebird login. The server still runs (ps aux | grep fb shows this).
Similarly after reboot, '/etc/init.d/firebird start' doesn't start the server.
Server should start at '/etc/init.d/firebird start' and stop at '/etc/init.d/firebird stop'.
At _every_ start of the firebird server this message appears:
* Starting Firebird server ...
check /var/log/firebird/firebird.log file for errors
can not start server [ ok ]
So it's always necessary to check the real state of affairs with 'ps aux | grep fb' or by trying to connect to a database.
The file /etc/conf.d/firebird contains the line 'ISC_PASSWORD=masterkey'. If this is used by the start script I suppose that's the bug.
Well don't get me wrong, but have you actually ever tried to change the password in that *configuration* file once you've changed it in the database? Because that's the entire reason why the file is there in the first place.
(In reply to comment #1)
> Well don't get me wrong, but have you actually ever tried to change the
> password in that *configuration* file once you've changed it in the database?
> Because that's the entire reason why the file is there in the first place.
It's quite right that this works, but I don't think the SYSDBA password should be visible on the server quite this easily! I don't really understand why the start script doesn't work without the line 'export ISC_PASSWORD' - with fbmgr.bin the server can be started by user firebird without using the sysdba password at all. Reopening the bug, because a valid SYSDBA password in a text file really doesn't sound very secure for a production environment. Will be back when I hear more about this from the firebird support list.
(In reply to comment #2)
> It's quite right that this works, but I don't think the SYSDBA password should
> be visible on the server quite this easily!
Yeah, maybe you could check the file permissions before saying something is 'easily visible'.