Re: [Koha] Koha offline circulation
Hello! Thank you for the answer! I don't have a pending_offline_transactions table, but there is a pending_offline_operations. Did you want to talk about her? Good Luck! Igor A. Sychev Tomsk Polytechnic University https://lib.tpu.ru -Original Message- From: Koha On Behalf Of Katrin Fischer Sent: Sunday, May 14, 2023 4:38 PM To: koha@lists.katipo.co.nz Subject: Re: [Koha] Koha offline circulation Hi, I am not aware of a limit, but 13.000 could be a little much. The transactions are stored in the pending_offline_transactions database table. Usually they are cleaned up by processing them. Maybe you want to backup the table and try with a few transactions first to see how that goes. Or try it out on a demo or test installation. Hope this helps, Katrin ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Background job / Staging MARC import stuck at 0%
Hi Michael, Did you also restart some services after changing the script including memcache? Sometimes it is necessary but not remember for this case. You should also look https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33412 Mengü Yazıcıoğlu Devinim Yazılım Eğitim Danışmanlık Reşit Galip Cad. No: 29/6 Çankaya/ANKARA Tel: (312) 446 86 68 Cep: (532) 701 90 27 On 13.05.2023 16:21, Michael Brown wrote: I tried Mengü's suggestion of editing manage-marc-import.pl, to no avail. Still hangs at enqueuement; no messages, no errors, simply hangs and spins my CPU into a frenzy. Responses to George's message below: On Wed, May 10, 2023 at 8:34 AM George Veranis wrote: Hi Michael, Could you check the following things: 1) if your rabbitmq-server is running ? Yes. 1.1) if yes, then check if the cluster of nodes in rabbit exist , the command is: rabbitmqctl cluster_status Cluster status of node rabbit@kiko ... Basics Cluster name: rabbit@kiko Disk Nodes rabbit@kiko Running Nodes rabbit@kiko Versions rabbit@kiko: RabbitMQ 3.9.21 on Erlang 24.3.4.2 Maintenance status Node: rabbit@kiko, status: not under maintenance Alarms (none) Network Partitions (none) Listeners Node: rabbit@kiko, interface: [::], port: 61613, protocol: stomp, purpose: STOMP Node: rabbit@kiko, interface: [::], port: 25672, protocol: clustering, purpose: inter-node and CLI tool communication Node: rabbit@kiko, interface: [::], port: 5672, protocol: amqp, purpose: AMQP 0-9-1 and AMQP 1.0 Feature flags Flag: implicit_default_bindings, state: enabled Flag: maintenance_mode_status, state: enabled Flag: quorum_queue, state: enabled Flag: stream_queue, state: enabled Flag: user_limits, state: enabled Flag: virtual_host_metadata, state: enabled 1.1.1) if not shows you something in json format you can try to start it with command rabbitmqctl start_app N/A, rabbitmq is already running. 1.2 ) If no , start it and check the logs from your rabbitmq-server at /var/log/rabbitmq/ and check if the service is start it normally . N/A, rabbitmq is already running. 2) check the worker-output.log on your koha if koha write there something and have koha connection with rabbit server . I cannot find a file called "worker-output.log" anywhere in my Alma installation. Best Regards, George -Original Message- From: Koha On Behalf Of Michael Brown Sent: Wednesday, May 10, 2023 3:50 PM To: Cindy Murdock Ames Cc: koha@lists.katipo.co.nz Subject: Re: [Koha] Background job / Staging MARC import stuck at 0% Hi Cindy, apologies for the double-response: I had unsubscribed from the koha list so my response didn't get added to the thread. I wanted to remedy that, and also say that, because I had unsubscribed, I missed Mengü's suggestion of updating manage-marc-import.pl. I am eager to try that fix and will report back later today or tomorrow with my findings. Here's my original response to Cindy before re-subscribing to to the koha list: Yes, my koha-conf.xml does contain that block because I added it during the initial setup. (You're right, it wasn't there originally.) However, it doesn't help; I still cannot import batch bib records in Koha 22.11 the way I could in Koha 22.05. The enqueuement hangs and sends my cpu through the roof until I navigate away from that page. I've gotten one off-list suggestion that upgrading to the newest Koha fixes the problem. Unfortunately for me, I don't really have time for that right now, so I have (at least temporarily) abandoned my efforts with Koha. Thanks for your suggestion! Bests, Michael On Tue, May 9, 2023 at 4:40 PM Michael Brown wrote: Hi Cindy, Yes, my koha-conf.xml does contain that block because I added it during the initial setup. (You're right, it wasn't there originally.) However, it doesn't help; I still cannot import batch bib records in Koha 22.11 the way I could in Koha 22.05. The enqueuement hangs and sends my cpu through the roof until I navigate away from that page. I've gotten one off-list suggestion that upgrading to the newest Koha fixes the problem. Unfortunately for me, I don't really have time for that right now, so I have (at least temporarily) abandoned my efforts with Koha. Thanks for your suggestion! Bests, Michael On Tue, May 9, 2023 at 1:37 PM Cindy Murdock Ames wrote: Hi Michael, Can you confirm your koha-conf.xml contains a message broker section, like this? localhost 61613 guest guest I had the same problem after upgrading from 22.05 to 22.11; I'm guessing 22.05 must have had some defaults set in the code that allowed the message broker to start automatically without this section whereas 22.11 must not. I was missing this section and added it and was able to complete imports after restarting Koha. I'm still having the issue with zombie background jobs (I'm afraid to test rolling back the code on a production server) but I made a hacky bash script to run as a cron job to check for them and
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/16/23 10:51, Bruce A. Metcalf wrote: On 5/15/23 16:41, Galen Charlton wrote: 3. Can I install a new instance in the same virtual machine and transfer the settings and data? Almost everything worth permanently keeping in a typical Koha system is stored in the database. Is MySQL/MariaDB running and can you get a mysqldump? I'm not sure. How can one tell? There is a MySQL instance running, but I suspect that may be for one of the other servers. There is no MariaDB running, which I recall having switched to some time back. Can I buy a clue about how to run mysqldump? MariaDB's process name is mysql, it doesn't matter much which you are using. you can make a backup wich mysqldump like this: mysqldump -u root -p --all-databases > backup.sql you should run this command from a directory with enough space to hold a backup of your database. you can reinstall koha-common by issuing this command: sudo apt-get install --reinstall koha-common it should pull any missing dependencies. Have you tried to backup your koha instance with "koha_dump" ? if your library instance is called "thisone", use: sudo koha_dump thisone it should put the backup on /var/spool/koha/thisone/ This process creates a mysqldump backup of just your database, and copies the rest of your koha files to a tar file. Those files can be used with koha_restore but if they can be made, your koha should be good enough for you to repair it. If not, are there at least database files present in /var/lib/mysql? If /var/lib/mysql/ibdata1 is the right file, then yes. It's almost a GB in size, which seems reasonable for the library's data. A current copy of the database could be imported into a fresh install of Koha (either in a new VM or after a wipe and recreation of the existing one - though if you do a wipe, triple-check that your database export is good!). Right. Tried to delete Koha and reinstall, but there was no change in the resultant. Wiping the whole VM is impractical due to the other servers on it, though that may prove necessary. I continue to suspect that the problem lies with the upgrades from Debian 9 to 10 and Koha 21.05 to 21.11. Something didn't upgrade correctly, or there's a hidden incompatibility, that's stopping work. Thanks for the ideas. Respectfully, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha -- Hector Gonzalez ca...@genac.org ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
> > Yet another command that may shed some light on the status of your installation: ~# systemctl status koha-common If Koha is running, that will display every active component. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
Bruce, here are some more suggestions: 1. When it comes to the logs, perhaps a command such as these (and similar) will reveal when and how something went wrong: grep -inr --include \*.log 'koha-common' /var/log/ zgrep -in 'koha-common' /var/log/dpkg.log* 2. You should double-check that your installation source file is correct, as covered by https://wiki.koha-community.org/wiki/Koha_on_Debian#Set_up_package_sources. For example, mine shows after the following command: ~# cat /etc/apt/sources.list.d/koha.list deb [signed-by=/usr/share/keyrings/koha-keyring.gpg] https://debian.koha-community.org/koha 22.05 main 3. If APT seems to be working, then you could install 'debsums' (apt install debsums) and see what it reveals with this command: debsums --all --silent dpkg --verify koha-common dpkg --audit koha-common Those are going to look for errors in packages and list the configuration files that have been altered from their default. It listed nicely the files that I already knew I changed for both Koha and Apache. 4. You may want to try the following commands, too: apt --fix-broken install apt --fix-missing install 5. If the Koha installation is incomplete, despite what the system seems to report, then you may want to use 'dpkg' to remove 'koha-common' and then reinstall with 'apt' according to the instructions. dpkg --remove koha-common 6. When it comes to listing the databases, here's what you might expect to see: ~# mysql -uroot -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 348 Server version: 10.5.19-MariaDB-0+deb11u2 Debian 11 Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. MariaDB [(none)]> show databases; ++ | Database | ++ | information_schema | | koha_library | | mysql | | performance_schema | ++ 4 rows in set (0.000 sec) MariaDB [(none)]> quit Bye Since our instance is named 'library', you can see that our database is named 'koha_library'. It is customary for the instance creation process to use the 'koha_' prefix for the database name. Does yours show something similar? On Tue, May 16, 2023 at 6:40 PM Bruce A. Metcalf wrote: > > On 5/15/23 16:35, David Liddle wrote: > > > Bruce, it’s an intriguing problem But I do have some more > > questions: > > > > - What other services are running on that server? Are they all still > > working correctly? > > > There is another Apache server and a MediaWiki server (which may also > run under Apache). Both are working as before with no problems or > noticeable slowdowns. > > > > - What clues are there in the logs in /var/log/? > > > The only logs with any entries are access logs which show that the > Chinese and Eastern Europeans are trying to hack the system. I don't > think those are relevant. > > What may be relevant is that TOP does not show that Koha is running, > though this could be just that the command isn't obvious. > > > > - Is the apt installer working generally, or do you perhaps have a > > broken Debian installation? Can you update or install other packages > > successfully? > > > The apt installer appears to be working, but it is not updating Koha > apps, and there have been several updates since this began. The > repository link appears to be correct; I'm (trying to run) on > "oldoldstable". > > > > - Can you access the database server to do a manual dump of the Koha > > database? > > > Not using any Koha tools or commands. I might be able to do so manually, > but am clueless about how to do so. > > Thanks for your continuing efforts. > > Respectfully, > / Bruce / > Bruce A. Metcalf, Librarian > The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/16/23 12:31, David Liddle wrote: What are the results of the following commands? Clearly your installation is incomplete. dpkg -l koha-common root@store:/var/lib/mysql# dpkg -l koha-common Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---=== ii koha-common21.11.19-1 all integrated (physical) library management system dpkg -s koha-common root@store:/var/lib/mysql# dpkg -s koha-common Package: koha-common Status: install ok installed Priority: optional Section: web Installed-Size: 574598 Maintainer: Mason James Architecture: all Source: koha Version: 21.11.19-1 Depends: ... [many lines deleted] They are similar, in that the first is a summary and the second is more detailed. For example, one of my systems shows the following with the first: ~# dpkg -l koha-common Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---=== hi koha-common22.05.12-1 all integrated (physical) library management system Which is a pretty fair match. Not at all sure what the latter is supposed to show me. (Full dump on request.) And the same system shows this with apt: ~# apt policy koha-common koha-common: Installed: 22.05.12-1 Candidate: 22.05.12-1 Version table: *** 22.05.12-1 500 500 http://debian.koha-community.org/koha 22.05/main amd64 Packages 100 /var/lib/dpkg/status root@store:/var/lib/mysql# apt policy koha-common koha-common: Installed: 21.11.19-1 Candidate: 21.11.19-1 Version table: *** 21.11.19-1 500 500 http://debian.koha-community.org/koha oldoldstable/main i386 Packages 100 /var/lib/dpkg/status Again, pretty much a match. So if these responses are good, where is my problem lurking? In case you need the commands for grabbing your database: ~# mysql -uroot -p show databases; Mine shows: root@store:/var/lib/mysql# mysql -uroot -p Enter password: Welcome to the MariaDB monitor. Commands end with ; or \g. Your MariaDB connection id is 18971 Server version: 10.3.38-MariaDB-0+deb10u1 Debian 10 (take note of KOHA_DB in the table) No table there to take note of. ~# mysqldump --databases KOHA_DB > koha_db_dump.sql This command gives me "access denied" for both root and myself. If your other configuration files – most of which are in /etc/koha/ and /var/lib/koha/ – are missing, you may be able to copy them from within the full-drive backup. Buncha stuff in both directories. Not sure if they're complete or not. Some formats are easier to mount and browse than others. What do you use? I use the automatic backup run by my virtual machine service. It restores just fine, but don't know if it can do file-by-file restores. Thanks for your continuing efforts, glad to test and post other items. Respectfully, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/15/23 16:41, Galen Charlton wrote: 3. Can I install a new instance in the same virtual machine and transfer the settings and data? Almost everything worth permanently keeping in a typical Koha system is stored in the database. Is MySQL/MariaDB running and can you get a mysqldump? I'm not sure. How can one tell? There is a MySQL instance running, but I suspect that may be for one of the other servers. There is no MariaDB running, which I recall having switched to some time back. Can I buy a clue about how to run mysqldump? If not, are there at least database files present in /var/lib/mysql? If /var/lib/mysql/ibdata1 is the right file, then yes. It's almost a GB in size, which seems reasonable for the library's data. A current copy of the database could be imported into a fresh install of Koha (either in a new VM or after a wipe and recreation of the existing one - though if you do a wipe, triple-check that your database export is good!). Right. Tried to delete Koha and reinstall, but there was no change in the resultant. Wiping the whole VM is impractical due to the other servers on it, though that may prove necessary. I continue to suspect that the problem lies with the upgrades from Debian 9 to 10 and Koha 21.05 to 21.11. Something didn't upgrade correctly, or there's a hidden incompatibility, that's stopping work. Thanks for the ideas. Respectfully, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
On 5/15/23 16:35, David Liddle wrote: Bruce, it’s an intriguing problem But I do have some more questions: - What other services are running on that server? Are they all still working correctly? There is another Apache server and a MediaWiki server (which may also run under Apache). Both are working as before with no problems or noticeable slowdowns. - What clues are there in the logs in /var/log/? The only logs with any entries are access logs which show that the Chinese and Eastern Europeans are trying to hack the system. I don't think those are relevant. What may be relevant is that TOP does not show that Koha is running, though this could be just that the command isn't obvious. - Is the apt installer working generally, or do you perhaps have a broken Debian installation? Can you update or install other packages successfully? The apt installer appears to be working, but it is not updating Koha apps, and there have been several updates since this began. The repository link appears to be correct; I'm (trying to run) on "oldoldstable". - Can you access the database server to do a manual dump of the Koha database? Not using any Koha tools or commands. I might be able to do so manually, but am clueless about how to do so. Thanks for your continuing efforts. Respectfully, / Bruce / Bruce A. Metcalf, Librarian The Augustan Library ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
Hello again, Bruce, I had some more thoughts today about your
situation. What are the results of the following commands? Clearly
your installation is incomplete.
dpkg -l koha-common
dpkg -s koha-common
They are similar, in that the first is a summary and the second is
more detailed. For example, one of my systems shows the following with
the first:
~# dpkg -l koha-common
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-==---===
hi koha-common22.05.12-1 all integrated (physical)
library management system
And the same system shows this with apt:
~# apt policy koha-common
koha-common:
Installed: 22.05.12-1
Candidate: 22.05.12-1
Version table:
*** 22.05.12-1 500
500 http://debian.koha-community.org/koha 22.05/main amd64 Packages
100 /var/lib/dpkg/status
In case you need the commands for grabbing your database:
~# mysql -uroot -p
> show databases;
(take note of KOHA_DB in the table)
> quit
~# mysqldump --databases KOHA_DB > koha_db_dump.sql
If your other configuration files – most of which are in /etc/koha/
and /var/lib/koha/ – are missing, you may be able to copy them from
within the full-drive backup. Some formats are easier to mount and
browse than others. What do you use?
On Mon, May 15, 2023 at 10:35 PM David Liddle wrote:
>
> Bruce, it’s an intriguing problem, since you’ve come from a working system.
> However, I shouldn’t think about it while I ought to be sleeping. Perhaps
> others will chime in as the sun works its way across the US. But I do have
> some more questions:
>
> - What other services are running on that server? Are they all still working
> correctly?
> - What clues are there in the logs in /var/log/?
> - Is the apt installer working generally, or do you perhaps have a broken
> Debian installation? Can you update or install other packages successfully?
> - Can you access the database server to do a manual dump of the Koha database?
>
>
> On Mon, May 15, 2023 at 8:51 PM Bruce A. Metcalf
> wrote:
>>
>> On 5/15/23 12:12, David Liddle wrote:
>>
>> > I see now that I overlooked your statement that commands such as
>> > 'koha-dump' are not recognized. Do they appear in the directory
>> > /usr/sbin/?
>>
>>
>> No. Not a single koha- command present in that directory.
>>
>>
>> > Do you have automated Koha backups configured that are available in
>> > /var/spool/koha/{instance}?
>>
>>
>> No, though that would have been smart of me. I don't even have a
>> directory /var/spool/koha, much less /var/spool/koha/instance.
>>
>> Appreciate the effort.
>>
>> Respectfully,
>> / Bruce /
>> Bruce A. Metcalf, Librarian
>> The Augustan Library
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Fwd: Dead Koha Resuscitation
> Almost everything worth permanently keeping in a typical Koha system is > stored in the database. Just to be complete, dont forget your uploads in the clone folder. They are not stored in the database. Marcel ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] 22.11.x String Freeze
I can happily report that we are now in string freeze for 22.11.06. Happy translating. Martin Renvoize, MPhys (Hons) Head of Development and Community Engagement E: martin.renvo...@ptfs-europe.com P: +44 (0) 1483 378728 M: +44 (0) 7725 985636 www.ptfs-europe.com ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
