Re: [Koha-devel] 3.18 install [was: koha-common install]
At 09:07 AM 12/30/2014 +1300, Chris Cormack wrote: [snip]
It is because you decided not to install using the packages, and instead used the tarball, so none of the package supplied scripts will be there
Yup... I tried four times (twice on a 32-bit sandbox, and twice on a new 64-bit machine due to go into production soon), reinstalling the whole server from scratch each time, and coha-common failed every time. So I went back to my notes from Koha 3.8 and used the tarball for 3.18.2. Do you have a list of the "package supplied scripts" not in the tarball? That would be most useful for me to chase down any final "missing advantages" of 3.18 -- our staff are excited at getting their hands on the "new version." Anyways I'm getting closer. The Zebra failure was that the daemon wasn't running, cured with a: paul@hood:/etc/init.d$ sudo ln -s /usr/share/koha/bin/koha-zebra-ctl.sh koha-zebra-daemon paul@hood:/etc/init.d$ sudo /etc/init.d/koha-zebra-daemon start Starting Zebra Server Bingo! OPAC and Staff now functional.
Regarding the "package supplied scripts", you can see the list here: http://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_packages It seems a shame to use the tarball when you're on Ubuntu though. What instructions did you use for installing the packages? It looks like you ran into the problem described here: http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Some_difficult ies_were_encountered_installing_apache2-mpm-itk. I recently ran into that problem myself when setting up Koha in Ubuntu 14.04 (although I was using the koha-deps and koha-perldeps packages rather than koha-common for a different kind of install). My suggestion would be to run the following: sudo apt-get install apache2 sudo a2dismod mpm_event sudo a2enmod mpm_prefork sudo service apache2 restart sudo apt-get install koha-common That way, you won't get those errors when you install " apache2-mpm-itk" as part of "koha-common" resolving its dependencies. If you don't like the idea of Koha automatically upgrading when new versions are released, you could also take a look at holding the package: https://help.ubuntu.com/community/PinningHowto#Introduction_to_Holding_Packa ges David Cook Systems Librarian Prosentient Systems 72/330 Wattle St, Ultimo, NSW 2007
-----Original Message----- From: koha-devel-bounces@lists.koha-community.org [mailto:koha-devel- bounces@lists.koha-community.org] On Behalf Of Paul A Sent: Tuesday, 30 December 2014 8:45 AM To: koha-devel@lists.koha-community.org Subject: Re: [Koha-devel] 3.18 install [was: koha-common install]
At 09:07 AM 12/30/2014 +1300, Chris Cormack wrote: [snip]
It is because you decided not to install using the packages, and instead used the tarball, so none of the package supplied scripts will be there
Yup... I tried four times (twice on a 32-bit sandbox, and twice on a new 64-bit machine due to go into production soon), reinstalling the whole server from scratch each time, and coha-common failed every time. So I went back to my notes from Koha 3.8 and used the tarball for 3.18.2.
Do you have a list of the "package supplied scripts" not in the tarball? That would be most useful for me to chase down any final "missing advantages" of 3.18 -- our staff are excited at getting their hands on the "new version."
Anyways I'm getting closer. The Zebra failure was that the daemon wasn't running, cured with a: paul@hood:/etc/init.d$ sudo ln -s /usr/share/koha/bin/koha-zebra-ctl.sh koha-zebra-daemon paul@hood:/etc/init.d$ sudo /etc/init.d/koha-zebra-daemon start Starting Zebra Server
Bingo! OPAC and Staff now functional.
_______________________________________________ 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/
participants (2)
-
David Cook -
Paul A