koha-index-daemon-ctl.sh is a init script for koha-index-daemon from Koha::Contrib::Tamil::IndexerDaemon. When starting system, this script needs to be started after the MySQL server because it uses it to access to Koha database.
Created attachment 19992 [details] [review] Bug 10665 - koha-index-daemon-ctl.sh needs mysql dependency Proposed patch. Without this patch, the log file show on startup : DBD::mysql::st execute failed: MySQL server has gone away at /usr/local/share/perl/5.14.2/Koha/Contrib/Tamil/IndexerDaemon.pm line 71. DBD::mysql::st fetchrow failed: fetch() without execute() at /usr/local/share/perl/5.14.2/Koha/Contrib/Tamil/IndexerDaemon.pm line 73.
Created attachment 20009 [details] [review] Bug 10665 - koha-index-daemon-ctl.sh dependency I revised patch because indexer may use a remote MySQL server and so the dependency on $mysql may not be possible. I changed for $all as dependency at startup.
Created attachment 20193 [details] [review] Bug 10665 - koha-index-daemon-ctl.sh dependency The daemon koha-index-daemon needs a connexion to MySQL server. This patch sets start dependance to "all" in order to wait for local MySQL server or not wait if using a remote MySQL server. Signed-off-by: Bernardo Gonzalez Kriegel <bgkriegel@gmail.com> Small fix, no errors.
Looks like a small change - is there an easy way to verify the effect?
Created attachment 21074 [details] [review] Bug 10665 - koha-index-daemon-ctl.sh dependency The daemon koha-index-daemon needs a connexion to MySQL server. This patch sets start dependance to "all" in order to wait for local MySQL server or not wait if using a remote MySQL server. Signed-off-by: Bernardo Gonzalez Kriegel <bgkriegel@gmail.com> Small fix, no errors. Signed-off-by: Mason James <mtj@kohaaloha.com>
(In reply to Katrin Fischer from comment #4) > Looks like a small change - is there an easy way to verify the effect? hmmmmm, a great question! ^^
We've had an indexing daemon in koha for years now.. do we really still need this confusing/misleading script in community koha at all? I've opened a new bug to discuss #23241 and am going to mark this one as wontfix.