I'm not sure which is the best solution, because this would break the setup for people using remote DB servers. I'd fill a bug on Koha::Contrib::Tamil asking for the indexer to recover when the DB server is available again. Talk to Frederic about this.


On Wed, Jul 31, 2013 at 5:21 AM, Fridolyn SOMERS <fridolyn.somers@biblibre.com> wrote:
I think the koha-index-daemon needs to be dependent on MySQL server starting.
I created a bug for that : Bug 10665.

Le 29/06/2013 22:06, Partha Mukhopadhyay a écrit :
Dear all

Reporting a problem for koha-index-daemon (Koha 3.12.01 on Ubuntu 12.04):

1. Evertime I restart computer I need to manually start koha-index-daemon
although i've used following instructions:

sudo ln -s /usr/share/koha/bin/koha-index-daemon-ctl.sh /etc/init.d/koha-index-daemon
sudo update-rc.d koha-index-daemon defaults
sudo service koha-index-daemon start

2. The log file (koha-index-daemon.err):

20130629 03:05:15 koha-index-daemon-koha: client (pid 2650) killed by signal 15, respawning
20130629 03:06:46 koha-index-daemon-koha: client (pid 2682) killed by signal 15, stopping
20130629 08:10:38 koha-index-daemon-koha: client (pid 2623) killed by signal 15, respawning
20130629 09:51:05 koha-index-daemon-koha: client (pid 2642) killed by signal 15, stopping
20130630 00:18:21 koha-index-daemon-koha: client (pid 3580) killed by signal 15, respawning
20130630 00:46:04 koha-index-daemon-koha: client (pid 3599) killed by signal 15, stopping
20130630 00:56:46 koha-index-daemon-koha: client (pid 4037) killed by signal 15, stopping
20130630 00:56:53 koha-index-daemon-koha: client (pid 4072) killed by signal 15, respawning
20130630 00:58:38 koha-index-daemon-koha: client (pid 4091) killed by signal 15, stopping
20130630 01:03:42 koha-index-daemon-koha: client (pid 2610) killed by signal 15, respawning
20130630 01:04:17 koha-index-daemon-koha: client (pid 2629) killed by signal 15, stopping
20130630 01:06:11 koha-index-daemon-koha: client (pid 2551) killed by signal 15, respawning
20130630 01:17:39 koha-index-daemon-koha: client (pid 2568) killed by signal 15, respawning

3. the output log:

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.
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.

when i start it manually ebverything works fine.

Pl help....

Partha

----------------------------------------------------

Dr. Parthasarathi Mukhopadhyay

Associate Prof.

Department of Library and Information Science

University of Kalyani (WB, India)

------------------------------------------



_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/


--
Fridolyn SOMERS
Biblibre - Pôle support
fridolyn.somers@biblibre.com

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/