The init script for quasselcore starts before the backend, in my case PostgreSQL, and never finds the data. Reproducible: Always Steps to Reproduce: 1. Add quasselcore to start at machine start 2. Start Quassel Actual Results: Quassel will initiate the new core wizard because it can't find the database where the data is stored. Expected Results: Quassel should start without a problem. After the system has started and I hit the "new core" wizard, closing out of the wizard and restarting quasselcore resolves the problem.
Is there still a postgresql-base init script, or doesn't it exist in newer versions. If you use an init script for postgresql it should be enough to add "need $name-of-init-script" in the depend section of the quasselcore init-script. Problem is we need to depend on it conditionally as not everybody is using postgres but sqlite instead as database for quassel.
(In reply to comment #1) > Is there still a postgresql-base init script, or doesn't it exist in newer > versions. If you use an init script for postgresql it should be enough to add > "need $name-of-init-script" in the depend section of the quasselcore > init-script. Problem is we need to depend on it conditionally as not everybody > is using postgres but sqlite instead as database for quassel. > No, there is no -base script. There is the -server script, and I appended postgresql to the need line. That's what fixed the problem. A conditional would be easy to add. Probably just add a: # Uncomment the following line if quasselcore and the PostgreSQL Server # backend you are using reside on the same machine. USE_PGSQL="YES" to the conf, which would be commented out by default, of course.The conditional in the init could then check for that: if [[ USE_PGSQL == "YES" ]] ; then need net postgresql else need net fi
Thanks for your investigations. Is there anything else we need to consider? I don't use the postgres backend. @patrick: You have some experience with postgres, what do you think?
(In reply to comment #3) > Thanks for your investigations. > > Is there anything else we need to consider? I don't use the postgres backend. > > @patrick: You have some experience with postgres, what do you think? > Nope, there's nothing that we need to do on our end. There are other problems regarding Quassel and PostgreSQL, but those problems belong to upstream.
+ 28 Apr 2010; Daniel Pielmeier <billie@gentoo.org> + files/quasselcore-2.conf, files/quasselcore-2.init: + Add support for a local postgres backend to the init script to make the + database available when quasselcore starts up. Fixes bug #316799, thanks + to Aaron W. Swenson for reporting.