I'm building a new koha server to replace our old koha 3.0.0 with koha
16.5.4. The new server has better specs than the old one. Towards the end of
my work I started doing some basic testing of the screens compared to the
old system. I noticed the new system is slower (much slower) than our old
3.0
Yea i used sudo apt-get install koha-common
Thanks for that advice. I seen mentions of plack here and there but didn't
know much about it.
I enabled plack:
> sudo koha-plack --enable
> sudo koha-plack --start
and memcached:
> USE_MEMCACHED="yes"
> SetEnv MEMCACHED_SERVERS "127.0.0.1:11211"
> Se
I just started using plack yesterday and I ran the commands below to get
started. Everything was fine. The next morning I found that plack daemon was
not running. I needed to rerun both:
> sudo koha-plack --enable
> sudo koha-plack --start
Also, for a while now each morning I need to re-start z
Upgraded to koha 16.05.04 and debian 8.6 today
-my sessionStorage was mysql. I tried to change it to memcached to see if
any better.
-I checked and no crontab existed for /root/or the koha user on the server
Not sure how to determine exactly when plack and zebra are being killed.
--
View this m
I set the SessionStorage back to MySQL as it seems more reliable even through
reboots.
Thanks for letting me know about those other crons. I should have known
about those.
I see why you suspected logrotate as it shuts down and restarts plack and
zebra.
I manually triggered:
sudo logrotate -f /et
How does search weighting work in koha now?
In opac doing a default search (ie no advanced options) for: 'pete the cat'
returns
# 1 result
-> Moses *the *kitten / by James Herriot ; illustrated by *Pete*r Barrett.
# 11 result
-> *Pete the cat* : I love my white shoes / story by Eric Li
Assume a basic opac search:
http:///cgi-bin/koha/opac-search.pl?q=dog&branch_group_limit=branch%3A349
This would take about 10 seconds to return the first time.
Assume the user refreshes the results using f5 and keep there finger there a
moment to long (3s):
This would kill my server for abou
when I try to place a hold I see the msg in red: *Patron is from different
library*
This happens for all books even when the parton is from the correct library.
I checked the syspreferences and they seem to indicate that holds are setup
OK
How can I fix this
->koha 16.11.02
--
View this message
My problem is related to koha permissions. I doubt anyone has delt with this
situation, so I'll try to explain the problem.
I recently took over the support of the koha system that takes care of all
the schools for my province. We are using koha 3.0 that has customizations.
Because of these custom
Fixed. Koha 3.2.10 contains some bugs in the reports files. Specifically
guided_reports.pl has a typo execute_report instead of execute_reports. that
typo was causing my problems with permissions.
--
View this message in context:
http://koha.1045719.n5.nabble.com/Upgrade-reports-from-3-0-to-3-2-1
My koha search no longer works after upgrading from 3.00.01.005 to
3.08.01.002. First I'll explain the details of my upgrade from July 6, 2012:
*PART1: details of my upgrade*
1) On a new server I created a new Debian 6 Squeeze installation on VMware.
2) I installed Koha using apt-get
3) I uploade
Hi,
the url is like this after a search with a branch selected:
http://kohapeiadmin/cgi-bin/koha/catalogue/search.pl?idx=kw&q=math&idx=kw&idx=kw&limit=branch%3A314&sort_by=relevance
notice it sets the branch based on number.
however koha translates that to the name of the school and spits out thi
Hi Eric,
I checked and the holdingbranch and homebranch in the items table for
records at bluefield high are 314. Other records will use the code for the
corresponding school where the book is located. Eg. books at Birchwood
Intermediate School have 320 as the code, and so on for each of the 64
br
Our system uses 090 tags instead of the default 952 tags for items...could
this be related to why my search is screwed up? If I choose
administration->koha to MARC mapping these are the options that are set
under items:
Koha field Tag SubfieldLib
itemnumber 090 g
Hi,
I'm doing some investigation into the space usage on my server and noticed
the following take the most space:
7.0 G *** ./var/lib/mysql
8.6 G
./var/lib/koha/kohapei/biblios/register
9.3 G
Using koha 3.10.4
If I run a 'MARC bibliographic framework test' I get this:
--
MARC bibliographic framework test
TestResult
itemnum
The field itemnum MUST be mapped
The corresponding subfield MUST be in with -1 (ignore) tab
OK All item fields are in the same tag
This is probably to specific a problem to be useful to anyone but here goes:
This problem was caused by a bug in how 'Toad For mysql' deals with tiny int
values in version 6.3.0.642. When I exported marc_subfield_structure from a
clean koha and imported into my upgraded koha I got the error above.
setting virtualshelves = 'don't allow' causes no changes in the staff client.
users can still see the 'lists' option and create/view lists. virtualshelves
= 'don't allow' should make completely remove lists from the staff client
everything seems to work fine with this setting in the opac
--
Vie
This problem was found in versions:
3.10.04.000
3.11.00.202
--
View this message in context:
http://koha.1045719.n5.nabble.com/Bug-virtualshelves-permisssion-broken-in-staff-client-tp5753457p5753481.html
Sent from the Koha-general mailing list archive at Nabble.com.
19 matches
Mail list logo