IRC log for #koha, 2016-08-17

← Previous day | Today | Search | Index

All times shown according to UTC.

Time Nick Message
00:06 papa joined #koha
01:43 geek_cl joined #koha
01:46 kathryn joined #koha
02:07 kathryn_ joined #koha
02:36 mario joined #koha
02:37 Francesca joined #koha
03:13 reza joined #koha
03:16 reza Hello, I have a problem with opac search. It's incredibly slow! i have 8gb of memory with 8 core. 148,133 biblioitems and running on Debian package Koha version 3.2204000. 45,097 borrowers.
03:17 yaz client search result:
03:18 Z> f linux
03:18 Sent searchRequest.
03:18 Received SearchResponse.
03:18 Search was a success.
03:18 Number of hits: 235, setno 3
03:18 SearchResult-1: term=linux cnt=235
03:18 records returned: 0
03:18 Elapsed: 0.000647
03:19 but when I use the opac to search it may take 40 seconds to show the results. Do you know what is the problem??
03:20 My uname: Linux lib 3.19.0-64-generic #72~14.04.1-Ubuntu SMP Fri Jun 24 17:59:48 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
03:23 wizzyrea reza do you have local book covers?
03:23 and what version of Koha?
03:24 reza Koha version 3.2204000
03:24 no. I'm using amazon
03:24 wizzyrea ah yeah, you'll want to do the minor upgrades
03:24 and make sure that local covers are turned off if you're not using them
03:24 reza can I do it without downtime?
03:24 I mean the minor upgrade
03:25 wizzyrea it'd be pretty short downtime
03:25 reza ah OK.
03:25 thank you
03:25 ;)
03:25 wizzyrea the packages will upgrade the schema, something like, generously, 10 minutes.
03:25 very generously.
03:26 reza yeah. I have to wait till library is closed :/
03:26 wizzyrea as you do :)
03:26 * wizzyrea knows all about it
03:26 reza :) thanks man
03:26 wizzyrea no worries
03:27 be careful when you do the upgrades, make sure your repo is set to oldstable, otherwise you'll do a full version upgrade!
03:27 and I don't think you want that :)
03:27 reza is oldstable in configuration?
03:27 wizzyrea it'll be in your apt confi
03:27 config
03:28 wherever you put in the koha apt sources
03:28 assuming you run from packages
03:28 reza yes. I am using package
03:28 wizzyrea some people put them in /etc/apt/sources.list
03:28 others in /etc/apt/sources.list.d/koha.list
03:29 reza oh, mine is in koha.list
03:29 wizzyrea so where it says "stable" change it to "oldstable"
03:29 reza critical point :D
03:29 wizzyrea and that will pull from the 3.22 seris
03:29 series*
03:30 reza deb http://debian.koha-community.org/koha oldstable main
03:30 looks good?
03:30 wizzyrea yep
03:30 reza great. thank you
03:31 wizzyrea note that when a new major version is released, oldstable becomes the next version up
03:31 so in november, that will change to 16.05
03:32 reza yeah. I see that 16 is out
03:32 so Nov is the next stable release
03:32 wizzyrea and stable becomes 16.11 and so on
03:32 reza cool
03:33 I'm trying to move the Koha to amazon web service
03:33 Francesca joined #koha
03:34 reza do you know where is the zebra indexing db folder?
03:38 wizzyrea i *think* /var/spool/koha but I might be wrong
03:39 reza thanks wizzyrea ;)
03:44 Francesca joined #koha
05:01 drojf joined #koha
05:01 drojf morning #koha
05:02 dcook yo drojf
05:03 drojf hi dcook
05:09 cait joined #koha
05:12 * dcook waves to cait
05:44 * cait waves
06:29 reza I'm trying to minor upgrade my koha from 3.2204 to the latest 3.22xx with apt-get install --only-upgrade koha-common
06:30 but it's downloading 63mb of file
06:30 am I doing something wrong?
06:39 drojf that sounds like the size of the file
06:42 koha-common_3.22.09_all.deb 02-Aug-2016 11:56   60M
06:43 also, why do you not want to upgrade your whole system?
06:44 morgane joined #koha
06:49 morgane hi #koha !
07:14 gaetan_B joined #koha
07:14 gaetan_B hello
07:14 wahanui bidet, gaetan_B
07:28 aliki joined #koha
07:34 sameeenz joined #koha
07:35 sameeenz Evening all
07:37 cait joined #koha
07:37 * cait waves
07:43 drojf hi cait
07:43 * sameeenz waves back
07:43 eythian hi
07:43 wahanui hello, eythian
08:11 drojf joined #koha
08:22 LibraryClaire joined #koha
08:23 LibraryClaire morning #koha
08:24 drojf guten morgen LibraryClaire
08:24 cait morning LibraryClaire
08:24 mornign drojf :)
08:24 LibraryClaire hi drojf!
08:24 hi cait!
08:24 drojf hi cait. i said hi earlier :)
08:24 must. migrate. data.
08:25 but i want to play with packages
08:25 cait sorry... another chaos day
08:25 drojf if i had to do packaging, i would want to migrate data
08:25 cait: why chaos?
08:27 cait ah... just like every nrmal day
08:29 drojf i see :)
08:29 LibraryClaire :)
08:29 eythian hi LibraryClaire, drojf, cait
08:30 drojf hi eythian
08:30 LibraryClaire hi eythian
09:00 drotsk joined #koha
09:03 barton joined #koha
09:05 vfernandes joined #koha
09:05 vfernandes hi #koha
09:06 I need some help
09:07 after many debug and installing koha 3.22 in Debian and in Ubuntu to test, Koha 3.22 has a poor performance comparing to Koha 3.20 and I don't know why
09:08 for example: OPAC search with 20 results -> 20 opac-image.pl scripts
09:09 koha 3.20 -> 0.3ms each opac-image.pl script
09:09 koha 3.22 -> 2/3s each opac-image.pl script
09:09 why such difference between these versions?
09:13 a simple SQL query to get a systempreference is more slow in Koha 3.22
09:15 cait vfernandes: are you using plack? caching?
09:15 i thin opac-image had some problem, but I don't remember what it was
09:15 Joubu: maybe you know?
09:16 vfernandes cait: i'm not using plack
09:18 cait: besides opac-image having a problem other scripts are taking more time in Koha 3.22
09:19 cait yes
09:19 3.22 without caching and plack is slower
09:19 benchmarks?
09:20 Joubu, tcohen or someone else will be better to talk to about this
09:20 https://wiki.koha-community.or[…]enchmark_for_3.22
09:20 are you using the latest version of 3.22?
09:20 vfernandes cait: i'm using Cache::Memory and cache on Apache
09:20 3.22.6
09:20 cait yeah, that's a different thing
09:20 koha's caching
09:21 you should probably try to update to the most recent
09:21 there has been work on improving speed
09:21 3.22.9 - so yours is 3 months old already again
09:21 vfernandes I can update on installation
09:22 *one installation
09:22 but I don't think is that
09:22 How I can activate Koha cache?
09:22 cait sorry, wrong person to talk to
09:23 it's quiet in here today - maybe try again a bit later
09:24 but they will probably tell you to use the latest 3.22.x as a start -  there have been security fixes and speed improvement stuff i am quite sure
09:28 vfernandes ok... I will update from koha 3.22.6 to koha 3.22.9
09:43 updating didn't solve the problem
09:53 LibraryClaire joined #koha
10:01 cait are specific pages apart from covers slow?
10:03 vfernandes yes... specially when called from another .pl
10:04 http://catalogo2.biblioteca.is[…]-lastdocuments.pl -> 1.7s
10:04 the same paged called from opac-search.pl HTML -> 3/4s
10:05 cait hm is that a custom page?
10:05 vfernandes yes
10:06 but the code is very simple... only reads a file from the filesystem and builds the HTML
10:07 http://catalogo2.biblioteca.is[…]iblionumber=74781 -> 0.5s
10:07 the same paged called from opac-search.pl HTML -> +- 3s
10:07 these differences are huge
10:08 cait sorry, no idea
10:09 vfernandes thanks anyway cait :)
10:09 Francesca joined #koha
10:09 vfernandes i don't even know what's causing the problem: Apache, MySQL, Koha, Perl... :/
10:24 NateC joined #koha
10:28 drojf joined #koha
11:36 jzairo joined #koha
11:37 marcelr joined #koha
11:37 marcelr hi #koha
11:37 LibraryClaire hi marcelr :)
11:37 marcelr :)
11:45 kmlussier joined #koha
11:47 meliss joined #koha
11:57 lds joined #koha
12:14 ericar joined #koha
12:31 Scott-CSPL joined #koha
12:51 Dyrcona joined #koha
13:00 edveal joined #koha
13:02 JoshB joined #koha
13:09 vfernandes plack is giving the following error: Response needs to be 3 element array, or 2 element in streaming at /usr/local/share/perl/5.22.​1/Plack/Middleware/Lint.pm line 112
13:23 JesseM_ joined #koha
13:32 oleonard joined #koha
13:33 oleonard Hi all
13:35 * cait waves
13:43 mario joined #koha
13:45 LibraryClaire hi oleonard
13:54 ericar_ joined #koha
14:05 geek_cl joined #koha
14:07 vfernandes plack works on Ubuntu Server 16.04?
14:08 tubaclarinet Good morn everyone. we got blacklisted by hotmail & now i'm trying to create a spf record on our domain.
14:08 can anyone help me with this?
14:08 Scott-CSPL joined #koha
14:08 talljoy joined #koha
14:10 drojf is there a law against line breaks in bibliographic records? because there should be
14:12 tubaclarinet: that does not sound like a koha problem
14:15 cait drojf: probably not...
14:15 tubaclarinet drojf: our instance of koha is hosted by BWS & I need to convince hotmail that mail sent from BWS server is from us
14:16 amyk joined #koha
14:17 drojf do BWS know? that sounds like a problem that not only you will have then
14:17 cait hm i think i know what it is
14:17 different domain thing?
14:17 tubaclarinet cait: do tell
14:18 cait mail servers don't like it when your from/sender e-mail is a different domain than the mail server... something like that
14:19 ashimema has put some notes ont he wiki https://wiki.koha-community.or[…]i/MRenvoize/Email
14:19 it's the main reason you can now specify a different reply-to and return-path address in koha
14:19 tubaclarinet yes, we have a domain (basinlibraries.org) which is diff than BWS' domain
14:21 I spoke with a colleague at a lib which was also blacklisted by hotmail and creating a spf record was 1 of the step to remedy problem
14:26 drojf: i submitted support ticket to BWS, but haven't heard back from them yet
14:26 cait i think either that - or changing your branchemail to be from the domain you send from and use the other email fields like reply-to for the library's address
14:26 that's how we do it
14:27 we have a noreply@... that is the 'branchemail' and kohaadmin... and a return-path and only reply to is from the library
14:27 tubaclarinet cait: thank you, yes i changed the branch email add and koha admin email add this morn
14:28 cait i think return-path is also a critical one
14:28 if you don't want to end up in spam
14:29 tubaclarinet i'm tweaking the branch records now...
14:30 cait there are matching prefs too - for the e-mais not sent from the branch email address
14:33 tubaclarinet cait and drojf: I think that i have changed all applicable email adds in koha appropriately- thanks
14:34 but i still need to set up a spf record on our domain :-(
14:35 drojf that seems like something google would know how to do
14:36 so when i add a patron, the save button is now floating on top, but when i set the permissions, it is at the bottom? hmm
14:37 tubaclarinet drojf: thanks :-)
14:43 archer121 joined #koha
14:43 archer121 hi,
14:44 vfernandes can anyone help me starting plack on Ubuntu?
14:46 archer121 We are asked to make our OPAC available publicly over the internet. Due to security reasons, it was decided to set up a separate koha server for this purpose. We are planning to give this koha instance readonly access to the main koha database. What go you guys think about this? Is there a better/safer way to do this?
14:47 oleonard What security problems do you think you'll have archer121?
14:47 Our OPAC has always been public.
14:48 archer121 I really don't know. I am a student admin and my professor suggests that we do it like this.
14:48 Maybe he is not very keen to make the koha system public.
14:48 oleonard archer121: Making your OPAC read-only will prevent the creation of lists, holds, patron modification requests, patron self-registration, etc.
14:49 talljoy left #koha
14:50 kidclamp joined #koha
14:50 archer121 And we don't want anyone from outside the intranet to use these facilities.
14:52 oleonard archer121: You could require that users of the OPAC log in before they can use it.
14:53 * kidclamp waves
14:53 LibraryClaire hi kidclamp
14:53 kidclamp Hi LibraryClaire
14:53 LibraryClaire :)
14:54 archer121 We just set up koha. currently we have just setup the username and password to be the same. We plan to roll out user login and those advanced features only in a later stage.
14:57 oleonard archer121: If you're talking about limiting the OPAC to an intranet, it seems like you could do something with your Apache setup to accomplish that without creating a separate Koha server
14:58 archer121: I don't know how to advise you on that, but I do think worrying about the OPAC being a security risk is not necessary.
14:59 nengard joined #koha

← Previous day | Today | Search | Index

koha1