Time Nick Message 07:25 Atral[m] hello everyone, I'm about to quit my old koha installation running on a Centos VPS and I would like to switch to a new Debian VPS (so I can install and manage Koha more easily). However, I'm having a lot of difficulty choosing a hosting provider: in fact, my old Centos VPS was Fully Managed, but at the moment I haven't found Hostig Providers that offer a Fully Managed VPS with Debian. Does anyone have any suggestions related to this topic? 07:25 Atral[m] Thanks! Atral 07:27 paulderscheid[m] We use Hetzner at LMSCloud.They are very cheap. However, I think Vultr and Linode are also pretty good options. What exactly do you mean by "Fully Managed" Atral ? 07:31 Atral[m] thank you paulderscheid for the suggestions! with "Fully Managed" i mean that the Hosting Provider take care of the general security the update and the backup of the VPS, and that they have a ticketing system for all the technical issues 07:36 paulderscheid[m] Ah, the providers I listed aren't fully managed then. You pretty much have to do that yourself. Vultr offers this in part, though. 07:41 Atral[m] ok, thanks...i think that is very difficult to find a Hosting Provider that offer a Fully Managed with Debian... 07:50 cait1 Atral[m]: maybe ask on the mailing list? you'll reach a lot more people there 07:51 Atral[m] hi cait1, yes thanks for the suggestion. I will try to ask on the mailing list 07:55 aroussos Atral[m]: You may want to have a look at this list, too: https://www.serverhunter.com/#query=operating_systems%3Adebian+features%3Amanaged 08:24 Atral[m] thanks aroussos ! 10:17 ashimema OK.. for anyone stuck with ktd failing to start.. there's definitely issues 10:17 ashimema but you can use local node_modules dependancies to get around it.. yarn install on the host and your ktd will start up next time 10:17 ashimema but we should really fix ktd 10:25 oleonard Thanks ashimema for the tip, and hi all 10:25 ashimema it's been killing me for days not being able to use ktd 10:26 ashimema qa 10:30 ashimema Joubu around? 10:45 tcohen[m] Have you tried cleaning your node_modules? 10:45 tcohen[m] I will trigger a rebuild of the images 10:46 tcohen[m] Just in case 10:48 tcohen[m] Also, you can check out the code pre-cypress change for startup and you will be fine afterwards 10:49 tcohen[m] I'll devote some time this morning to debug this 10:50 tcohen[m] mtj: what's up with the trixie build? 10:59 ashimema we've confirmed it here 10:59 ashimema if you nuke your hosts node_modules then you can replicate the issue very easily 11:00 ashimema it's the container.. 11:09 tcohen[m] thank you davidnind 11:09 ashimema ha. 11:10 ashimema OK.. so the build I triggered this morning seems to have fixed it for me entirely now 11:10 ashimema no need for local node_modules again 11:11 tcohen[m] good 11:11 tcohen[m] docker run -ti koha/koha-testing:master bash 11:11 tcohen[m] that's what I was waiting for the download to run 11:12 tcohen[m] with that command you have a shell inside a container out of the image 11:12 tcohen[m] and you can inspect the effective cypress version 11:12 ashimema for me, whatever I did, it was picking the 9.7 old version 11:13 ashimema but isn't now 11:17 tcohen[m] For me, it is either the image cache messing up, or this lines having some cache issue as weel 11:17 tcohen[m] https://gitlab.com/koha-community/koha-testing-docker/-/blob/master/dists/bullseye/Dockerfile?ref_type=heads#L148-149 11:17 tcohen[m] maybe we should point the Dockerfile to the community repo 11:17 tcohen[m] now it has resources and won't fail too often 11:18 ashimema 🙂 11:18 tcohen[m] root@1f86be49d98f:/kohadevbox# ls -l Cypress/ 11:18 tcohen[m] total 4 11:18 tcohen[m] drwxr-xr-x 3 1000 root 4096 Sep 7 08:59 12.17.4 11:18 tcohen[m] ^^ the image now has the right version 11:19 tcohen[m] Joubu: "cypress": "^12.17.2", 11:20 tcohen[m] should we fix it to 12.17.2/4 or we just allow it to get updated each time we build, to minor/patch versions 11:55 ashimema @seen magnuse 11:55 huginn ashimema: magnuse was last seen in #koha 6 days, 4 hours, 38 minutes, and 33 seconds ago: <magnuse> ciao dcook 11:56 ashimema anyone else here using sip sorters? 12:24 cait1 not yet 12:25 cait I know KIT will 12:25 cait what's up? 12:25 ashimema I'm considering enhancing the preference 12:25 cait MichaelaSieberBIB[m]: ping 12:25 ashimema and wanted to know if my customers requirements are a bit specific to them or not 12:26 ashimema basically.. they don't need the rules by checkin branch (which surprises me).. but they do need more than one field comparison 12:26 ashimema they do 'itemtype + collectino code' for their bin sorting 12:26 ashimema which we don't support.. 12:26 ashimema we require branch + any item field 12:27 ashimema but can't add further fields to the conditionals 12:28 cait I've poked MichaelaSieberBIB[m] 12:29 ashimema thanks 12:30 cait a question I had: do your customers sort on hold items separately? 12:30 cait I think that came up in some of our discussions 12:30 ashimema very good question 12:30 cait because those will go to the circulation desk and not to re-shelving 12:30 ashimema I have no idea 12:32 cait I feel checkin branch for sure makes sense, because you might have different sorting machinges at different branches 12:32 cait is your question if it should be possible to combine arbitrary item fields for conditions or more specific combinations? 12:32 MichaelaSieberBIB[m] Hi all 12:32 MichaelaSieberBIB[m] this is our configuration for SIP2SortBinMapping 12:33 MichaelaSieberBIB[m] CS:permanent_location:eq:LST:Links2 12:33 MichaelaSieberBIB[m] CS:permanent_location:eq:LSN:Links2 12:33 MichaelaSieberBIB[m] CS:permanent_location:eq:LSG:Links3 12:33 MichaelaSieberBIB[m] CS:permanent_location:eq:MAG07:Mitte 12:33 MichaelaSieberBIB[m] CS:permanent_location:eq:MAG08:Mitte 12:33 MichaelaSieberBIB[m] CS:permanent_location:eq:MAG09:Mitte 12:33 MichaelaSieberBIB[m] CS:permanent_location:eq:MAG10:Mitte 12:33 MichaelaSieberBIB[m] CS:permanent_location:eq:MAG11:Mitte 12:33 MichaelaSieberBIB[m] CS:permanent_location:eq:LSW:Rechts1 12:33 MichaelaSieberBIB[m] CS:permanent_location:eq:LBS:Rechts2 12:33 MichaelaSieberBIB[m] FBH:homebranch:eq:$holdingbranch:Mitte 12:33 MichaelaSieberBIB[m] FBH:homebranch:ne:$holdingbranch:Links1 12:33 cait I like the middle and right :) 12:33 ashimema interesting.. your bins have names as apposed to just numeric codes 12:34 ashimema it's about adding further field conditions 12:34 ashimema so they currently have it so they check itemtype first.. then look for collection code and finally sort on that combination 12:34 PedroAmorim[m] https://wiki.koha-community.org/wiki/ down for anyone else? 12:35 ashimema so DVD + Adult = sort bin 2, DVD + PG = sort bin 7 12:35 paulderscheid[m] Yes 12:35 paulderscheid[m] Pedro Amorim: 12:35 ashimema but you may also have Book + Adult = sort bin 3 12:36 ashimema I missed this case when I helped magnuse get his approach through QA 12:37 ashimema shame.. we've had custom sort bin handling modules at our end for years 12:37 cait from what I get, we#d not need collections 12:38 cait or itemtype+collection - but it might be nice for some 12:38 cait more interested in a flag for the on hold ones :) 12:38 ashimema I'm not sure how to achieve it in a 'nice' way 12:38 ashimema I was considering adding nesting into the config 12:39 ashimema > CS:effective_itemtype:eq:DVD:- 12:39 ashimema > ccode:eq:Adult:3 12:39 ashimema grr.. 12:39 ashimema it lost the leading space formatting there 12:40 ashimema I put a tab (4 spaces) before the 'ccode' line 12:40 ashimema and was using '-' to mean look for nested condition 12:40 ashimema it fixes it at two fields in combination though.. which may not be adequate for all cases? 12:41 ashimema and.. I have no idea if there's someone out there using '-' as a valid sort bin name 12:43 cait i think that is not THAT likely 12:43 cait i think if you don't take options way, it will be fine ;) 12:44 aude_c[m] If it's the library I'm familiar with 😉 their items on hold go in the "exceptions" bin - basically anything else that doesn't get sorted into the other bin. Mainly that's items on hold at the sorter's branch but also any items that need to go / go back to other branches. 12:44 cait yes, wiki is down 12:45 aude_c[m] I think their sorting rules has gotten even more complex recently because they've had to reorganise the library layout. Their bins are mostly by floor 12:45 ashimema er.. where's the code for the holds stuff aude_c 12:45 ashimema is that done at the sorter end using a different field 12:45 ashimema I think it must be 12:45 aude_c[m] I don't think there's any because it's just "anything else, go to the end bin"? 12:46 aude_c[m] I agree that being able to use ccode in the parameters would be great too. 12:48 ashimema they can use ccode 12:48 ashimema they can use any field (or method in the item object actually) 12:48 aude_c[m] cool 12:48 ashimema what we can't currently do is have more than one field matched 12:49 aude_c[m] ahh ok 13:07 cait maybe the sorter has some additional logic 13:08 cait that's how it often works here, they check, I think, Item information 13:08 cait we have no flag in the item that tells it's needed to fill a hold, so you need to get the info otherweise 13:08 ashimema indeed 13:08 ashimema must have other logic 13:13 cait because we can only tell on checkin if the item is needed to fill a hold 13:13 MichaelaSieberBIB[m] <aude_c[m]> "I don't think there's any..." <- I think so too 13:14 MichaelaSieberBIB[m] cait: exactly 13:23 oleonard-away PedroAmorim[m]: The patch on Bug 34723 works for you? I was about to comment that it doesn't work for me 13:23 huginn 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34723 minor, P5 - low, ---, dcook, Signed Off , opac-imageviewer.pl not showing thumbnails 13:24 PedroAmorim[m] it did work for me, yes 13:24 PedroAmorim[m] I added a missing test plan step 13:26 oleonard-away That's very weird. I've tested multiple times. 13:29 PedroAmorim[m] I will double-check 13:41 tcohen[m] the portainer server is not accepting connections of any kind 13:41 tcohen[m] checking what's going on 13:41 tcohen[m] portainer <- wiki, jenkins 13:50 tcohen[m] things restored 13:50 PedroAmorim[m] tcohen++ 13:51 PedroAmorim[m] oleonard-away: what exactly fails for you with 34723 13:51 PedroAmorim[m] I just went through it again and it works for me 13:53 oleonard For me it doesn't fix the problem. No thumbnails show up. 13:53 oleonard But I'm happy for QA to get it and have a look 13:53 PedroAmorim[m] have you restarted plack after applying patch 13:53 oleonard Yes, restarted all 13:53 oleonard (not that it should matter, I would think, for a template-only change) 13:54 PedroAmorim[m] with images uploaded, if I go to... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/eOEkIfWlEogqxWTjVAcvwDwH>) 13:55 aude_c[m] tcohen++ for restoring things (in this case, the wiki 😉) 13:56 cait tcohen++ 14:05 Shane-NP[m] what tool(s) can I run to see if my server is the cause of slowness. Basically even to load the About page, the server seems to hang on response. Client side, I can ping, nslookup instantly...so I want to see if it is waiting on Apache or something on the backend. Just not sure where to start to monitor the delay. 14:06 Shane-NP[m] The server needs to be re-done...it is running gasp 18.11.05.000 14:06 Shane-NP[m] so...there is that...but I am limping by until I can build a new instance. 14:20 cait sorry, not a sys admin :( 14:35 PedroAmorim[m] Shane-NP: if you're not running with plack, it's very slow. The "about" page itself is not a good example as it always loads slower than other pages, plack or nto 14:40 MichaelaSieberBIB[m] Since update to koha 23.05 we have an issue with OpenID Connect Authentication. Error Message in OPAC is... (full message at <https://matrix.org/_matrix/media/v3/download/matrix.org/irPavUBtsqIBCGOpeOUaoHjz>) 14:41 Shane-NP[m] Thanks, every page is slow, might be due to hairpin/loopback as the DNS server was removed. I have a lot to unpack, just didn't know if there a tool or tools on the server to show average page load times, or data load times, etc. I have seen that on the footer of some sites...ill do some searching. 14:45 MichaelaSieberBIB[m] If the user clicks once again on the login button he is logged in his opac account. The same for koha staff when using OIDC for authentication 14:45 MichaelaSieberBIB[m] has anyone else this problem or an advice? 14:45 tcohen[m] what is the landing page after login? 14:46 cait do you mean the URL with the error or soemthing in configuration? 14:47 MichaelaSieberBIB[m] koha/mainpage.pl?auth_error=wrong_csrf_token 14:47 tcohen[m] You click login -> redirected to the OIDC provider -> login -> go back to Koha 14:47 tcohen[m] I mean the last step 14:48 tcohen[m] that mainpage.pl is probably another redirect to let you know you are missing a CSRF token 14:48 tcohen[m] I'd like to know the previous one 14:51 tcohen[m] it is probably a bug, Koha not passing the csrf_token param on the passed URL for the OIDC server 14:51 tcohen[m] but it is also possible that we are forcing CSRF too much on some page 14:52 tcohen[m] maybe we should zoom so you show me 14:52 tcohen[m] :-D 14:52 MichaelaSieberBIB[m] 😆 14:52 MichaelaSieberBIB[m] That would be great ! 14:59 tcohen[m] am I online? 14:59 ashimema yes 15:04 MichaelaSieberBIB[m] <tcohen[m]> "am I online?" <- I wrote a pm but I belive you didn't receive it ? 15:08 cait I see it 15:08 cait well... not the pm... 15:08 tcohen[m] I didn't get a pm 15:08 tcohen[m] but will ping you for a call tomorrow morning 15:08 tcohen[m] lunch+school drop time 15:09 MichaelaSieberBIB[m] tcohen[m]: awesome 15:09 MichaelaSieberBIB[m] thank you :-) 15:09 tcohen[m] will be back online in 2 hours today 15:09 cait his morning = our afternoon :) 15:09 MichaelaSieberBIB[m] See you tomorrow 15:10 MichaelaSieberBIB[m] cait: afternoon is better than night ;-) 15:10 MichaelaSieberBIB[m] bye all 15:12 cait kidclamp: around? 15:12 * kidclamp nods 15:22 cait oh almost missed you 15:23 cait kidclamp: bug 34736 15:23 huginn 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34736 major, P5 - low, ---, koha-bugs, NEW , Item checkboxes move to wrong order line in multi-receive, breaking partial receive 15:23 cait you worked on keeping the checkboxes previously... I wonder if the bug could be in the same code maybe? 15:23 cait the checkboxes "wander" to the wrong order line 15:23 cait checkboxes in the items table that is... 15:25 kidclamp will try to look 15:30 cait thank you - I think yours shoudl walk into that one too sooner or later, but took me a while to figure out how it happens 15:41 marie-luce Hi 15:41 marie-luce I need help. Is anyone familiar with "grace period" parameter on a circulation rule? 15:42 aude_c[m] A tiny bit. What's the issue? 15:44 marie-luce We have set a 21 days grace period. What will happen if the checkout has 15 days overdue and we attempt to renew it? 15:45 marie-luce I'm curious to know if Koha will charge a 15 days fine. 15:46 aude_c[m] My understanding is that it wouldn't charge the fine until the end of the grace period. 15:46 aude_c[m] So if it's returned during the grace period, no fine. 15:46 aude_c[m] But that might need to be checked!! :D 15:47 marie-luce :) 15:47 aude_c[m] There's also the FinesIncludeGracePeriod sys pref 15:48 aude_c[m] [FinesIncludeGracePeriod](https://koha-community.org/manual/23.11/en/html/circulationpreferences.html#finesincludegraceperiod) 15:48 marie-luce thanks aude_c 15:49 aude_c[m] But that's if the item is returned like 23 days late: whether to charge for 23 days of fine or just 2 days (from the end of grace period) 15:49 marie-luce It makes sense 16:06 cait aude_c[m]: is right marie-luce 16:06 cait first fine is charged after the grace period - and then it depends on the interval setting 16:07 cait if you have "at the beginning" it will charge the day after grace period, otherwise it will be grace period + interval for the first charge 16:07 aude_c[m] 👍️ Thanks for confirming @cait! 16:07 cait fines are still very common here 16:08 marie-luce cait++ aude_c[m]++ 16:08 marie-luce thanks for the info 16:10 aude_c[m] You're welcome :) 16:14 oleonard As I understand it, Koha has changed over time how borrowers.lastseen gets populated, which means for us that it's probably an inaccurate field. Does anyone have current best way to find inactive patrons? 16:15 ashimema is this related to our bug oleonard? 16:16 oleonard No 16:16 ashimema bug 15504 16:16 huginn 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15504 enhancement, P1 - high, ---, matt.blenkinsop, Signed Off , Track Patron's Last Activity 16:16 ashimema we try to make it much clearer what/how lastseen is populated 16:16 caroline_catlady I think it depends on what is considered inactive? no checkouts? expired account? 16:16 oleonard Oh cool ashimema I hadn't seen that 16:16 ashimema we also try to fix updated_on in bug 33997 16:17 huginn 04Bug https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33997 minor, P5 - low, ---, matt.blenkinsop, In Discussion , Borrowers.updated_on should not be updated by track_login 16:17 ashimema but that's got well and truly stuck with discussion 16:17 ashimema which I hate 16:17 ashimema but hey... that's me 16:17 oleonard caroline_catlady: Yes I agree it might be a different definition for different libraries. 16:17 ashimema I've spent a chunk of today uncoupling them so we can try and get 15504 moving again 16:17 ashimema yup.. 15504 does exactly that now 16:17 ashimema it puts it in the libraries control 16:17 ashimema they pick what actions should prompt the field update 16:31 oleonard I guess even with 15504 we'd have to come up with a best-possible query to report on patrons who have been inactive for a while. We don't record any statistic for login do we? 16:34 cait you can log successful logins... 16:34 cait but not sure if that is only for web 16:35 cait i thought the last_seen actually did that - for different auth mehods? 16:35 cait time to cook dinner here - cy later all :) 16:49 ashimema That is exactly what last_seen was originally designed and intended to double 16:49 ashimema Do 18:31 tcohen[m] last_seen also tracks checkins i.e. 'staff saw the patron' 18:31 tcohen[m] right? 19:04 cait tcohen: I am not sure, we should document it 19:31 tcohen[m] it would be great 20:13 cait ;)