Wiping all partial or full Koha isntallation(s) and installing stable under Mint
I have a virtual machine that may have two conflicting Koha installations. What, if anything, can I do that will wipe all Koha installations completely, and install a new stable from scratch, following https://wiki.koha-community.org/wiki/Debian? I don't know if I *exactly* need to go so far as to delete details like the Koha repository in aptitude... but I am willing to do so if I am advised. I do think it would be better to wipe any Koha-created directory heirarchies, and drop any Koha-related databases. (Note: My system doesn't contain any valuable information *in* Koha; the only loss would be the time and energy to delete and rebuild the installation.) -- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website <https://cjshayward.com/>.
If you installed using the packages I believe you can use koha-remove . See here: https://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_package... Doug -----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of C.J.S. Hayward Sent: Tuesday, July 25, 2017 11:18 AM To: koha@lists.katipo.co.nz Subject: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint I have a virtual machine that may have two conflicting Koha installations. What, if anything, can I do that will wipe all Koha installations completely, and install a new stable from scratch, following https://wiki.koha-community.org/wiki/Debian? I don't know if I *exactly* need to go so far as to delete details like the Koha repository in aptitude... but I am willing to do so if I am advised. I do think it would be better to wipe any Koha-created directory heirarchies, and drop any Koha-related databases. (Note: My system doesn't contain any valuable information *in* Koha; the only loss would be the time and energy to delete and rebuild the installation.) -- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website <https://cjshayward.com/>. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Thank you. I've used koha-remove, and uninstalled and reinstalled koha-common, including setting an a2enmod. Right now I have an /etc/koha heirarchy that has a lot of stuff in it, but /etc/koha/sites is an empty directory *after* trying to run "koha-create library": toolchest sites # koha-create library failed to load external entity "/etc/koha/sites/library/koha-conf.xml" How can I create or get an appropriate koha-conf.xml? I notice that there is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing to ideally transform it to make /etc/koha/sites/library/koha-conf.xml (and anything else that should be in /etc/koha/sites/library/)? On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden <dearden@sarsf.org> wrote:
If you installed using the packages I believe you can use koha-remove . See here: https://wiki.koha-community.org/wiki/Commands_provided_by_ the_Debian_packages#koha-remove
Doug
-----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of C.J.S. Hayward Sent: Tuesday, July 25, 2017 11:18 AM To: koha@lists.katipo.co.nz Subject: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint
I have a virtual machine that may have two conflicting Koha installations.
What, if anything, can I do that will wipe all Koha installations completely, and install a new stable from scratch, following https://wiki.koha-community.org/wiki/Debian?
I don't know if I *exactly* need to go so far as to delete details like the Koha repository in aptitude... but I am willing to do so if I am advised. I do think it would be better to wipe any Koha-created directory heirarchies, and drop any Koha-related databases.
(Note: My system doesn't contain any valuable information *in* Koha; the only loss would be the time and energy to delete and rebuild the installation.)
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website <https://cjshayward.com/>. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website <https://cjshayward.com/>.
Try with --create-db: koha-create --create-db library The doc says that --create-db is the default value, but it does not seem to work. Could you report the bug? On Tue, 25 Jul 2017 at 15:36 C.J.S. Hayward <cjsh@cjshayward.com> wrote:
Thank you. I've used koha-remove, and uninstalled and reinstalled koha-common, including setting an a2enmod.
Right now I have an /etc/koha heirarchy that has a lot of stuff in it, but /etc/koha/sites is an empty directory *after* trying to run "koha-create library":
toolchest sites # koha-create library failed to load external entity "/etc/koha/sites/library/koha-conf.xml"
How can I create or get an appropriate koha-conf.xml? I notice that there is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing to ideally transform it to make /etc/koha/sites/library/koha-conf.xml (and anything else that should be in /etc/koha/sites/library/)?
On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden <dearden@sarsf.org> wrote:
If you installed using the packages I believe you can use koha-remove . See here: https://wiki.koha-community.org/wiki/Commands_provided_by_ the_Debian_packages#koha-remove
Doug
-----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of C.J.S. Hayward Sent: Tuesday, July 25, 2017 11:18 AM To: koha@lists.katipo.co.nz Subject: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint
I have a virtual machine that may have two conflicting Koha installations.
What, if anything, can I do that will wipe all Koha installations completely, and install a new stable from scratch, following https://wiki.koha-community.org/wiki/Debian?
I don't know if I *exactly* need to go so far as to delete details like the Koha repository in aptitude... but I am willing to do so if I am advised. I do think it would be better to wipe any Koha-created directory heirarchies, and drop any Koha-related databases.
(Note: My system doesn't contain any valuable information *in* Koha; the only loss would be the time and energy to delete and rebuild the installation.)
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website <https://cjshayward.com/ . _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website <https://cjshayward.com/>. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Let me send off this email, and I'll report a bug. N.B. Koha is installed in some sense, but when I try to access the webinstaller I got maintenance mode: System Maintenance The Koha online catalog is offline for system maintenance. We'll be back soon! If you have any questions, please contact the site administrator A brief search turned up https://lists.katipo.co.nz/public/koha/2013-December/038208.html which picked up in a possible email typo specifying a port as 8008. This suggestion appears to be irrelevant because if the OP had tried to access Koha on 8008 and hadn't added anything else listening on that port, the error would be "Connection refused", not "System maintenance". On Tue, Jul 25, 2017 at 10:02 PM, Jonathan Druart < jonathan.druart@bugs.koha-community.org> wrote:
Try with --create-db: koha-create --create-db library
The doc says that --create-db is the default value, but it does not seem to work. Could you report the bug?
On Tue, 25 Jul 2017 at 15:36 C.J.S. Hayward <cjsh@cjshayward.com> wrote:
Thank you. I've used koha-remove, and uninstalled and reinstalled koha-common, including setting an a2enmod.
Right now I have an /etc/koha heirarchy that has a lot of stuff in it, but /etc/koha/sites is an empty directory *after* trying to run "koha-create library":
toolchest sites # koha-create library failed to load external entity "/etc/koha/sites/library/koha-conf.xml"
How can I create or get an appropriate koha-conf.xml? I notice that there is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing to ideally transform it to make /etc/koha/sites/library/koha-conf.xml (and anything else that should be in /etc/koha/sites/library/)?
On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden <dearden@sarsf.org> wrote:
If you installed using the packages I believe you can use koha-remove . See here: https://wiki.koha-community.org/wiki/Commands_provided_by_ the_Debian_packages#koha-remove
Doug
-----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of C.J.S. Hayward Sent: Tuesday, July 25, 2017 11:18 AM To: koha@lists.katipo.co.nz Subject: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint
I have a virtual machine that may have two conflicting Koha installations.
What, if anything, can I do that will wipe all Koha installations completely, and install a new stable from scratch, following https://wiki.koha-community.org/wiki/Debian?
I don't know if I *exactly* need to go so far as to delete details like the Koha repository in aptitude... but I am willing to do so if I am advised. I do think it would be better to wipe any Koha-created directory heirarchies, and drop any Koha-related databases.
(Note: My system doesn't contain any valuable information *in* Koha; the only loss would be the time and energy to delete and rebuild the installation.)
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website < https://cjshayward.com/ . _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website <https://cjshayward.com/ . _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website <https://cjshayward.com/>.
I've filed a bug at https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18983 On Tue, Jul 25, 2017 at 11:17 PM, C.J.S. Hayward <cjsh@cjshayward.com> wrote:
Let me send off this email, and I'll report a bug.
N.B. Koha is installed in some sense, but when I try to access the webinstaller I got maintenance mode:
System Maintenance
The Koha online catalog is offline for system maintenance. We'll be back soon! If you have any questions, please contact the site administrator
A brief search turned up https://lists.katipo.co.nz/ public/koha/2013-December/038208.html which picked up in a possible email typo specifying a port as 8008. This suggestion appears to be irrelevant because if the OP had tried to access Koha on 8008 and hadn't added anything else listening on that port, the error would be "Connection refused", not "System maintenance".
On Tue, Jul 25, 2017 at 10:02 PM, Jonathan Druart < jonathan.druart@bugs.koha-community.org> wrote:
Try with --create-db: koha-create --create-db library
The doc says that --create-db is the default value, but it does not seem to work. Could you report the bug?
On Tue, 25 Jul 2017 at 15:36 C.J.S. Hayward <cjsh@cjshayward.com> wrote:
Thank you. I've used koha-remove, and uninstalled and reinstalled koha-common, including setting an a2enmod.
Right now I have an /etc/koha heirarchy that has a lot of stuff in it, but /etc/koha/sites is an empty directory *after* trying to run "koha-create library":
toolchest sites # koha-create library failed to load external entity "/etc/koha/sites/library/koha-conf.xml"
How can I create or get an appropriate koha-conf.xml? I notice that there is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing to ideally transform it to make /etc/koha/sites/library/koha-conf.xml (and anything else that should be in /etc/koha/sites/library/)?
On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden <dearden@sarsf.org> wrote:
If you installed using the packages I believe you can use koha-remove . See here: https://wiki.koha-community.org/wiki/Commands_provided_by_ the_Debian_packages#koha-remove
Doug
-----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of C.J.S. Hayward Sent: Tuesday, July 25, 2017 11:18 AM To: koha@lists.katipo.co.nz Subject: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint
I have a virtual machine that may have two conflicting Koha installations.
What, if anything, can I do that will wipe all Koha installations completely, and install a new stable from scratch, following https://wiki.koha-community.org/wiki/Debian?
I don't know if I *exactly* need to go so far as to delete details like the Koha repository in aptitude... but I am willing to do so if I am advised. I do think it would be better to wipe any Koha-created directory heirarchies, and drop any Koha-related databases.
(Note: My system doesn't contain any valuable information *in* Koha; the only loss would be the time and energy to delete and rebuild the installation.)
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website < https://cjshayward.com/ . _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website < https://cjshayward.com/>. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website <https://cjshayward.com/>.
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website <https://cjshayward.com/>.
If you reach the "system maintenance" screen that means you are hitting the OPAC interface, not the staff interface. Try on :8080 On Tue, 25 Jul 2017 at 17:17 C.J.S. Hayward <cjsh@cjshayward.com> wrote:
Let me send off this email, and I'll report a bug.
N.B. Koha is installed in some sense, but when I try to access the webinstaller I got maintenance mode:
System Maintenance
The Koha online catalog is offline for system maintenance. We'll be back soon! If you have any questions, please contact the site administrator
A brief search turned up https://lists.katipo.co.nz/public/koha/2013-December/038208.html which picked up in a possible email typo specifying a port as 8008. This suggestion appears to be irrelevant because if the OP had tried to access Koha on 8008 and hadn't added anything else listening on that port, the error would be "Connection refused", not "System maintenance".
On Tue, Jul 25, 2017 at 10:02 PM, Jonathan Druart < jonathan.druart@bugs.koha-community.org> wrote:
Try with --create-db: koha-create --create-db library
The doc says that --create-db is the default value, but it does not seem to work. Could you report the bug?
On Tue, 25 Jul 2017 at 15:36 C.J.S. Hayward <cjsh@cjshayward.com> wrote:
Thank you. I've used koha-remove, and uninstalled and reinstalled koha-common, including setting an a2enmod.
Right now I have an /etc/koha heirarchy that has a lot of stuff in it, but /etc/koha/sites is an empty directory *after* trying to run "koha-create library":
toolchest sites # koha-create library failed to load external entity "/etc/koha/sites/library/koha-conf.xml"
How can I create or get an appropriate koha-conf.xml? I notice that there is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing to ideally transform it to make /etc/koha/sites/library/koha-conf.xml (and anything else that should be in /etc/koha/sites/library/)?
On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden <dearden@sarsf.org> wrote:
If you installed using the packages I believe you can use koha-remove . See here: https://wiki.koha-community.org/wiki/Commands_provided_by_ the_Debian_packages#koha-remove
Doug
-----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of C.J.S. Hayward Sent: Tuesday, July 25, 2017 11:18 AM To: koha@lists.katipo.co.nz Subject: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint
I have a virtual machine that may have two conflicting Koha installations.
What, if anything, can I do that will wipe all Koha installations completely, and install a new stable from scratch, following https://wiki.koha-community.org/wiki/Debian?
I don't know if I *exactly* need to go so far as to delete details like the Koha repository in aptitude... but I am willing to do so if I am advised. I do think it would be better to wipe any Koha-created directory heirarchies, and drop any Koha-related databases.
(Note: My system doesn't contain any valuable information *in* Koha; the only loss would be the time and energy to delete and rebuild the installation.)
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website < https://cjshayward.com/ . _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website < https://cjshayward.com/>. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website <https://cjshayward.com/>.
Thank you. This server is multipurpose and has multiple webapps that listen on 8080 by default. My library entry in /etc/apache2/sites-enables reads, with /etc/hosts assigning "opac" and "library" to 127.0.0.1: # Koha instance library Apache config. # OPAC Listen 7027 <VirtualHost *:7027> <IfVersion >= 2.4> Define instance "library" </IfVersion> Include /etc/koha/apache-shared.conf # Include /etc/koha/apache-shared-disable.conf # Include /etc/koha/apache-shared-opac-plack.conf Include /etc/koha/apache-shared-opac.conf ServerName opac SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml" AssignUserID library-koha library-koha ErrorLog /var/log/koha/library/opac-error.log # TransferLog /var/log/koha/library/opac-access.log # RewriteLog /var/log/koha/library/opac-rewrite.log </VirtualHost> # Intranet Listen 7028 <VirtualHost *:7028> <IfVersion >= 2.4> Define instance "library" </IfVersion> Include /etc/koha/apache-shared.conf # Include /etc/koha/apache-shared-disable.conf # Include /etc/koha/apache-shared-intranet-plack.conf Include /etc/koha/apache-shared-intranet.conf ServerName intranet SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml" AssignUserID library-koha library-koha ErrorLog /var/log/koha/library/intranet-error.log # TransferLog /var/log/koha/library/intranet-access.log # RewriteLog /var/log/koha/library/intranet-rewrite.log </VirtualHost> ~ I had earlier tried to access opac:7027 and got the reported error. Now I am trying to access intranet:7028 and I can't tell a difference. Do I need to be doing more if I reassign port numbers? Thanks, On Tue, Jul 25, 2017 at 11:47 PM, Jonathan Druart < jonathan.druart@bugs.koha-community.org> wrote:
If you reach the "system maintenance" screen that means you are hitting the OPAC interface, not the staff interface. Try on :8080
On Tue, 25 Jul 2017 at 17:17 C.J.S. Hayward <cjsh@cjshayward.com> wrote:
Let me send off this email, and I'll report a bug.
N.B. Koha is installed in some sense, but when I try to access the webinstaller I got maintenance mode:
System Maintenance
The Koha online catalog is offline for system maintenance. We'll be back soon! If you have any questions, please contact the site administrator
A brief search turned up https://lists.katipo.co.nz/public/koha/2013-December/038208.html which picked up in a possible email typo specifying a port as 8008. This suggestion appears to be irrelevant because if the OP had tried to access Koha on 8008 and hadn't added anything else listening on that port, the error would be "Connection refused", not "System maintenance".
On Tue, Jul 25, 2017 at 10:02 PM, Jonathan Druart < jonathan.druart@bugs.koha-community.org> wrote:
Try with --create-db: koha-create --create-db library
The doc says that --create-db is the default value, but it does not seem to work. Could you report the bug?
On Tue, 25 Jul 2017 at 15:36 C.J.S. Hayward <cjsh@cjshayward.com> wrote:
Thank you. I've used koha-remove, and uninstalled and reinstalled koha-common, including setting an a2enmod.
Right now I have an /etc/koha heirarchy that has a lot of stuff in it, but /etc/koha/sites is an empty directory *after* trying to run "koha-create library":
toolchest sites # koha-create library failed to load external entity "/etc/koha/sites/library/koha- conf.xml"
How can I create or get an appropriate koha-conf.xml? I notice that there is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing to ideally transform it to make /etc/koha/sites/library/koha-conf.xml (and anything else that should be in /etc/koha/sites/library/)?
On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden <dearden@sarsf.org> wrote:
If you installed using the packages I believe you can use koha-remove . See here: https://wiki.koha-community. org/wiki/Commands_provided_by_ the_Debian_packages#koha-remove
Doug
-----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of C.J.S. Hayward Sent: Tuesday, July 25, 2017 11:18 AM To: koha@lists.katipo.co.nz Subject: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint
I have a virtual machine that may have two conflicting Koha installations.
What, if anything, can I do that will wipe all Koha installations completely, and install a new stable from scratch, following https://wiki.koha-community.org/wiki/Debian?
I don't know if I *exactly* need to go so far as to delete details like the Koha repository in aptitude... but I am willing to do so if I am advised. I do think it would be better to wipe any Koha-created directory heirarchies, and drop any Koha-related databases.
(Note: My system doesn't contain any valuable information *in* Koha; the only loss would be the time and energy to delete and rebuild the installation.)
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website < https://cjshayward.com/ . _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website < https://cjshayward.com/>. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website <https://cjshayward.com/ .
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website <https://cjshayward.com/>.
I think the 2 "Listen" lines should go to ports.conf On Tue, 25 Jul 2017 at 18:11 C.J.S. Hayward <cjsh@cjshayward.com> wrote:
Thank you. This server is multipurpose and has multiple webapps that listen on 8080 by default. My library entry in /etc/apache2/sites-enables reads, with /etc/hosts assigning "opac" and "library" to 127.0.0.1:
# Koha instance library Apache config.
# OPAC
Listen 7027 <VirtualHost *:7027> <IfVersion >= 2.4> Define instance "library" </IfVersion> Include /etc/koha/apache-shared.conf # Include /etc/koha/apache-shared-disable.conf # Include /etc/koha/apache-shared-opac-plack.conf Include /etc/koha/apache-shared-opac.conf
ServerName opac SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml" AssignUserID library-koha library-koha
ErrorLog /var/log/koha/library/opac-error.log # TransferLog /var/log/koha/library/opac-access.log # RewriteLog /var/log/koha/library/opac-rewrite.log </VirtualHost>
# Intranet Listen 7028 <VirtualHost *:7028> <IfVersion >= 2.4> Define instance "library" </IfVersion> Include /etc/koha/apache-shared.conf # Include /etc/koha/apache-shared-disable.conf # Include /etc/koha/apache-shared-intranet-plack.conf Include /etc/koha/apache-shared-intranet.conf
ServerName intranet SetEnv KOHA_CONF "/etc/koha/sites/library/koha-conf.xml" AssignUserID library-koha library-koha
ErrorLog /var/log/koha/library/intranet-error.log # TransferLog /var/log/koha/library/intranet-access.log # RewriteLog /var/log/koha/library/intranet-rewrite.log </VirtualHost> ~
I had earlier tried to access opac:7027 and got the reported error. Now I am trying to access intranet:7028 and I can't tell a difference.
Do I need to be doing more if I reassign port numbers?
Thanks,
On Tue, Jul 25, 2017 at 11:47 PM, Jonathan Druart < jonathan.druart@bugs.koha-community.org> wrote:
If you reach the "system maintenance" screen that means you are hitting the OPAC interface, not the staff interface. Try on :8080
On Tue, 25 Jul 2017 at 17:17 C.J.S. Hayward <cjsh@cjshayward.com> wrote:
Let me send off this email, and I'll report a bug.
N.B. Koha is installed in some sense, but when I try to access the webinstaller I got maintenance mode:
System Maintenance
The Koha online catalog is offline for system maintenance. We'll be back soon! If you have any questions, please contact the site administrator
A brief search turned up https://lists.katipo.co.nz/public/koha/2013-December/038208.html which picked up in a possible email typo specifying a port as 8008. This suggestion appears to be irrelevant because if the OP had tried to access Koha on 8008 and hadn't added anything else listening on that port, the error would be "Connection refused", not "System maintenance".
On Tue, Jul 25, 2017 at 10:02 PM, Jonathan Druart < jonathan.druart@bugs.koha-community.org> wrote:
Try with --create-db: koha-create --create-db library
The doc says that --create-db is the default value, but it does not seem to work. Could you report the bug?
On Tue, 25 Jul 2017 at 15:36 C.J.S. Hayward <cjsh@cjshayward.com> wrote:
Thank you. I've used koha-remove, and uninstalled and reinstalled koha-common, including setting an a2enmod.
Right now I have an /etc/koha heirarchy that has a lot of stuff in it, but /etc/koha/sites is an empty directory *after* trying to run "koha-create library":
toolchest sites # koha-create library failed to load external entity "/etc/koha/sites/library/koha-conf.xml"
How can I create or get an appropriate koha-conf.xml? I notice that there is an /etc/koha/koha-conf-site.xml.in; what can or should I be doing to ideally transform it to make /etc/koha/sites/library/koha-conf.xml (and anything else that should be in /etc/koha/sites/library/)?
On Tue, Jul 25, 2017 at 8:46 PM, Doug Dearden <dearden@sarsf.org> wrote:
If you installed using the packages I believe you can use koha-remove . See here: https://wiki.koha-community.org/wiki/Commands_provided_by_ the_Debian_packages#koha-remove
Doug
-----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of C.J.S. Hayward Sent: Tuesday, July 25, 2017 11:18 AM To: koha@lists.katipo.co.nz Subject: [Koha] Wiping all partial or full Koha isntallation(s) and installing stable under Mint
I have a virtual machine that may have two conflicting Koha installations.
What, if anything, can I do that will wipe all Koha installations completely, and install a new stable from scratch, following https://wiki.koha-community.org/wiki/Debian?
I don't know if I *exactly* need to go so far as to delete details like the Koha repository in aptitude... but I am willing to do so if I am advised. I do think it would be better to wipe any Koha-created directory heirarchies, and drop any Koha-related databases.
(Note: My system doesn't contain any valuable information *in* Koha; the only loss would be the time and energy to delete and rebuild the installation.)
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website < https://cjshayward.com/ . _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website < https://cjshayward.com/>. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website < https://cjshayward.com/>.
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- christos Jonathan Seth Hayward, An Orthodox Christian author. Amazon <http://amazon.com/author/cjshayward> - email <christos.jonathan.hayward@gmail.com> - website <https://cjshayward.com/>.
participants (3)
-
C.J.S. Hayward -
Doug Dearden -
Jonathan Druart