At 10:48 PM 1/3/2015 -0700, Christopher Davis wrote:

Paul,

I don't know if someone else has already mentioned this, but does your institution utilize any catalog enhancements such as cover art images, series lists, or book reviews? I remember last year when Syndetics added twenty seconds to our OPAC searches until we disabled it. Try turning off any or all of these services and then re-measure the performance.

Christopher, Thanks for your reply -- we have none of the "services" (including cover images, etc) turned on. Yesterday I verified every page in Home : Administration : System preferences (and compared to our workhorse 3.8.5 installation) to make sure we have a truly no-frills environment. Regards -- Paul

HTH,

Christopher Davis, MLS Systems & Electronic Services Librarian Uintah County Library cgdavis@co.uintah.ut.us (435) 789-6261 <http://uintahlibrary.org>uintahlibrary.org <http://facebook.com/uintahcountylibrary>facebook.com/uintahcountylibrary

On January 3, 2015 6:17:33 PM MST, Paul A <paul.a@navalmarinearchive.com> wrote: I'm really looking for some help here, please, my brain (whatever is left!) is swimming in Perl code. I'm getting the notion that maybe the db conversion (3.08 => 3.18, which reported all done) missed something, or that after two years of use, there's possibly something corrupt. If not, there's maybe a "config file" that's missing somewhere with some fine detail. All perl modules are present (except 3.18 tells me that Readonly::XS (1.02) is not installed, but I have 1.05), permissions have been verified, ps -u koha shows the daemon and zebrasrv running, mysqlcheck is clean, etc. Wireshark/pcap gives (repeatable): http://koha-admin318/cgi-bin/koha/catalogue/search.pl?q=t slow (~20 secs) and finds all results absolutely perfectly but http://koha-admin318/cgi-bin/koha/cataloguing/addbooks.pl?q=t is fast (~0.7 secs) and finds all the same results plus 73 records in reservoir. Maybe addbooks.pl doesn't need this $limit (or whatever) that search.pl requires, although the results are identical So, tried Perl debug (I don't know how to input the cookie data for admin staff, so this is the opac search, times identical): koha@hood:/usr/share/koha/opac/cgi-bin/opac$ perl -d -w ./opac-search.pl ?q=t Loading DB routines from perl5db.pl version 1.39_10 C4::Tags::CODE(0xa633720)(/usr/share/koha/lib/C4/Tags.pm:73): 73: $ext_dict and $Lingua::Ispell::path = $ext_dict; DB<1> c

=====> Romps instantaneously through 16 "Use of uninitialized value" warnings (snipped, basically in "value in string eq", $ENV{"SERVER_PORT"} and "value in concatenation (.) or string" in Auth.pm; $index, $_ and first mention of $limit in Search.pm) up to Use of uninitialized value $limit in concatenation (.) or string at /usr/share/koha/lib/C4/Search.pm line 1769. at /usr/share/koha/lib/C4/Search.pm line 1769. C4::Search::buildQuery('ARRAY(0xa7aaea0)', 'ARRAY(0xa7b5b58)', 'ARRAY(0xa7aaf60)', 'ARRAY(0xa7b5e58)', 'ARRAY(0xa7aa1b0)', 0, 'en') called at opac-search.pl line 473 =====> stops, no screen action, here for ~19 seconds, then resumes... Use of uninitialized value $expanded_facet in string eq at /usr/share/koha/lib/C4/Search.pm line 527. at /usr/share/koha/lib/C4/Search.pm line 527. C4::Search::__ANON__[/usr/share/koha/lib/C4/Search.pm:627](1, 25397) called at /usr/share/koha/lib/C4/Search.pm line 2567 C4::Search::_ZOOM_event_loop('ARRAY(0x72799a8)', 'ARRAY(0x72799f0)', 'CODE(0xb0b5878)') called at /usr/share/koha/lib/C4/Search.pm line 628 C4::Search::getRecords('(rk=(Title-cover,ext,r1="s" or ti,ext,r2="s" or Title-cover,p...', 's', 'ARRAY(0xa7aa1b0)', 'ARRAY(0xa7aad80)', 20, 0, undef, 'HASH(0xa8e8990)', 'HASH(0x7b80a90)', ...) called at opac-search.pl line 552 eval {...} called at opac-search.pl line 551

=====> and romps instantaneously through (snip, basically $priority (in Reserves.pm), $expanded_facet, $transfertwhen and plain vanilla "value in hash element" in Search.pm) 770 lines of "Use of uninitialized value" warnings, then completes: Status: 200 OK Set-Cookie: CGISESSID=d62edfbbd23aa65c2acea0f49974cb31; path=/; HttpOnly /... expected HTML, css, scripts, etc .../ </body> </html> The complete list of uninitialized values from $ perl -Mdiagnostics=-traceonly ./opac-search.pl ?q=t runs about 180 lines but I can supply it if required. I can possibly ghost 3.8.5 (also tarball) onto this machine, but I'd really like to get 3.18 up and running. I recognize that this install is tarball, but it's too late now to make radical changes, it's a big server with a lot of other databases and websites. Nothing new compared to our existing production box, except Ubuntu 14.04.1 LTS and Koha 3.18 Help, pointers, suggestions warmly welcomed. Thanks -- Paul

----------

Koha-devel mailing list

Koha-devel@lists.koha-community.org

<http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel>http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel

website : <http://www.koha-community.org>http://www.koha-community.org/

git : <http://git.koha-community.org>http://git.koha-community.org/

bugs : <http://bugs.koha-community.org/>http://bugs.koha-community.org/

--- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

Robin, Many thanks for the suggestion. But late yesterday I got frustrated, ghosted 3.8.5 to the new server and put it into production -- my theoretical deadline was 31/12/14... ;={ However, I still want 3.18 if I can. I started over on a fresh 64-bit sandbox, got all the dependencies (and copied over an "archival" tarball of ./etc/koha, ./var/lib/koha and ./usr/share/koha for history's sake) and am now trying the "package." Followed the Wiki page, but so far, very limited luck. It seems to have set up an empty mysql db, under a new name (pw unknown), with new unknown zebra name/pw, and above all a new user on the system! again pw unknown. I probably misunderstood the very limited questions during the install trying to use existing names for "instance" (and all I want is one.) Not at all like the tarball, which allowed some granularity. File permissions are all over the place, with root mixed in with group "koha318-koha" (whoever that is?) I've got a staff-admin page but no db (it's there, but Koha is looking for it's own I suppose.) No OPAC at all - apache reports "The requested URL /cgi-bin/koha/opac-main.pl was not found on this server." but it's there: -rwxr-xr-x 1 root root 2645 Dec 28 23:55 opac-main.pl ... Onwards and upwards :) Best regards -- Paul At 11:01 AM 1/5/2015 +1300, Robin Sheat wrote:

Paul A schreef op za 03-01-2015 om 20:17 [-0500]:

...

I'm really looking for some help here, please, my brain (whatever is left!) is swimming in Perl code.

I suggest that a holiday may not be the best time to ask :)

...

I'm getting the notion that maybe the db conversion (3.08 => 3.18, which reported all done) missed something, or that after two years of use, there's possibly something corrupt. If not, there's maybe a "config file" that's missing somewhere with some fine detail. All perl modules are present (except 3.18 tells me that Readonly::XS (1.02) is not installed, but I have 1.05), permissions have been verified, ps -u koha shows the daemon and zebrasrv running, mysqlcheck is clean, etc.

Try this:

http://wiki.koha-community.org/wiki/Profiling_with_Devel::NYTProf

if you're running things from the command line (which is generally fine), then you can run it as, for example:

perl -d:NYTProf ./opac-search.pl ...

rather than needing to edit the file.

This should make it pretty obvious where all it's time is spent.

Also, you can pass server variables through just as environment variables. So, SERVER_PORT could be filled in with:

SERVER_PORT=80 perl -d....

I've used this to feed cookies and client IP addresses in so that it thinks I'm logged in.

-- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF

_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/

--- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

At 11:33 AM 1/6/2015 +1300, Robin Sheat wrote:

...

However, I still want 3.18 if I can. [snip some very helpful pointers -- thank you very much] Additionally, I've added a little bit to my in-development package docs

Paul A schreef op ma 05-01-2015 om 13:13 [-0500]: that explain at a high level what a koha-create does: http://wiki.koha-community.org/wiki/Talk:Koha_on_Debian#How_koha-create_conf...

Robin, Many thanks for all your input. I started all over again using your advice and the Wiki. The only possible exception was from README.Debian (see /usr/sbin/koha-create for which variables to set) $ /usr/sbin/koha-create --help So I tried to "populate" the instance with the correct db (mysql koha18 belongs to 'koha' with all grants) and ran: $ sudo /usr/sbin/koha-create --use-db --database dbname koha18 --adminuser koha which ran and restarted apache2. It appears to have created a user koha18-koha (system, but not mysql where it's added a 'debian-sys-maint' user), and chowned to that user in multiple places (as far as I can see mostly root:koha18-koha.) However, apache is returning for the OPAC: Can't call method "config" on unblessed reference at /usr/share/koha/lib/C4/Context.pm line 779. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 84. Compilation failed in require at /usr/share/koha/opac/cgi-bin/opac/opac-main.pl line 23. BEGIN failed--compilation aborted at /usr/share/koha/opac/cgi-bin/opac/opac-main.pl line 23. and for the staff site: Can't call method "config" on unblessed reference at /usr/share/koha/lib/C4/Context.pm line 779. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 84. Compilation failed in require at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 25. BEGIN failed--compilation aborted at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 25. perl -d -w is perhaps a bit more explicit: unable to locate Koha configuration file koha-conf.xml at /usr/share/koha/lib/C4/Context.pm line 373. at /usr/share/koha/lib/C4/Context.pm line 373. C4::Context::new('C4::Context', undef) called at /usr/share/koha/lib/C4/Context.pm line 322 C4::Context::import('C4::Context') called at /usr/share/koha/lib/C4/Auth.pm line 28 C4::Auth::BEGIN() called at /usr/share/koha/lib/C4/Auth.pm line 28 eval {...} called at /usr/share/koha/lib/C4/Auth.pm line 28 require C4/Auth.pm called at ./opac-main.pl line 23 main::BEGIN() called at /usr/share/koha/lib/C4/Auth.pm line 28 eval {...} called at /usr/share/koha/lib/C4/Auth.pm line 28 unable to locate Koha configuration file koha-conf.xml at /usr/share/koha/lib/C4/Context.pm line 373. There is only one copy of koha-conf.xml: :/$ sudo find -iname koha-conf.xml ./etc/koha/sites/koha18/koha-conf.xml :/$ Is that where it's supposed to be? Thanks and best regards -- Paul

At 12:07 PM 1/7/2015 +1300, Robin Sheat wrote: [snip

...

perl -d -w is perhaps a bit more explicit: unable to locate Koha configuration file koha-conf.xml at

That's a totally different error, and it's because it doesn't have environment variables set up to find the koha-conf.xml.

Thanks - correct: the new user koha18-koha does not have it. $ sudo -Hiu koha18-koha env | grep koha USER=koha18-koha USERNAME=koha18-koha MAIL=/var/mail/koha18-koha PWD=/var/lib/koha/koha18 HOME=/var/lib/koha/koha18 LOGNAME=koha18-koha However, global env includes the correct koha path: $ printenv | grep koha PERL5LIB=/usr/share/koha/lib KOHA_CONF=/etc/koha/sites/koha18/koha-conf.xml KOHA_PATH=/usr/share/koha How to set up the new user's envvars? There's no "home" or "profile" as far as I can see, and no obvious conf file at "HOME=/var/lib/koha/koha18". Yesterday you suggested that username/pw would be in koha-conf.xml -- but this just has the [correct] mysql db credentials, and the new zebra user/pw. Is there any easy way to remove this "instance" and start over? Many thanks -- Paul

But you shouldn't be running perl against it directly anyway, in general.

...

There is only one copy of koha-conf.xml: :/$ sudo find -iname koha-conf.xml ./etc/koha/sites/koha18/koha-conf.xml :/$

Is that where it's supposed to be?

Yes.

-- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF

_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/

--- Maritime heritage and history, preservation and conservation, research and education through the written word and the arts. <http://NavalMarineArchive.com> and <http://UltraMarine.ca>

Paul A schreef op di 06-01-2015 om 19:21 [-0500]:

Thanks - correct: the new user koha18-koha does not have it.

$ sudo -Hiu koha18-koha env | grep koha USER=koha18-koha USERNAME=koha18-koha MAIL=/var/mail/koha18-koha PWD=/var/lib/koha/koha18 HOME=/var/lib/koha/koha18 LOGNAME=koha18-koha

However, global env includes the correct koha path: $ printenv | grep koha PERL5LIB=/usr/share/koha/lib KOHA_CONF=/etc/koha/sites/koha18/koha-conf.xml KOHA_PATH=/usr/share/koha

How to set up the new user's envvars? There's no "home" or "profile" as far

Stop wanting that. This won't help you at all, you don't need to have them, when they are required they are automatically set appropriately. If you know why you need them, then you also know enough to know how to set them up. If you don't know why you need them, then all you're going to do is get yourself in trouble by prodding at things you shouldn't prod at.

Yesterday you suggested that username/pw would be in koha-conf.xml -- but this just has the [correct] mysql db credentials, and the new zebra user/pw.

Yes... what else would you expect?

Is there any easy way to remove this "instance" and start over?

This is all documented: http://wiki.koha-community.org/wiki/Talk:Koha_on_Debian#Other_Commands -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF

Paul A schreef op di 06-01-2015 om 20:33 [-0500]:

Thanks Robin -- "remove" isn't on the Wiki page, but it did point me to the man page for koha-create which (last line) pointed me to koha-remove.

There is a link there, "commands provided by the Debian packages", that lists all the commands. Including koha-remove. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF