You could try "SET GLOBAL foreign_key_checks = 0".
You could also try adding `$dbh->{AutoCommit} = 0;` to see if that will
keep the foreign_key_checks setting set. That shouldn't really change
anything though.
I assume you are using the `koha-upgrade-schema` script to do this; that
should be the w
Yes, that update turns off the foreign key checks for the duration, but I'm
not sure that that would affect the column type, I think it only affects
column content checks. But I could be wrong.
This update does more than add the collate I think. It does check the
collate to see if the update has
Memcached was the process requesting more memory, not necessary the process
using a lot of memory.
Looking through the logs you attached it seems Beam.smp (which I believe is
RabbitMQ), MariaDB, and Koha Plack are the top three memory processes.
rebuild_zebra is also using a lot of paged memory, bu
I won't comment on how it happened, but it does in fact seem that there is
a biblio record (at least one) that doesn't have a biblioitems table row to
go along with it.
I just checked my database for this, and was astonished to find there were
many such records. What I found in my case was that th
That's cool.
I use Nagios4 in Ubuntu 24.04 for that.
I'll include excerpts of my Nagios config for those who are curious. This
Koha Status Monitor is probably a lot easier to setup.
On Mon, Jan 27, 2025 at 10:10 AM Atanu from Koha Support Team via
Koha-devel wrote:
> Dear Community,
>
> I'm ex
When that happens to me, the first thing I check (if the service is running
as fastcgi / plack / fpm) is that the process manager is running. Often I
have to start / restart plack / fpm.
'Bad Gateway' probably means there is a load balancer (reverse proxy) in
the path, and the breakage is between
The `git branch -u origin/main` command should come after a `git fetch` or
`git pull` so that your git is aware of the remote branch change. Changing
it by hand in the .git/config file as you have done should be fine too.
On Mon, Apr 22, 2024 at 12:47 AM Magnus Enger via Koha-devel <
koha-devel@
On Wed, Mar 6, 2024 at 1:11 AM Wagner, Alexander
wrote:
> Hi!
>
> ...
> > These are home branch and holding branch internally.
> > It seems like most of what you are talking about here is the Shelving
> > Location.
>
> Yes. My question is mainly: how do I tell, also to patrons in the OPAC but
>
Forgive me if I add to your confusion a bit instead of clearing it up.
There are actually three locations in Koha: Permanent location, current
location, and shelving location. The first two only matter if you have
more than one site; if you only have one site you can set them to the same
value and
I believe, for Zebra, the file /etc/koha/zebradb/authorities/etc/bib1.att
maps attributes to indexes.
I don't know elasticsearch that well, so I can't say whether there is or
isn't a similar configuration there. Or even whether it's possible to do
that.
In the past it was deemed unfeasible to have
10 matches
Mail list logo
