Thank you very much, Martin (and Katrin again)!
I reverted to my previous Ubuntu/Debian repository configuration, as
Martin kindly suggested, and performed an apt update/upgrade.
Nothing changed: as said, Koha looked as if it was already up-to-date.
But this time I finally noticed that a
Hi Giuseppe,
I think wires have been crossed a little here, you didn't need to switch to
oldoldstable.. that's the Koha codename. you have two codenames in there..
one for the OS you're running on and one for the Koha version you wish to
follow.
I'd stick to 'stable' for the Koha version and
Thanks, Katrin.
I did as suggested in the webpage you kindly pointed out, and, since I am
using Ubuntu 18.04 bionic, inserted oldoldstable in my koha.list file
But I think it's too late, since the previous updates have upgraded my
Koha installation to version 22.05.00.000, which is a more
Hi Giuseppe,
I believe you might have to change the entry in koha.list as you are
using an older Ubuntu version:
https://wiki.koha-community.org/wiki/Koha_on_Debian#Support_for_Koha_on_older_versions_of_Debian.2FUbuntu_.28Debian_8.2C_Ubuntu_18.04.2C_Ubuntu_16.04.29
I am not sure what the exact
Hi, Katrin.
You have a package installation on Ubuntu 18.04 LTS?
Yes, correct.
What does your entry in etc/apt/sources.list.d/koha.list look like?
The above file reads:
deb http://debian.koha-community.org/koha stable main
Many thanks!
Giuseppe.
Hi Guiseppe,
these system preferences have a different purpose. The internally used
API routes should work without changing any configuration. This is most
likely to be an installation/dependency issue.
The acquisition error you reported also points in this direction, it's
all symptoms of the
Hi, Katrin.
the patron search in 22.05 was changed over to use the API for
searching. I think the API is not working correctly for you.
In fact, after looking for "API" among the Koha Administrative Interface
paraments, I noticed that RESTBasicAuth and others were "disabled" for me.
After
Hi Guiseppe,
the patron search in 22.05 was changed over to use the API for
searching. I think the API is not working correctly for you. Other
places you could check to see if that is the problem are if the list of
libraries or the list of STMP servers under Administration are showing
for you.
Hi,
I am using Koha 22.05.00.000 on Ubuntu 18.04.6 LTS.
Since a few (Koha) updates ago, I've noticed that the "search patrons"
function is not working.
I type in the first letters or the full name of an (existing) patron, the
search engine starts, but no one is found.
In order to display
Hi,
In the administration interfaz koha advanced search, authorities search and
periodicals search is not working. Just give me a page in blank with the
words not found (like dont found the page not the term).
It works in koha opac.
Any idea about what is happening?
--
*Lic. Vanesa E.
Le 16/05/2011 20:41, Chris Hobbs a écrit :
That was the hint I needed. While zebrasrv was running, checking the
zebrasrv logs I discovered:
zebra_lock_create fail fname=/var/lock/koha/zebradb/biblios/shadow..LCK
[Permission denied]
Removing those files then restarting koha-zebra-daemon got
That was the hint I needed. While zebrasrv was running, checking the
zebrasrv logs I discovered:
zebra_lock_create fail fname=/var/lock/koha/zebradb/biblios/shadow..LCK
[Permission denied]
Removing those files then restarting koha-zebra-daemon got the search
working again.
Thanks!
--
Chris
12 matches
Mail list logo
