IRC log for #koha, 2022-07-26

← Previous day | Today | Next day → | Search | Index

All times shown according to UTC.

Time Nick Message
00:05 eythian joined #koha
01:44 Sean_He joined #koha
02:20 alohabot 🎁 🐵 Koha '21.05.x' packages pushed to 'koha-staging' repo  🥫🍒🥔
02:28 koha-jenkins Project Koha_21.05_U18 build #194: SUCCESS in 38 min: https://jenkins.koha-community[…]ha_21.05_U18/194/
02:29 Project Koha_21.05_U20 build #204: SUCCESS in 40 min: https://jenkins.koha-community[…]ha_21.05_U20/204/
02:43 Project Koha_21.05_D10 build #281: SUCCESS in 54 min: https://jenkins.koha-community[…]ha_21.05_D10/281/
02:48 tuxayo dcook: what happen when you try to run ES?
02:49 Could it be related to that? https://gitlab.com/koha-commun[…]elasticsearch-run
02:50 dcook tuxayo: Nah, it's not that. I've already taken care of that part.
02:50 I think I just don't get any search results from ES
02:50 tuxayo :o
02:50 dcook Tried changing options and re-indexing and :S
02:50 I'm probably just missing some step
02:50 tuxayo So at least it indexes?
02:51 dcook Not sure in hindsight
02:51 It's been a few weeks since I last tried
02:51 Need to sit down and look at it but.. yeah so behind at the moment
02:51 Hmm Tomas mentioned setting something to "yes" in the .env file. Maybe that's the key..
02:52 tuxayo bug 27667 can help to check if ES returns of the right number of indexed record
02:53 huginn Bug https://bugs.koha-community.or[…]_bug.cgi?id=27667 enhancement, P5 - low, ---, fridolin.somers, Pushed to master , Display the number of non-indexed records
02:53 tuxayo I guess you already have KOHA_ELASTICSEARCH=1
02:56 fridolin joined #koha
02:58 wajasu its funny.  i've been hitting koha-community.org for 3+ weeks now. It always says "Introducing Koha 20.05" [Try in now]
02:59 Even if I reload or reboot machine.  So do I really have to slear my cache to see it move to 22.05?
02:59 firefox on archlinux
03:00 koha-jenkins Project Koha_21.05_U16 build #203: SUCCESS in 1 hr 9 min: https://jenkins.koha-community[…]ha_21.05_U16/203/
03:00 wajasu my friend hit the site and saw 21.11 I think today.
03:01 mu laptop show 22.05 today.
03:02 it's wordpress, so it's probably caching in my firefox.
03:03 koha-jenkins Yippee, build fixed!
03:03 Project Koha_21.05_D12 build #130: FIXED in 34 min: https://jenkins.koha-community[…]ha_21.05_D12/130/
03:03 wahanui Congratulations!
03:03 tuxayo wajasu: I see "Introducing Koha 22.05", that's weird you have not that
03:04 > my friend hit the site and saw 21.11 I think today.
03:04 super weird
03:04 wajasu it through me off because the dashboard show 21.xx.  that's why i was working to add the 22.05
03:05 tuxayo In the PC that shows 20.05, can you try in private browsing?
03:05 > it's wordpress, so it's probably caching in my firefox.
03:05 2 years old cache that's too much. Did you even come to the website two years ago?
03:06 Is the news section up to date for you?
03:06 You should see stuff from July 26th, 2022
03:06 Just bellow the "try now"
03:07 wajasu 4 or 6 years ago and 10/12 before that.  maybe i got a version with bad expiry.  bu i know i've wipe all my cache in the past months, since i was developing web sites.
03:08 wow. i see the new values now.
03:08 it might have to due with the 26th being ahead of Florida.  In an hour it will be the 26th.
03:09 well i didn't touch refreshing my cache.  so i just wanted to mention this before I did and it just cleaned up.
03:09 tuxayo Website site TZ is new zealan
03:09 *zealand
03:09 That would be weird that it would affect something
03:10 wajasu the weird thing was that i've seen 20.05 for 3 weeks. never saw 21.xx and now here we are at 22.05
03:11 maybe the web page was edited and they just hit publish today.
03:12 i started working on db autoincrement today.
03:12 4 borrowers messaed up.   16 items messed up
03:13 borrower has 66 child relations ships as schemaspy shows.
03:14 i might just delete those 4 borrowers, but what a pain investigating other tables.
03:14 tmrw i'll investigat the items.
03:15 my librarian said it might just be items he deleted, or that he marked missing.  will have to see.
03:20 i brought up might site on a 1GB ram box, but if i nav to about->systeminfo, the second session caused the site to go down. so i need to figure out how to run with memcached (if possible), or maybe plack disabled.
03:20 i tried disabled plack, but it still crashed.
03:20 i might need more swap. only 512M
03:24 tuxayo At least more swap indeed
03:25 1 ram + 0.5 swap isn't enough for two worders
03:25 *workers
03:26 > maybe the web page was edited and they just hit publish today.
03:26 It was already 22.05 in the past
03:26 https://web.archive.org/web/20[…]ha-community.org/
03:26 puzzling
03:31 wajasu i commented out the memcached in koha-conf and it seems that things arent crashing.  but 75M to spare is too close for comfort.
03:32 maybe i need to bump to a 2GB RAM node for $5 more per month.
03:32 i probably has 2-4G of ram in that old 2010 PC I ran it on all these years.
03:33 who knows. if i had the memcached configured then, maybe the hard drive wouldn't have been working so hard.
03:34 its a 1GBnano on linode.com right now.
03:45 koha-jenkins Yippee, build fixed!
03:45 Project Koha_21.05_D11 build #232: FIXED in 59 min: https://jenkins.koha-community[…]ha_21.05_D11/232/
03:45 wahanui Congratulations!
04:07 wajasu i think that the autoincrement fix init-file should be included in koha-common install so new installations and existing don't continue to cause the problem
04:08 noting that if a bug fix is available, the file would be/could be detected and removed in that update
04:28 dcook wajasu: koha-common doesn't install MySQL
04:28 That reminds me though..
04:29 https://bugs.mysql.com/bug.php?id=77743
04:29 Not sure how that translate to MariaDB off the top of my head..
04:30 Actually.. maybe an unrelated bug
04:30 Anyway, hopefully the older versions of MariaDB/MySQL will be supported soon and then we won't have to worry about this issue anymore..
04:44 wajasu oh. i guess you are waiting for them not to use MAX(primarykey column). our having two tables where we "move
04:44 koha-jenkins Project Koha_21.05_D11 build #233: SUCCESS in 59 min: https://jenkins.koha-community[…]ha_21.05_D11/233/
04:45 wajasu " the row to deletedXXXX  is what caused it.
04:46 i guess moving the row out was for performance reasons, for joins, indexes.
04:47 i guess koha-create could add the init-file if not present :)
04:49 or in system info tab, add a button ito add it if it doesn't exist.  but the koha intra app would need to run as root
04:50 or maybe the init.d koha-common could at service startup.
04:51 does the problem exist in postgres?
04:52 what a headache
04:52 i'll be through fixing records by tomorrow i hope.
05:01 playing with running 1GB with 1 plack worker things work wihtout OOM killer for starman on Debian 11 mariab.
05:02 but just 50M of ram to survive isnt practical
05:35 fridolin joined #koha
06:33 reiveune joined #koha
06:33 reiveune hello
06:53 paulderscheid[m] Bonjour #koha
06:58 cait joined #koha
07:06 dcook wajasu: The autoincrement issue doesn't exist in newer versions of MySQL/MariaDB. They patched it. Just an issue for older versions.
07:07 Like we use newer database servers that don't have that problem
07:07 With postgres you usually use sequences which work differently so no the problem doesn't happen with postgres
07:07 I think their autoincrement might auto generate a sequence actually.. was reading something the other day
07:07 Oh well done work for the day. Dooooone.
07:17 cait good morning #koha
07:32 hm I just realized the manuals on pootle stop at 21.05
09:07 Joubu How do I retrieve the result from a REST API request when using Test::Mojo?
09:15 $t->tx->res->body
09:18 fridolin left #koha
10:20 khall joined #koha
10:38 oha joined #koha
10:40 oha hi there. quick question: what's the typical/expected delay for the debian packages to be available after a new release (22.05.03 in this case)? thanks
10:54 cait oha: usually they come out pretty fast these days
10:55 less than a week
10:59 khall_ joined #koha
10:59 oha ok, thanks. had the impression that in the past it happened on the same day :)
11:01 oleonard Hi #koha
11:11 thd joined #koha
11:21 tcohen hola #koha
11:26 oleonard Hi tcohen
11:30 jajm around?
11:33 cait hi oleonard and tcohen
11:46 mtj hi folks, any chance we can remove installer/data/mysql/atomicupdate/bug_30899.pl, for the 22.05.03 release?
11:46 cait oh i thought it had been done :(
11:47 it will be rerun as it was already in 22.05.02
11:47 not sure what we can do now as it has been released?
11:48 tcohen I think lukeg will cut a new release
11:48 cait does he know?
11:48 tcohen because there was a typo on the version as well
11:48 mtj ...perhaps add patch for bz-31108 too?
11:48 tcohen he's asleep for a few more hours
11:48 cait Waht about bug 31108?
11:48 huginn Bug https://bugs.koha-community.or[…]_bug.cgi?id=31108 blocker, P1 - high, ---, mtj, Pushed to master , rename ./t/00-check-atomic-updates.pl extension to *.t
11:49 tcohen mtj: good idea!
11:50 mtj cait: bz-31108 has a test to detect left-over atomic/*.t files
11:54 cait oh yes, that's a good one
11:55 mtj no probs, ill send him an email - will hold off pushing a 22.05 package
11:55 cait mtj++
11:56 tcohen oh, that's great mtj
11:59 alohabot 🎁 🦁 Koha '21.11.x' packages pushed to 'koha' repo  🥈🌎🚀
12:14 Joubu git pre-push hook for RM and RMaints should already have that test ;)
12:14 tcohen is there something about that on the wiki?
12:17 mtj tcohen: this perhaps -> https://wiki.koha-community.or[…]Git_pre-push_hook
12:21 tcohen yeah, was about to paste
12:21 I already have it on my box
12:21 but didn't have the reference to share
12:21 mtj tcohen: ill try to build a newer libdatetime-perl, for bionic
12:22 tcohen mtj++
12:26 rmaints please use https://wiki.koha-community.or[…]Git_pre-push_hook
12:33 cait i don't think they all read back here
12:33 maybe email?
12:35 Anne joined #koha
12:36 huginn News from kohagit: Bug 31211: (QA follow-up) Add class to new list element for error <https://git.koha-community.org[…]0cbcd21851e4d9c9c>
12:36 News from kohagit: Bug 31229: (bug 30063 follow-up) fix column visibility <https://git.koha-community.org[…]9a1a1c402be867eba>
12:36 News from kohagit: Bug 31211: Check slips and notices for valid Template Toolkit and report errors <https://git.koha-community.org[…]c35195a498b5342ae>
12:36 News from kohagit: Bug 21982: Circulation statistics wizard does not count deleted items <https://git.koha-community.org[…]8810792d25c6dc47b>
12:37 Anne Hi there, I was wrong when I installed Koha. I choose Marc instead of unimarc. So I need to reinstall it... How to do this ?
12:39 cait Where are you located Anne?
12:39 and how did you install?
12:43 Anne Thanks Cait : I'm in Belguim. I used commands line such as sudo koha-create --create-db biblio
12:44 cait I think you might need to remove the instance and start over
12:44 and use the koha-create command witht he UNIMARC option
12:46 koha-jenkins Project Koha_Master_D11_ES6 build #38: SUCCESS in 8 min 7 sec: https://jenkins.koha-community[…]aster_D11_ES6/38/
12:48 Anne Ok Cait, I'll try this. Thanks
12:48 marie-luce joined #koha
12:49 cait Anne: and then in the web installer also pick UNIMARC - so it all matches up
13:07 koha-jenkins Project Koha_Master_D11_ES7 build #40: SUCCESS in 8 min 9 sec: https://jenkins.koha-community[…]aster_D11_ES7/40/
13:12 mtj does anyone know why the 22.05 builds are failing?
13:16 hi tuxayo, can you push a v21.05.16 tag pweese
13:16 oops, v21.05.17 tag
13:18 koha-jenkins Project Koha_Master_U20 build #510: SUCCESS in 39 min: https://jenkins.koha-community[…]a_Master_U20/510/
13:25 Project Koha_Master_D11_My8 build #939: UNSTABLE in 47 min: https://jenkins.koha-community[…]ster_D11_My8/939/
13:28 cait hm, studying our coding guidelines: all SQL must be in the C4/xxxx.pm or Koha/xxxx.pm (xxxx being the module your SQL refers to)
13:29 ... didn't we say no SQL in the Koha namespace?
13:30 tcohen/Joubu?
13:31 tcohen mtj: missing misc4dev in the docker image?
13:31 cait: generally, yes
13:31 what is the question context?
13:31 cait so is this a case where we should update the coding guidelines?
13:31 bug 29145
13:31 huginn Bug https://bugs.koha-community.or[…]_bug.cgi?id=29145 enhancement, P5 - low, ---, koha-bugs, Needs Signoff , Allow patrons to have overdue items that would not result in debarment when removing overdue debarments
13:32 tcohen that one should be FQA for more tahn one reason
13:32 cait yes, I am just looking into it
13:32 sysprefs.sql is missing
13:32 0,1 shuld be used in .pref
13:34 tcohen new sub without POD, lacking tests on a sensible area
13:34 old style coding in Koha::Patron
13:35 koha-jenkins Yippee, build fixed!
13:35 Project Koha_Master_D10 build #761: FIXED in 55 min: https://jenkins.koha-community[…]a_Master_D10/761/
13:35 wahanui Congratulations!
13:35 tcohen has_overdues feels like the wrong place for this too
13:36 overduerules is about messaging and restricting the patron
13:36 items are overdue regardless what overduerules says
13:36 cait I think you might want to add your own notes too :)
13:37 mtj tcohen: hmm, misc4dev is loaded ok, but some sql files seem to be unavailable
13:37 cait but maybe let me post mine first
13:38 tcohen: can you run the script for creating the next dev meeting agenda
13:38 ?
13:38 I'd like to add the SQL question
13:39 and also the info on LTS
13:41 caroline joined #koha
13:42 tcohen I think it is done
13:42 the calendar stuff never worked for me
13:42 cait it isN#t
13:42 not listed in the wiki
13:42 and we better figure it out before Joubu leaves
13:42 :)
13:42 tcohen https://wiki.koha-community.or[…]Next_IRC_meetings
13:42 cait oh, just updated, on the wiki now
13:42 sorry, reload took a while
13:43 it was not there a few minutes ago
13:45 koha-jenkins Project Koha_Master_U22 build #156: SUCCESS in 1 hr 7 min: https://jenkins.koha-community[…]a_Master_U22/156/
13:48 mtj folks, whats the misc4dev repo?   https://gitlab.com/koha-community/koha-misc4dev ?
13:49 tcohen yes
13:50 mtj ah yep
13:57 ah, its the $VERSION = "22.05.03.00" typo, thats causing the 22.05 build fails
13:59 https://jenkins.koha-community.org/view/22.05/
14:00 np, email sent
14:02 tcohen I'm in a chat with lukeg
14:11 koha-jenkins Project Koha_Master_D11_MDB_Latest build #1033: SUCCESS in 45 min: https://jenkins.koha-community[…]_MDB_Latest/1033/
14:16 reks joined #koha
14:22 lukeg joined #koha
14:27 koha-jenkins Project Koha_Master build #2126: STILL UNSTABLE in 1 hr 11 min: https://jenkins.koha-community[…]Koha_Master/2126/
14:36 Project Koha_Master_D11_ES7 build #41: SUCCESS in 9 min 2 sec: https://jenkins.koha-community[…]aster_D11_ES7/41/
14:40 alohabot 🎁 🦄 Koha 'master' packages pushed to 'koha-staging' repo  🥐🥮🧀
14:41 tuxayo mtj: oops forgot when I was waiting for the CI. Done!
14:43 mtj: «whats the misc4dev repo» A lot of stuff used in spinning up ktd and KohaDevBox
14:43 khall joined #koha
14:48 caroline Just to confirm, adding release notes text is useless if it's released in an older version right? e.g. https://bugs.koha-community.or[…]_bug.cgi?id=18392 was released in 22.05.00, so it's too late to add release notes text. Should we remove the keyword release-notes-needed so that it doesn't appear in the list anymore?
14:48 huginn Bug 18392: enhancement, P5 - low, ---, nick, RESOLVED FIXED, Allow exporting circulation conditions as CSV or spreadsheet
14:53 koha-jenkins Project Koha_Master_D12 build #220: SUCCESS in 1 hr 8 min: https://jenkins.koha-community[…]a_Master_D12/220/
14:56 Project Koha_Master_D11_MDB_Latest build #1034: SUCCESS in 45 min: https://jenkins.koha-community[…]_MDB_Latest/1034/
14:58 tcohen caroline: yes
14:58 is it in the manual?
14:58 nm, that's another keyword
14:58 caroline Not yet, I can add the Manual keyword and remove the release-notes-needed
15:00 tcohen that's what I'd do
15:00 bag joined #koha
15:10 reiveune bye
15:10 reiveune left #koha
15:13 khall_ joined #koha
15:38 Anne I've just reinstalled Koha. But now I've got an internal error server when I try to access the Web installer. In plack-error.log I've got : Auth ERROR: Cannot get_session() at /usr/share/koha/lib/C4/Auth.pm line 1009. Is this a significant error ? If so, how can I fix it ?
15:38 cait did you restart all the things?
15:42 Anne joined #koha
15:42 wajasu dcook: thanks for letting me know that the newer mysql/mariadb doesn't have the autoincrement problem so I dont have to put the init-file in place on my new Debian11/mariadb upgrade
15:45 so though we move to deleted table, the memory and the periodic redo log for innodb record the max autoincrment value.
15:46 so upon startup the redo log/data dictionary is used to restore what the MAX is for the table.
15:47 so our moving rows from to deleted doesn't break the autoincrment in the newer mysql/mariadb versions mention in the wiki.
15:47 Anne cait : I restarted koha-zebra, koha-plack, apache (and always the same error). do I need to restart something else?
15:48 wajasu the only  time things can get messed up is with an abnormal exit of mysqld (OOM) where the redolog doesn't get flushed to disk.
15:53 Anne: i think sessions might be stored in memcached if its used. someone here may know. so maybe check if memcached is started.
15:53 cait Anne: did you add the instance with the same name as before?
15:53 but restarting memcahced is also a godo idea
15:54 wajasu service koha-common restart    or  systemctl koha-common restart may help
15:56 Anne thanks guys ! I restarted memcached and it works now ;)
15:57 cait great!
16:35 reks joined #koha
16:37 lukeg joined #koha
16:40 m23 joined #koha
16:44 cait joined #koha
16:47 Oak joined #koha
17:28 Oak joined #koha
18:51 wajasu is the issues table the one that record checkouts?
18:53 caroline wajasu, yes
19:38 fridolin joined #koha
19:38 fridolin yellow
19:42 fridolin1 joined #koha
19:59 keiths joined #koha
19:59 keiths After upgrading to the latest (22.05.02.000), I am getting 500 errors when a search should return a biblio entry. This happens on the OPAC and when I do a search under the cataloging section in the staff site. I am able to search for patrons with no  apparent problem.(I did have quite a bit of trouble updating my database)   I ran rebuild zebra and it made no difference.   How do I detect what is causing this problem?  _______________________________________
20:04 lukeg keiths: do the error logs give you any further info.?
20:21 tuxayo tcohen: Hola :) If I want to reach Spanish speaking librarians to make signoff sessions, where can I go?
20:21 What happened to es.koha-community.org ?
20:22 There isn't much traffic in https://lists.koha-community.o[…]ipermail/koha-es/
20:22 keiths Getting This error:
20:22 [Tue Jul 26 20:18:03.948868 2022] [cgi:error] [pid 3214] [client 37.19.200.146:54230] AH01215: DBIx::Class::Storage::DBI::_dbh_execute(): DBI Exception: DBD::mysql::st execute failed: Unknown column 'reserves.patron_expiration_date' in 'field list' at /usr/share/koha/lib/Koha/Objects.pm line 312: /usr/share/koha/opac/cgi-bin/opac/opac-search.pl, referer: http://sati.pustaka-digital.asia/ [Tue Jul 26 20:18:03.997828 2022] [cgi:error] [pid 3214] [client 37.19.
20:25 lukeg joined #koha
20:25 tuxayo keiths: did you recently upgrade your Koha? from which version to which version?
20:27 keiths Yes, recently upgraded to 22.05. I was at 21 (something). The database upgrade has a quite a few problems/errors
20:28 I just manually added the missing field to the table and the error disappears. Hope that won't effect things going forward.
20:32 Is there a way to test the data structure to be sure it is correct? I have run the schema update several times
20:32 wajasu finally. got the patrons cleaned up. spent all day recontiling all those 66 child tables.
20:33 now i have to work on items. 16 items with autoincrement problems.
20:39 tuxayo keiths: reserves.patron_expiration_date is missing
20:39 https://gitlab.com/koha-commun[…]revs/211200010.pl
20:40 Ah I though «manually added the missing field to the table» was during the update.
20:40 Did you do something about the update errors?
20:40 Do you still have the error log?
20:41 wajasu: congrats
20:41 wajasu thx
20:42 so biblionumber is the same as biblioitemnumber in the items table. same values with each other in my
20:42 db
20:42 tuxayo I'm not sure
20:42 let me query some database
20:45 wajasu select * from items where biblionumber != biblioitemnumber;   returned 0 rows.
20:45 keiths tuxayo: I saw that and modified it manually. Works Now. Don't know why the schema update didn't work
20:48 tuxayo wajasu: ok if in your base they are not different you are safe to assume that
20:49 I recall some columns are usually in sync but once saw an offset of a few numbers
20:49 keiths: so you already manually did the upgrades that failed when you did the upgrade?
20:53 koha-jenkins Project Koha_22.05_U18 build #40: NOW UNSTABLE in 39 min: https://jenkins.koha-community[…]oha_22.05_U18/40/
20:54 wajasu keiths: if you used mysql commandline client, look in your ~/.mysql_history file, you can save those fixes to a text file, then put them on the koha pastebin
20:59 intersting that biblioitemnumber is not in deleteditems table.
20:59 but that not stopping my autoincrement investigation
21:01 koha-jenkins Yippee, build fixed!
21:01 Project Koha_22.05_U22 build #35: FIXED in 48 min: https://jenkins.koha-community[…]oha_22.05_U22/35/
21:01 wahanui Congratulations!
21:04 keiths wajasu: thanks.
21:05 wajasu bummer. for my autoincrement problem, deleteditems have different biblio number from the corresponding items
21:15 koha-jenkins Project Koha_22.05_U20 build #39: NOW UNSTABLE in 1 hr 2 min: https://jenkins.koha-community[…]oha_22.05_U20/39/
21:47 Project Koha_22.05_D11 build #43: NOW UNSTABLE in 1 hr 10 min: https://jenkins.koha-community[…]oha_22.05_D11/43/
22:04 tcohen hi all
22:20 fridolin1 tcohen: le bonjour cher RM
22:33 tuxayo tcohen: Hola :) If I want to reach Spanish speaking librarians to make signoff sessions, where can I go?
22:33 There isn't much traffic in https://lists.koha-community.o[…]ipermail/koha-es/
23:39 koha-jenkins Project Koha_22.05_D11 build #44: STILL UNSTABLE in 1 hr 9 min: https://jenkins.koha-community[…]oha_22.05_D11/44/

← Previous day | Today | Next day → | Search | Index

koha1