root@www2:/home/user# koha-plack --enable library
Plack enabled for library
root@www2:/home/user# koha-plack --restart library
* Restarting Plack daemon for library
* Stopping Plack daemon for library
Two questions about Plack:
1. What is the concrete indicator that Plack is enabled and running or not?
2. I've looked at https://wiki.koha-community.org/wiki/Plack but: What
can be useful for plack in my setup or for me?
Recommended? Required? Extra? Only for developers?
Thank you.
El 19/03/18
Is it safe for data consistency to run this SQL command?
DELETE FROM koha_LibraryName.authorised_value_categories WHERE
category_name = "EmptyCategory";
El 20/03/18 a les 03:00, Irma Birchall ha escrit:
> Hi Narcis,
>
> At the moment there is no possibility to delete a category from the
> sta
Subject: Re: [Koha] Fw: Koha creating budget error
Date: Tue, 20 Mar 2018 06:46:02 + (UTC)
From: Asim Ullah
To: Katrin Fischer
i am using
Koha version: 17.11.03.000
perl version: 5.026000
apache version server version: 2.5.27
MySQL version: mysql Ver 15.1 Distrib 10.2.13-M
Excerpts from Narcis Garcia's message of 2018-03-20 10:38:26 +0100:
> 1. What is the concrete indicator that Plack is enabled and running or not?
In the "About Koha" page, immediately after the "Apache version:" line, you
should
see a line that looks like this:
PSGI: Plack (deployment)
___
This is the apache conf file that we use. Maybe someone can give a hint or
something, 'cause i'm running out of ideas. The "koha-plack --enable" does
not seem to do anything. If I run the disable command there are # placed in
front of the include. After enable the plack and restarting the apache th
Can anyone help verify if these queries will work? Don't have access to
system to verify and trying to help other Koha users complete these
questions on the PLDS Annual Survey.
/* calculate annual average days of circulation of items by item type */
SELECT r.itemtype, sum(r.datetime-b.datetime)/co
The important entry is the one for port 443. This one only does a redirect.
Is that generated by koha-create or a custom made apache file?
El mar., 20 mar. 2018 a las 10:18, JanM ()
escribió:
> This is the apache conf file that we use. Maybe someone can give a hint or
> something, 'cause i'm runn
I think it is a custom made file, but I don't know. I was asked to
administrate the server since the guy before me has left us.
What is important about the redirect? Is it the entry causing the fault?
Should it be deleted? Or should it be there, like without it, it would not
work.
--
Sent from:
Your eyes are on the :80 entry, but that entry redirects to another vhost
definition, using port 443. You need to look at the 443 vhost definition
for answers, as the port 80 one doesn't actually *server* Koha, it just
redirects.
El mar., 20 mar. 2018 a las 10:48, JanM ()
escribió:
> I think it i
Ok, gotcha.. I have two files, first:
Include /etc/koha/apache-shared.conf
# Include /etc/koha/apache-shared-disable.conf
Include /etc/koha/apache-shared-opac.conf
SSLCertificateFile /etc/ssl/certs/.pem
SSLCertificateKeyFile /etc/ssl/private/.pem
SSLCertificateChainFile /etc/
Right, that's what I thought.
You need to add the following:
Include /etc/koha/apache-shared-opac-plack.conf
above the line that says:
Include /etc/koha/apache-shared-opac.conf
And
Include /etc/koha/apache-shared-intranet-plack.conf
above the line that says:
Include /etc/koha/apache-sha
Ok, done that. After restarting the Apache it says:
/Service Unavailable
The server is temporarily unable to service your request due to maintenance
downtime or capacity problems. Please try again later./
in the Webbrowser.
Restart worked without errors. Also tried koha-plack --restart library
What is the OS version?
El mar., 20 mar. 2018 a las 11:24, JanM ()
escribió:
> Ok, done that. After restarting the Apache it says:
>
> /Service Unavailable
>
> The server is temporarily unable to service your request due to maintenance
> downtime or capacity problems. Please try again later./
>
>
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.4 LTS
Release:16.04
Codename: xenial
Koha-Version: 17.11.03.000
Perl-Version: 5.022001
Apache-Version: Server version: Apache/2.4.18 (Ubuntu)
MySQL-Version: mysql Ver 15.1 Distrib 10.0.34-MariaDB,
The best thing you could do, is regenerate the instance with sane clean
apache configuration files, and import the DB to the fresh instance. This
way, you will get your apache files patched on each upgrade, etc. This
hand-made files will cause you trouble in the future.
A workaround for your situa
And I like hazelnut cookies, BTW :-D
El mar., 20 mar. 2018 a las 11:35, Tomas Cohen Arazi ()
escribió:
> The best thing you could do, is regenerate the instance with sane clean
> apache configuration files, and import the DB to the fresh instance. This
> way, you will get your apache files patche
Oh man! I promis you will get invited for those cookies i we should meet us
one day. Thanks, that worked.
--
Sent from: http://koha.1045719.n5.nabble.com/Koha-general-f3047918.html
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.n
Check if you have any values for the category first, but if you haven't
used it yet, it should be safe.
On 20.03.2018 10:47, Narcis Garcia wrote:
Is it safe for data consistency to run this SQL command?
DELETE FROM koha_LibraryName.authorised_value_categories WHERE
category_name = "EmptyCateg
Hi Asim,
I have tested adding bugets on 17.11.03, but it worked without any
problems for me. I am using MySQL, which might or might not make a
difference.
The wiki recommends disabling the strict mode with your MariaDB version,
maybe this will help:
https://wiki.koha-community.org/wiki/Koh
20 matches
Mail list logo
