ubuntu-s-2vcpu-4gb-sgp1-01:~# docker-compose versionubuntu-s-2vcpu-4gb-sgp1-01:~# apt policy docker-ce | head← Previous day | Today | Next day → | Search | Index
All times shown according to UTC.
| Time | Nick | Message |
|---|---|---|
| 00:42 | schnydszch joined #koha | |
| 00:52 | schnydszch | Hi all! I am still stuck with starting my kohadev |
| 00:52 | koha-es-1 | [2022-11-04T00:46:18,945][INFO ][o.e.l.LicenseService ] [9wAl3JA] license [8c9a77ac-4ace-4e3a-998e-dddd8fcf3332] mode [basic] - valid | |
| 00:53 | that's the last line where it is stucked. hmmm.. I already adjusted vm.max_map_count | |
| 01:18 | fridolin joined #koha | |
| 01:54 | schnydszch | I added some swap into the system, re-run command "ku", now, this is what I am getting: Error response from daemon: cannot stop container: f1956468b9cdaefca5d8d6ca69e5a92333d138f66ba99a88a5e96406d3077b36: permission denied |
| 02:57 | mtj | schnydszch: try stopping , then starting again |
| 02:57 | kd; kd | |
| 02:58 | well, try control-c first, then kd; kd | |
| 02:58 | then ku | |
| 02:59 | your system probably wants 3 gigs ram, to be happy | |
| 03:01 | i always run kd twice, when restarting - just to make sure :0) | |
| 03:05 | schnydszch | hi mtj! It seems that was the problem. just deleted the first and trying out again |
| 03:06 | mtj | perhaps we should fix the 'kd' alias to run twice :) |
| 03:06 | schnydszch | well added some swap then issued: # Increase vm.max_map_count |
| 03:06 | sudo sysctl -w vm.max_map_count=262144 | |
| 03:06 | # Make it permanent | |
| 03:06 | echo "vm.max_map_count=262144" | sudo tee -a /etc/sysctl.conf | |
| 03:07 | tried kd | |
| 03:07 | [+] Running 0/4 | |
| 03:07 | ⠿ Container koha-db-1 Error while Stopping 14.1s | |
| 03:07 | ⠿ Container koha_selenium_1 Error while Stopping 14.1s | |
| 03:07 | ⠿ Container koha_es_1 Error while Stopping 14.1s | |
| 03:07 | ⠿ Container koha-memcached-1 Error while Stopping 14.1s | |
| 03:07 | Error response from daemon: cannot stop container: f5e70168dfdcb8ddf84adda9800b6d602d93ebba54bd67e1ca9b9d123b5811b2: permission denied | |
| 03:07 | now that is the error | |
| 03:08 | mtj | hmm, a reboot would fix it :/ |
| 03:08 | /etc/init.d/docker restart | |
| 03:08 | perhaps try to restart docker 1st | |
| 03:10 | schnydszch: how much RAM does your system have? | |
| 03:10 | you are running debian/ubuntu? | |
| 03:10 | schnydszch | 4GB ram, then another 4gb swap |
| 03:10 | ubuntu 20.04 | |
| 03:11 | mtj | which docker-compose version? |
| 03:11 | docker-compose version | |
| 03:11 | Docker Compose version v2.10.2 | |
| 03:12 | apt policy docker-ce | head | |
| 03:13 | Installed: 5:20.10.18~3-0~debian-buster | |
| 03:13 | schnydszch | rootubuntu-s-2vcpu-4gb-sgp1-01:~# docker-compose version |
| 03:13 | docker-compose version 1.25.0, build unknown | |
| 03:13 | docker-py version: 4.1.0 | |
| 03:13 | CPython version: 3.8.10 | |
| 03:13 | OpenSSL version: OpenSSL 1.1.1f 31 Mar 2020 | |
| 03:13 | rootubuntu-s-2vcpu-4gb-sgp1-01:~# apt policy docker-ce | head |
|
| 03:13 | WARNING: apt does not have a stable CLI interface. Use with caution in scripts. | |
| 03:13 | docker-ce: | |
| 03:13 | Installed: 5:20.10.21~3-0~ubuntu-focal | |
| 03:13 | Candidate: 5:20.10.21~3-0~ubuntu-focal | |
| 03:13 | Version table: | |
| 03:13 | *** 5:20.10.21~3-0~ubuntu-focal 500 | |
| 03:13 | 500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages | |
| 03:13 | 100 /var/lib/dpkg/status | |
| 03:13 | 5:20.10.20~3-0~ubuntu-focal 500 | |
| 03:13 | 500 https://download.docker.com/linux/ubuntu focal/stable amd64 Packages | |
| 03:13 | 5:20.10.19~3-0~ubuntu-focal 500 | |
| 03:14 | mtj | hmm, can you reboot and try again? |
| 03:14 | ooh wait.. | |
| 03:14 | schnydszch | I have already rebooted :) |
| 03:14 | mtj | aah :) |
| 03:14 | docker volume prune -f | |
| 03:14 | docker image prune -f | |
| 03:14 | docker system prune -a -f | |
| 03:15 | ..you can wipe your old docker stuff using 'prune' command | |
| 03:15 | schnydszch | oh so this command is to delete all containers? |
| 03:15 | seems like it | |
| 03:15 | mtj | yeah |
| 03:15 | i have used it for similar 'permission denied' errors | |
| 03:16 | schnydszch | and so the koha I cloned is already deleted? |
| 03:16 | mtj | koha git repo will still be there |
| 03:17 | docker prune just removes old docker stuff | |
| 03:19 | schnydszch | hmm koha folder was removed |
| 03:20 | anyway, I just cloned it again | |
| 03:23 | mtj | schnydszch: if you have more problems... upgrade docker-compose to v2 |
| 03:23 | https://docs.docker.com/compos[…]ng-the-repository | |
| 03:24 | v2 might be more reliable... | |
| 03:27 | schnydszch | hmmm.. i will just have to run those stated in the docs.docker? and my docker will be updated? |
| 03:57 | mtj | $ sudo apt-get install docker-ce docker-ce-cli containerd.io docker-compose-plugin |
| 03:57 | schnydszch: that should update you ^ | |
| 03:57 | ..you are already using the docker apt repo | |
| 03:58 | docker-compose-plugin will get you ... docker-compose v2 | |
| 03:58 | then kd; kd; ku | |
| 03:59 | ..if you get some 'permission denied' error, try the docker prune command(s) | |
| 04:04 | bag joined #koha | |
| 04:42 | schnydszch | mtk: thanks! |
| 04:42 | mtj: thanks! | |
| 06:20 | fridolin joined #koha | |
| 06:38 | Oak joined #koha | |
| 07:30 | reiveune joined #koha | |
| 07:31 | reiveune | hello |
| 07:47 | SupportLibrary[m] | Hi |
| 07:52 | Hello. I am writing to you with a request for help. After I created a new .pl file and put it in build_folder. How to reflect the changes so that it is visible in Koha? | |
| 08:00 | alex_ joined #koha | |
| 08:01 | alex_ | Bonjour |
| 08:47 | fridolin | SupportLibrary[m]: mmm how did you install Koha ? Debian Package ? |
| 08:50 | perl files should be in /usr/share/koha/lib | |
| 08:50 | SupportLibrary[m] | Yes and i found it |
| 08:50 | fridolin | you may need to restart plack middleware |
| 08:50 | SupportLibrary[m] | I put the file there and evrything is okey |
| 08:50 | fridolin | https://wiki.koha-community.or[…]ckages#koha-plack |
| 08:51 | Have a look at https://gitlab.com/koha-community/koha-gitify can be usefull | |
| 08:52 | Because package upgade may remove your changes | |
| 08:52 | you may build your own deb package i think | |
| 08:52 | or reapply changes after each upgrade | |
| 09:17 | magnuse_ joined #koha | |
| 09:22 | magnuse joined #koha | |
| 09:27 | marcelr joined #koha | |
| 09:27 | marcelr | o/ |
| 09:37 | Joubu | Can I get help on bug 30310? Could someone apply the patches and confirm they get (or don't get) the warning in the console? |
| 09:37 | huginn` | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=30310 enhancement, P5 - low, ---, jonathan.druart+koha, Failed QA , Replace Moment.js with Day.js |
| 09:39 | marcelr | they apply Joubu |
| 09:40 | let me check if I see a warning | |
| 09:42 | I am seeing: Uncaught TypeError: t is undefined /intranet-tmpl/lib/dayjs/dayjs.min_22.0600077.js:1 :246 | |
| 09:46 | Joubu | I have not idea why, but I don't get them, and they don't appear in the sandbox either |
| 09:47 | marcelr: where do you see the warning? mainpage? | |
| 09:48 | marcelr | right on mainpage |
| 09:48 | Joubu | https://staff-bz30310.sandboxe[…]/koha/mainpage.pl - not there, right? |
| 09:48 | marcelr | no my own container |
| 09:49 | Joubu | that's fun... |
| 09:49 | marcelr | debugging fun |
| 09:49 | Joubu | yes, especially when I am the only one not getting the error! |
| 09:50 | I am missing something obvious here | |
| 09:50 | marcelr | familiar experience ;) |
| 09:53 | Joubu | ha |
| 09:53 | ok | |
| 09:53 | The following paths are ignored by one of your .gitignore files: | |
| 09:53 | koha-tmpl/intranet-tmpl/lib/dayjs/plugin | |
| 09:53 | Use -f if you really want to add them. | |
| 09:54 | I have one file that is not committed there | |
| 09:54 | but it does not appear in git status because "plugin" is in .gitignore | |
| 09:54 | marcelr | thats progress |
| 09:55 | Joubu | marcelr: can you try again with the last patch please? |
| 09:57 | marcelr | warning is gone |
| 09:58 | Joubu | thanks, marcelr! |
| 09:59 | marcelr | do not ignore gitignore |
| 10:40 | Joubu | @later tell mtj aware of the 00-strict failures? https://jenkins.koha-community[…]2/333/consoleFull |
| 10:40 | huginn` | Joubu: The operation succeeded. |
| 10:40 | Joubu | @later tell mtj "Can't locate HTTPD/Bench/ApacheBench.pm in @INC" |
| 10:40 | huginn` | Joubu: The operation succeeded. |
| 11:03 | Joubu | oleonard: https://snipboard.io/fNbTzQ.jpg - shouldn't we have the other "x" back to red as well? |
| 11:05 | * ashimema | puts money on davidnind not being around yet |
| 11:07 | oleonard | Joubu I'd probably choose to change the link altogether to make it match instances like this: https://snipboard.io/6uLlny.jpg |
| 11:10 | * ashimema | likes oleonards suggestion. |
| 11:10 | ashimema | so much cleare |
| 11:10 | * so much clearer | |
| 11:12 | Joubu | oleonard: ok thanks |
| 11:14 | tcohen: curbside pickup broken, see follow-up on 30718 | |
| 11:17 | oleonard: aware of "fa-fw" | |
| 11:17 | ? | |
| 11:17 | oleonard | yes |
| 11:17 | Joubu | for fixed-width |
| 11:17 | we should use that in those situations | |
| 11:17 | <i class="fa fa-fw fa-trash"></i>Remove</a> | |
| 11:18 | instead of | |
| 11:18 | <i class="fa fa-trash"></i> Remove</a> | |
| 11:18 | shouldn't we? | |
| 11:19 | tcohen | hola #koha o/ |
| 11:20 | Joubu | forget that, that's not what their doc says |
| 11:21 | oleonard | Joubu: Was there a display issue you were hoping to solve? |
| 11:24 | Joubu | oleonard: not really, there is fa-fw on the current green 'x', and none on the 'trash' icon for guarantor. I've tested the difference and noticed that, with fa-fw you don't need the space betwee <i> and 'Remove' |
| 11:24 | but nevermind, I will remove fa-fw and add the space, to match other occurrences | |
| 11:25 | oleonard | fa-fw is used on the OPAC's bibliographic detail page for the sidebar menu because in that situation it helps the icons and text line up vertically |
| 11:28 | Joubu | bug 32108. Thanks, oleonard! |
| 11:28 | huginn` | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=32108 minor, P5 - low, ---, jonathan.druart+koha, Needs Signoff , Change "x" icon to replace patron when scheduling a pickup |
| 11:33 | oleonard | Joubu: You didn't file a bug yet for this one did you? https://snipboard.io/2ets1d.jpg |
| 11:34 | ashimema | I have one for you now oleonard.. it comes from comments from davidnind on my catalog concerns work. |
| 11:35 | He's keen for feedback that an action has taken place on modal submissions | |
| 11:35 | which I can understand | |
| 11:35 | in a few other places we add add our standard 'alert' box at the top above the header on the page.. things like 'Thing X updated successfully' | |
| 11:36 | does that make sense to you.. it feels like a slightly icky page re-arrange to me.. by adding it in there we shift the page content down.. | |
| 11:36 | I'm probably overthinking | |
| 11:36 | Joubu | oleonard: I thought I did, but cannot find it right now! Maybe I only reported it on IRC |
| 11:37 | ashimema | it's the sort of thing a toast would work nicely for |
| 11:37 | oleonard | a.... toast? |
| 11:37 | * oleonard | is reminded he hasn't had breakfast yet |
| 11:37 | ashimema | hehe |
| 11:38 | little temporary popovers that detail an action happened then dissaper a few moments later.. or are dismissable if you decide to opt to have them stay around instead of expire and dissaper | |
| 11:38 | I think we used to have something like that in sysprefs.. might still have it... | |
| 11:38 | * ashimema | checks |
| 11:39 | oleonard | Right HumanMsg |
| 11:39 | ashimema | ah yeah.. that's it. |
| 11:39 | that's a toast UX | |
| 11:39 | w don't use those anywhere else do we? | |
| 11:39 | hyst the sysprefs | |
| 11:40 | wow.. they sitck around for a while and are really in your face.. | |
| 11:40 | * ashimema | likes less obtrusive bottom right style toasts |
| 11:40 | oleonard | Yes, one or two other places I think... Advanced cataloging I think is one |
| 11:42 | huberto joined #koha | |
| 11:52 | Joubu | asking because you are having a look at erm? I am displaying a sticky dialog at the top when something wrong happens after a form submission |
| 11:57 | ashimema | Haha, I hadn't noticed that yet Joubu |
| 11:58 | Nah, I have no issues with eRM so far.. been working through the code.. everything so far that I've questioned I've gone and looked at vue docs and decided you've taken the right approach | |
| 11:58 | Actually, on that, I reckon I'm nearly ready to add my sign off | |
| 11:58 | I did comment about possibly sharing more CSS rather than doing that scoped stuff.. but at the same time I've not really dug deep enough to know if that's a silly proposal | |
| 11:59 | It's also something we can do later.. I expect polishing to continue as part of the overall UI polishing going on | |
| 12:00 | Joubu | yes, I like to have everything inside the component, but that leads to duplicate css rules... |
| 12:01 | do we change something about flatpickr and the "disabled" property? curbside pickup is broken at the OPAC because of that, but cannot find the root of the problem | |
| 12:01 | did we* | |
| 12:04 | ashimema | my feeling is that we can have css inside with the components.. but stick to only things that are really specific to that one component.. if we find ourselves repeating css then that css should get moved up into our global and thus unscoped |
| 12:05 | oleonard | That would be my instinct as well |
| 12:05 | ashimema | so in most cases I'm envisaging we won't need to have a really narrowly scoped piece and thus won't have it bunched in with the component itself. |
| 12:05 | but there might be the odd case and in those cases I love having it right there in front of me in the same component file rather than having to work my way backwards to the scss source file somewhere else... | |
| 12:05 | hope that makes sense | |
| 12:06 | but yeah.. for me it's not a QA fail right now.. just something to be aware of and consider a coding guideline for and fixes down the line. | |
| 12:06 | as for broken curbside.. no idea I'm afraid | |
| 12:12 | tcohen | Joubu: is there a report for the breakage? |
| 12:12 | Joubu | not yet |
| 12:13 | git bisect blames 30718 as well | |
| 12:27 | alex_ joined #koha | |
| 12:30 | Joubu | tcohen: bug 32111 |
| 12:30 | huginn` | 04Bug https://bugs.koha-community.or[…]_bug.cgi?id=32111 critical, P5 - low, ---, jonathan.druart+koha, ASSIGNED , Cannot schedule a pickup at the OPAC |
| 12:32 | Joubu | NSO now |
| 12:41 | schnydszch joined #koha | |
| 12:53 | davidnind[m] left #koha | |
| 13:10 | caroline joined #koha | |
| 13:19 | eugene_ joined #koha | |
| 13:35 | tundunf joined #koha | |
| 13:43 | lukeg joined #koha | |
| 13:51 | lukeg joined #koha | |
| 14:33 | caroline joined #koha | |
| 14:40 | eugene_ | Hi! I guess I'm doing good with docker. I updated the server to 22.04 ubuntu, I am now getting a different error message, it seems it has to do with apache2, with the following error message: Error:\tApache has not been designed to serve pages while\n\trunning as root. There are known race conditions that\n\twill allow any local user to read any file on the system.\n\tIf you still desire to serve pages as root then\n\tadd |
| 14:40 | -DBIG_SECURITY_HOLE to the CFLAGS env variable\n\tand then rebuild the server.\n\tIt is strongly suggested that you instead modify the User\n\tdirective in your httpd.conf file to list a non-root\n\tuser.\n | |
| 14:50 | logbot joined #koha | |
| 14:51 | pastebot joined #koha | |
| 15:04 | caroline joined #koha | |
| 15:40 | Joubu | @later tell oleonard do you think this is reasonable (the refresh section)? https://snipboard.io/sfo6We.jpg - bug 30963 |
| 15:40 | huginn` | Joubu: The operation succeeded. |
| 15:53 | huberto | Is there anything special that I need to add when making a curl request to the API? |
| 15:54 | I am testing using 'PUT /api/v1/contrib/kitchensink/patrons/patate/bother' but keep getting "Authentication failure" errors, despite having using -u 'username:password'. | |
| 15:55 | Joubu | huberto: do you know Postman? |
| 15:57 | huberto | I do, I have the same error in Postman. I have double-checked that RESTBasicAuth is enabled in the system preferences. |
| 15:59 | Joubu | With Postman you can ask for the curl version of a given query. But if it does not work with postman then you are missing something else. You need to pass a header with "Authorization: Basic" |
| 15:59 | cannot remember the exact syntax however | |
| 16:00 | huberto | I thought it would work for sure with Postman, because it's trivial to input the username and password and Postman converts it to the "Authorization: Basic [...]" header. |
| 16:01 | Maybe there's something in Kitchensink that I'm missing. The Openapi.json is fairly simple so I don't know what it could be. | |
| 16:01 | Joubu | do you have the same error with GET /patrons? |
| 16:01 | huberto | Let me give it a try |
| 16:03 | Do I absolutely need to send filters when trying /api/v1/patrons? | |
| 16:03 | Because I'm getting the same error: "Authentication failure." | |
| 16:04 | Joubu | nope, no filter |
| 16:04 | http://kohadev-intra.mydnsname[…]81/api/v1/patrons | |
| 16:05 | in tab Authorization, select type:"basic auth", then enter credential for your Koha user (needs the correct permissions, so pick your usual superlibrarian to be sure) | |
| 16:07 | huberto | Well at least it's good to know I'm not doing anything wrong. This is exactly what I'm using and I keep getting Authentication failure. |
| 16:09 | Joubu | something else in Koha logs? |
| 16:09 | are you using koha-testing-docker? | |
| 16:11 | caroline joined #koha | |
| 16:13 | huberto | Nothing that I can see in the logs, nothing's been added there for the past hour or so, despite my tests. |
| 16:15 | I am not using docker for this one, it's a standard installation, albeit "inLibro"ised ;) | |
| 16:16 | Joubu | huberto: `tail -f /var/log/$KOHA_INSTANCE/*.log`, then `restart_all` (if you have this alias), then try again, and watch the logs |
| 16:18 | The other solution is to search for "Authentication failure" in Koha/REST/V1/Auth.pm. Find which occurrence is returned to you (modify the message for instance) | |
| 16:18 | then you will know in which situation you are | |
| 16:19 | oleonard | Joubu: How did you arrive at that curbside pickups screenshot? |
| 16:19 | Joubu | look like you are missing the credential 523 unless ($credentials) { |
| 16:20 | oleonard: with the patch from 30963 | |
| 16:20 | oleonard: was it the question? Or are you asking on which screen you can find it? | |
| 16:22 | oleonard | I missed the part where you mentioned the bug number before, sorry |
| 16:26 | huberto | Joubu: thanks for the remote debugging :) I will dig down starting with Auth.pm and try to find out why the credentials are not reaching it. |
| 16:39 | oleonard | Joubu: I don't think the look of the refresh options isn't perfect but I don't know what to suggest |
| 16:40 | Joubu: I'm not sure it's working though... it does one automatic refresh and then reverts to 60 seconds | |
| 16:42 | Joubu | oleonard: did you reload plack? |
| 16:44 | oleonard | Whoops, no. That made it work, thanks |
| 16:45 | I wonder if we need a "stop" control | |
| 17:02 | davidnind[m] joined #koha | |
| 17:14 | reiveune | bye |
| 17:14 | reiveune left #koha | |
| 17:26 | caroline joined #koha | |
| 17:44 | fridolin joined #koha | |
| 18:14 | Bill joined #koha | |
| 18:17 | Guest440 | Hello! I've been running a Koha instance in AWS for a little bit. We were having some issues that seemed to be tied to Mojolicious::Plugin::OpenAPI today and so I updated/graded our koha version. Since then our instance hasn't been reachable in the load balancer's target group and I'm running out of ideas to debug it. Does anyone have experience with this? |
| 18:29 | oleonard | Sorry Guest440, at this time of day not many people are round |
| 18:30 | Guest440: There is a recent bug related to that: https://bugs.koha-community.or[…]_bug.cgi?id=28926 | |
| 18:30 | huginn` | 04Bug 28926: normal, P5 - low, ---, mtj, Pushed to oldoldoldstable , Update cpanfile for Mojolicious::Plugin::OpenAPI v2.16 |
| 18:30 | oleonard | I don't know if it's relevant to your situation. |
| 18:52 | huberto | Is there anything that would strip the Authorization header when making a request to the API? I dumped the headers and even though I can confirm that I'm sending the Authorization header with Postman or curl, it's not in the headers dumped inside Koha/REST/V1/Auth.pm. |
| 20:10 | It seems that on some of our servers Apache will strip the Authorization header by default. Adding `CGIPassAuth On` to the API directory worked perfectly. | |
| 20:31 | lukeg joined #koha | |
| 21:43 | huberto | Have a good weekend! |
| 22:38 | fridolin left #koha | |
| 23:30 | tcohen | next (monday) is ERM and OIDC |
| 23:30 | please test and provide follow-ups! | |
| 23:30 | oleonard++ | |
| 23:30 | lukeg++ | |
| 23:30 | Joubu++ | |
| 23:30 | cait++ | |
| 23:30 | kidclamp++ | |
| 23:30 | khall++ | |
| 23:30 | ashimema++ | |
| 23:30 | koha++ | |
| 23:30 | community++ | |
| 23:30 | team++ | |
| 23:31 | have a great weekend y'all | |
| 23:31 | ka kite wawe koe | |
| 23:31 | ^^ is that right, rangi[m] ? | |
| 23:48 | eugene_ joined #koha |
← Previous day | Today | Next day → | Search | Index
