Hi Michael
What version of Koha is it?
Do you have errors or messages in the log files?
You can monitor them using tail. At first place I would have a look at
opac-error.log and plack-error.log,
something like: tail -f opac-error.log
Kind regards
Marc
Am 17.04.2017 um 23:20 schrieb Jonatha
Hi Michael,
A more general hint about mailing lists:
It seems that you started this thread by answering to a mail from an
other thread (Re: [Koha] [Koha-devel] What's on in koha-devel #11 Tue,
11 Apr 2017 21:49:51 +).
See https://lists.katipo.co.nz/pipermail/koha/2017-April/thread.html as
You can't yet. As I said, you should leave Zebra running. Koha will
update Elastic and Zebra.
Zebra still provides the Z3950 engine, and scripts that haven't been
ported to Elastic yet like the one you mention still need zebra
Chris
On 18/04/17 14:06, Abdulsalam Yousef wrote:
> So, How can we us
So, How can we use scripts like (link_bibs_to_authorities.pl) with
ElasticSearch?
When using it, We get this error
oAuth error: Connect failed (1)
unix:/var/run/koha/zebradb/authoritysocket ZOOM
On Mon, Apr 17, 2017 at 11:29 PM, Abdulsalam Yousef
wrote:
> Hello All,
>
> We would like to k
This is the output of curl -XGET "localhost:9200" command
{
"status" : 200,
"name" : "Hammerhead",
"cluster_name" : "elasticsearch",
"version" : {
"number" : "1.7.6",
"build_hash" : "c730b59357f8ebc555286794dcd90b3411f517c9",
"build_timestamp" : "2016-11-18T15:21:16Z",
"bui
In production I am not aware of something you could do (well there is
strace if you are patient and quick :D)
In test you could use a code profiler or tell mysql to log slow queries.
But the code profiler will be hazardous if it does not happens 100% of the
time and htop would have told you if mysq
Hi Jonathan
Some patrons have no issues/holds at all, some have very few (2 or 3),
some have some more. As I wrote the slow login process doesn't happen
all the time, but more or less often. At the moment we can't see a
pattern why it happens, but it does happen...
Is there maybe a way how t
Hi Abdulsalam
You don't need to touch those lines at all. ElasticSearch in Koha
doesn't use those lines for config (in fact you shouldn't touch them we
keep updating zebra as well as elastic currently)
Just add this to your config
localhost:9200
koha_robin
Below all the zeb
Hello All,
We would like to know the alternative path of
(authorityserver&biblioserver) in koha-conf.xml file for ElasticSearch
instead of the following Zebra path here
unix:/var/run/koha/zebradb/bibliosocket
unix:/var/run/koha/zebradb/authoritysocket
Thanks in advance.
_
Hello,
Which version of ES are you using? (curl -XGET "localhost:9200").
I can only tell you that it works with ES version 5 and master (no need to
test version 5 on 16.11, see bug 17255). I do not have a 16.11 install with
previous version of ES setup.
Regards,
Jonathan
On Mon, 17 Apr 2017 at 1
Hello All,
Concerning the Facets Show more previous problem with ElasticSearch, I've
noticed this error
(
[DEBUG][action.search.type ] [Professor Power] [koha_biblios][2],
node[3q5C0W4oQsa7Ovj2QMmj5w], [P], s[STARTED]: Failed to execute
[org.elasticsearch.action.search.SearchRequest@40bac79f]
Eric,
Thank you for sharing this list :-)
All the best,
Christopher Davis, MLS
Systems & E-Services Librarian
Uintah County Library
cgda...@uintah.utah.gov
(435) 789-0091 ext.261
uintahlibrary.org
basinlibraries.org
facebook.com/uintahcountylibrary
instagram.com/uintahcountylibrary
On Fri, Apr
Hello Michael,
How many issues and holds has the patron?
Regards,
Jonathan
On Thu, 13 Apr 2017 at 15:13 Michael Kuhn wrote:
> Hi
>
> We're running a new host with Debian GNU/Linux 8 and Koha 16.11.04.
>
> Usually the Koha OPAC login process is quick as expected. But sometimes
> when trying to
> Our librarian discovered that our patrons are not allowed to place holds on
> items, even though the feature is enabled.
Is this true of ALL items?
Do you have "On shelf holds allowed" enabled for the item types in
question? This setting might be in system preferences or in
Circulation and Fine
Excerpts from Abdulsalam Yousef's message of 2017-04-17 11:04:58 +0300:
> - Importing MARC records into catalog form (Manage staged MARC records) in
> staff client GUI using ElasticSearch engine is very slow and accidentally
> stops after importing some hundreds of records, That we may spend 3 days
Hi Yousef,
How much RAM is there on your server and how many CPU cores available to
you?
While the speed of import and indexing does depend on the server config, 3
days is way too much.
Regards
Indranil Das Gupta
L2C2 Technologies
On Apr 17, 2017 1:35 PM, "Abdulsalam Yousef" wrote:
> Hello all
Hello all,
- Importing MARC records into catalog form (Manage staged MARC records) in
staff client GUI using ElasticSearch engine is very slow and accidentally
stops after importing some hundreds of records, That we may spend 3 days to
import about 26000 record only, Is that normal? or there are a
17 matches
Mail list logo
