Re: [Koha] New Debian install - OPAC invisible

[Mirko Tietgen]

Hi,

Mark Tompsett schrieb am 08.10.2015
> Greetings,
> 
> We owe them the best solution.

I don't think I owe anyone anything when it comes to free community
support. But I'd rather not decide what is the best solution for
everyone.


> requires Apache and Networking configuration knowledge.
> Knowledge which is not easily condensed to "a simple command that
> leads to the result people ask for".

True, there is a second command (add Listen 8080 to ports.conf).

All things Koha require a lot of special knowledge. We could close
the list then and make it autoreply "get paid support" to all questions.


> Why should default not be disabled? Perhaps […]

Perhaps not. Who knows. When someone asks about a Koha installation
on a local IP address, I'd assume a test installation on a dedicated
(virtual) machine, not a production system, unless they tell me
otherwise.


> Most of time, it likely will work, but not in all cases. Is
> debugging all those cases part of Koha's scope?I don't believe so.
> This is why a support company would be recommended. They would be
> able to navigate any pitfalls provided by the users configuration
> which could vary wildly from user to user.

So we close the list? I do not see why we should make any difference
between the Apache setup (magic only a professional can do) and Koha
(much more complex than doing some webserver config). Maybe we
should go as far as labelling free community support dangerous,
because we can never take into account all things that may or may
not be, while suppport companies could get the whole picture before
making recommendations?


> As stated before, name-based access is the default. Name based
> installations are the simplest. All that is needed is the hosts file
> hack. But a DNS entry is the correct solution, because otherwise
> someone has to run around to every computer on the network editing
> their hosts file?!

A "hack" with a wrong DNS entry is the right solution? Sounds fishy
to me.

I do not assume any other computers needing to access it in this and
many other cases. There must be thousands of local test
installations out there. Many of which lead to getting a support
company once people tested and decided they would actually like to
migrate to Koha.


> That's the wrong way to do networking, but best
> practices regarding networking is definitely beyond scope. 

You can either let people do it in a way that works, or explain the
way you think is better. "Don't do A, but B is too complicated, hire
someone" is not a constructive answer.


> Also, knowing where to put the hosts file hack ON THE CLIENT is hard.
> http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Tweak_Hosts_File

Oh, even more reading required for the easiest solution. :P


> Next, if someone decides to move their Koha on the internet, having
> already set up for name-based access makes the transition easier.

Because they all run on myDNSname.org? That will be lot of fun once
I spend the 12€ to buy that domain.


> [lots of imagination stuff]

I imagine nothing of that. I see a question that from years of
experience (I'm a support provider, we know a lot of stuff :P) I can
me assume to be about a local installation and I give advice that is
easy to follow. If that leads to a follow-up question, fine. In
dozens of cases it lead to something like "great, it's working now,
thanks a lot, koha is awesome".

Cheers,

Mirko



signature.asc
Description: OpenPGP digital signature
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] 請幫忙回覆

[long_sam.tw]

Dear bybak , 

I suppose it may be zebra index errors. 
you can exceute following operations,
change  zebra owner ,  maybe koha , 

export KOHA_CONF=/etc/koha/koha-conf.xmlexport PERL5LIB=/usr/share/koha/lib
# rebuild koha index
/usr/share/koha/bin/migration_tools/rebuild_zebra.pl  

try again , search data
BR,
longshan






-- Forwarded message --
From: Decka David 
Date: 2015-10-07 17:51 GMT+08:00
Subject: Re: [Koha] Question about language of OPAC query
To: 박병용 , koha@lists.katipo.co.nz
副本： 진승일 


I am really eager to know to the answeerr to such questions.


Chrs,

Decka

-Original Message-
From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of ???
Sent: Wednesday, October 07, 2015 5:56 PM
To: koha@lists.katipo.co.nz
Cc: 진승일
Subject: [Koha] Question about language of OPAC query

 Dear all,


I firstly installed the Koha 3.20.04.000 a few days ago. I cataloged
some Korean books and searched it on OPAC in Korean language. But the
result was incorrect. The keyword is correctly highlighted but the
number of list item is incorrect. For example, the correct number of
result record is 1 but the actual result of now is 4. If experienced
similar problems, tell me some guide for me, please!

Kind regards,


P.S.) My server info.
- Koha ver.: 3.20.04.000
- OS: Ubuntu 14.04.1
- Perl ver.: 5.018002
- MySQL ver.: 5.6.19
- Apache ver.: 2.4.7
- Zebra ver.: 2.0.44

--
Byeong-yong Bak | Librarian  CEO of Vinea Inc.
#508-1, Enterpreneurship Dev. Ctr. of Mokwon University, Daejeon City,
South Korea.
Vinea discover the value of information.


박병용 | 주식회사 비네아 대표이사
010 5195 5414, by...@vinea.co.kr
A 대전 서구 도안북로 88 목원대학교 창업진흥센터 508-1호(우 35349)
  - (Lab) 유성구 대덕대로512번길 20, 스마트벤처창업학교 2층 개발실
T 82 42 716 0095 (Fax. 0096)
S www.vinea.co.kr
비네아는 정보의 가치를 발견합니다.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


-- 
Wishing you all the best. . . .


Anthony Mao 毛慶禎
＋886 2 29052334 (voice)
+ 886 2 29017405 (FAX)

 
  
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] New Debian install - OPAC invisible

[Aparrish]

Hello all,

Thank you all for the suggestions. I had already disabled 000-config and
enabled koha, and actually deleted the default site on the recommendation of
another set of instructions, which was why I was confused. However, upon
opening the web browser again this morning the OPAC catalog is displaying
properly. Guess it just needed a refresh. Thanks again! 



--
View this message in context: 
http://koha.1045719.n5.nabble.com/New-Debian-install-OPAC-invisible-tp5856117p5856271.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

[Koha] Koha glacially slow

[Aparrish]

Hello all,

Fresh install of Koha on a Debian Jessie computer. The machine has three
gigs of RAM and an Athlon dual-core 4050-e. It's about 7 years old so I'm
going to assume I just need a better PC, but this Koha instance (a local
test server through 127.0.1.1) is so slow it's literally impossible to use,
both staff and opac side. It takes about twenty seconds to resolve any
request at all. Everything else on the PC is quite snappy though. Am I
correct in my suspicion or is something configured incorrectly? 



--
View this message in context: 
http://koha.1045719.n5.nabble.com/Koha-glacially-slow-tp5856288.html
Sent from the Koha-general mailing list archive at Nabble.com.
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha glacially slow

[Mark Tompsett]

Greetings,

Version 3.22 is still a month or so away from release. Because from a 
software perspective, I think Koha running Plack is your only hope. And that 
will be a feature available out of the box, if I am not mistaken.


However, your assumption of new hardware is a good place to start, in my 
opinion.

https://www.cpubenchmark.net/midlow_range_cpus.html
You will notice your CPU is listed near the bottom of the low to mid range 
CPU's.


I was playing around built a junk machine on partpicker 
(http://pcpartpicker.com/). I was thinking an Intel G3258 or AMD FX-4300 
3.8GHz Quad-Core Processor would be nice. They both hit the high range cpu 
page, and are relatively cheap. Anything on the high or mid-high lists would 
suffice. I personally don’t recommend anything lower, though if you have 
patience, lower is feasible to run Koha (just not well). And for the record, 
look at the benchmarks, Intel is rocking the list.


The other thing I found unusual is 3GB or ram. A lot of motherboards are 2, 
4, and if you get the really awesome boards 8 memory slots. It's usually 
recommended to match memory size and brand on slot pairs, particularly on 
Intel machines. You can take advantage of dual and quad channel memory that 
way. Also, given that your motherboard is likely an AM2 socket motherboard, 
and AMD has come out with 2 generations (AM3, AM3+) of sockets since then 
(and they are SLOW about that, making them a great upgrade option), I think 
a motherboard upgrade is in order for sure.


Depending on your budget and lifecycle plans, it is possible to get away 
with a $500 USD machine, but more money means a nicer machine which can last 
longer. Debian does a stable release every 2 years. I would recommend 
planning a computing budget for every 4 years at worst, because 7 years ago, 
I would suspect your CPU was low-end of the high list maybe high-end of the 
mid-high list. Now it's dropped 1-2 pages.


There may be some apache tweaks to speed it up, but replacing 7 year old 
hardware is probably a better place to start at this time. But if you can 
wait for 3.22, Plack may resolve your issues for less.


Hope this feedback is useful.

GPML,
Mark Tompsett

P.S. Remember database access is frequently hard drive access, unless you 
can cache your entire DB in memory ((1+(db backup size in GB 
/var/spool/koha/{instance name}/{files for same day} * 4 [because zebra is a 
memory hog, this might be possible with 3]) rounded up to a power of 2 -- my 
rough guess-timate), so an SSD might be nice. :)


P.P.S. This is also why the Koha community is working on Plack as part of 
the default install for 3.22 (if I am not mistaken), so script running 
(triggering disk access) can be cached in memory (add another 1 before 
rounding to the equation to be safe -- another guess-timation)


-Original Message- 
From: Aparrish

Sent: Thursday, October 08, 2015 12:22 PM
To: koha@lists.katipo.co.nz
Subject: [Koha] Koha glacially slow

Hello all,

Fresh install of Koha on a Debian Jessie computer. The machine has three
gigs of RAM and an Athlon dual-core 4050-e. It's about 7 years old so I'm
going to assume I just need a better PC, but this Koha instance (a local
test server through 127.0.1.1) is so slow it's literally impossible to use,
both staff and opac side. It takes about twenty seconds to resolve any
request at all. Everything else on the PC is quite snappy though. Am I
correct in my suspicion or is something configured incorrectly? 


___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha glacially slow

[Robin Sheat]

Aparrish schreef op do 08-10-2015 om 09:22 [-0700]:
> but this Koha instance (a local
> test server through 127.0.1.1) is so slow it's literally impossible to
> use,
> both staff and opac side. It takes about twenty seconds to resolve any
> request at all.

What is slow? Loading the main page, performing a search, the staff
interface, all of the above?

When it's slow and trying to load, what is using the CPU (a command like
'top') is helpful for this. Is it apache, is it Koha Perl scripts, is it
mysql, is it zebra? Or is it none of the above, in which case it might
be a network configuration issue. Also keep an eye on memory use,
especially to see if your machine is going into swap. On 3GB it
shouldn't be, but if it is noticeably, then that would indicate
something strange and would also be a problem.

When it's being slow, what does the browser say? You can bring up the
firefox element inspector by right-clicking on a page, and then use the
network tab to get a set of graphs showing the time taken to load
things, is there one thing that's slower than other things, or are they
all pretty slow?

You say "resolve" above, do you mean resolve in the technical sense
(i.e. DNS resolution), or do you mean in the colloquial "to finish"
sense?

With this sort of detail, we might be able to point you towards the
right place to look.

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


signature.asc
Description: This is a digitally signed message part
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Circulation Problem

[Robin Sheat]

Bob Ewart schreef op do 08-10-2015 om 15:59 [-0400]:
> However, I'm still having the original problem of the people on the 
> circulation desk being logged out when trying to check an item  out.  
> The item is checked out!

How do they connect to the Koha server? Is there a proxy in the middle
that could be causing issues, or some reason for them to be changing IP
address? Can you watch the session cookies in the browser, is something
deleting them? What (if anything) do the Koha error logs say? I wonder
if turning on debug would help, too. It might, though it'll cause your
error logs to have a lot of noise.

What browser are you using, and does a different browser help?

(You can turn on debug by adding SetEnv DEBUG "1" to the appropriate
virtualhost section in your apache config.)

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


signature.asc
Description: This is a digitally signed message part
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Circulation Problem

[library]

Hi there
It's a permissions thing. I'm sorry I cannot get to the settings at the
moment but what I did was set circulation users to super librarian
permission settings and then turned each one off until I hit the crucial
one, then reset everything else accordingly. Start at the bottom.

Regards
Ann Murphy
Katikati College Library

On Friday, October 9, 2015,  wrote:

> Send Koha mailing list submissions to
> koha@lists.katipo.co.nz 
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.katipo.co.nz/mailman/listinfo/koha
> or, via email, send a message with subject or body 'help' to
> koha-requ...@lists.katipo.co.nz 
>
> You can reach the person managing the list at
> koha-ow...@lists.katipo.co.nz 
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Koha digest..."
>
>
> Today's Topics:
>
>1. Re: Circulation Problem (Robin Sheat)
>
>
> --
>
> Message: 1
> Date: Fri, 09 Oct 2015 11:51:03 +1300
> From: Robin Sheat >
> To: koha@lists.katipo.co.nz 
> Subject: Re: [Koha] Circulation Problem
> Message-ID: <1444344663.31651.17.ca...@catalyst.net.nz >
> Content-Type: text/plain; charset="utf-8"
>
> Bob Ewart schreef op do 08-10-2015 om 15:59 [-0400]:
> > However, I'm still having the original problem of the people on the
> > circulation desk being logged out when trying to check an item  out.
> > The item is checked out!
>
> How do they connect to the Koha server? Is there a proxy in the middle
> that could be causing issues, or some reason for them to be changing IP
> address? Can you watch the session cookies in the browser, is something
> deleting them? What (if anything) do the Koha error logs say? I wonder
> if turning on debug would help, too. It might, though it'll cause your
> error logs to have a lot of noise.
>
> What browser are you using, and does a different browser help?
>
> (You can turn on debug by adding SetEnv DEBUG "1" to the appropriate
> virtualhost section in your apache config.)
>
> --
> Robin Sheat
> Catalyst IT Ltd.
> ✆ +64 4 803 2204
> GPG: 5FA7 4B49 1E4D CAA4 4C38  8505 77F5 B724 F871 3BDF
> -- next part --
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 473 bytes
> Desc: This is a digitally signed message part
> URL: <
> https://lists.katipo.co.nz/pipermail/koha/attachments/20151009/90f57e3c/attachment-0001.sig
> >
>
> --
>
> Subject: Digest Footer
>
> ___
> Koha mailing list
> Koha@lists.katipo.co.nz 
> https://lists.katipo.co.nz/mailman/listinfo/koha
>
>
> --
>
> End of Koha Digest, Vol 120, Issue 15
> *
>
___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Koha glacially slow

[Craig Butosi]

>"Version 3.22 is still a month or so away from release. Because from a 
>software perspective, I think Koha running Plack is your only hope. And that 
>will be a feature available out of the box, if I am not mistaken."

Really? This is fantastic. I'll hold off on troubleshooting my current Plack 
install in that case!

You guys are outstanding. Thank you for all your hard work. I'm learning so 
much from this list.

Best,

Craig Butosi, MA, MLIS, B Mus (Hons.)
LIBRARY SERVICES MANAGER
THE ROYAL CONSERVATORY
TELUS Centre for Performance and Learning
273 Bloor Street West
Toronto, ON M5S 1W2
416.408.2824 x338
www.rcmusic.ca

-Original Message-
From: Koha [mailto:koha-boun...@lists.katipo.co.nz] On Behalf Of Mark Tompsett
Sent: October-08-15 2:03 PM
To: Aparrish
Cc: koha@lists.katipo.co.nz
Subject: Re: [Koha] Koha glacially slow

Greetings,

Version 3.22 is still a month or so away from release. Because from a software 
perspective, I think Koha running Plack is your only hope. And that will be a 
feature available out of the box, if I am not mistaken.

However, your assumption of new hardware is a good place to start, in my 
opinion.
https://www.cpubenchmark.net/midlow_range_cpus.html
You will notice your CPU is listed near the bottom of the low to mid range 
CPU's.

I was playing around built a junk machine on partpicker 
(http://pcpartpicker.com/). I was thinking an Intel G3258 or AMD FX-4300 3.8GHz 
Quad-Core Processor would be nice. They both hit the high range cpu page, and 
are relatively cheap. Anything on the high or mid-high lists would suffice. I 
personally don’t recommend anything lower, though if you have patience, lower 
is feasible to run Koha (just not well). And for the record, look at the 
benchmarks, Intel is rocking the list.

The other thing I found unusual is 3GB or ram. A lot of motherboards are 2, 4, 
and if you get the really awesome boards 8 memory slots. It's usually 
recommended to match memory size and brand on slot pairs, particularly on Intel 
machines. You can take advantage of dual and quad channel memory that way. 
Also, given that your motherboard is likely an AM2 socket motherboard, and AMD 
has come out with 2 generations (AM3, AM3+) of sockets since then (and they are 
SLOW about that, making them a great upgrade option), I think a motherboard 
upgrade is in order for sure.

Depending on your budget and lifecycle plans, it is possible to get away with a 
$500 USD machine, but more money means a nicer machine which can last longer. 
Debian does a stable release every 2 years. I would recommend planning a 
computing budget for every 4 years at worst, because 7 years ago, I would 
suspect your CPU was low-end of the high list maybe high-end of the mid-high 
list. Now it's dropped 1-2 pages.

There may be some apache tweaks to speed it up, but replacing 7 year old 
hardware is probably a better place to start at this time. But if you can wait 
for 3.22, Plack may resolve your issues for less.

Hope this feedback is useful.

GPML,
Mark Tompsett

P.S. Remember database access is frequently hard drive access, unless you can 
cache your entire DB in memory ((1+(db backup size in GB 
/var/spool/koha/{instance name}/{files for same day} * 4 [because zebra is a 
memory hog, this might be possible with 3]) rounded up to a power of 2 -- my 
rough guess-timate), so an SSD might be nice. :)

P.P.S. This is also why the Koha community is working on Plack as part of the 
default install for 3.22 (if I am not mistaken), so script running (triggering 
disk access) can be cached in memory (add another 1 before rounding to the 
equation to be safe -- another guess-timation)

-Original Message-
From: Aparrish
Sent: Thursday, October 08, 2015 12:22 PM
To: koha@lists.katipo.co.nz
Subject: [Koha] Koha glacially slow

Hello all,

Fresh install of Koha on a Debian Jessie computer. The machine has three gigs 
of RAM and an Athlon dual-core 4050-e. It's about 7 years old so I'm going to 
assume I just need a better PC, but this Koha instance (a local test server 
through 127.0.1.1) is so slow it's literally impossible to use, both staff and 
opac side. It takes about twenty seconds to resolve any request at all. 
Everything else on the PC is quite snappy though. Am I correct in my suspicion 
or is something configured incorrectly?

___
Koha mailing list  http://koha-community.org Koha@lists.katipo.co.nz 
https://lists.katipo.co.nz/mailman/listinfo/koha


Note: This email message and any attachments are intended only for the use of 
the individual to which it is addressed, and may contain information that is 
privileged, confidential and exempt from disclosure under applicable law. If 
the recipient of this email is not the intended recipient (or the employee or 
agent responsible for delivering the email to the intended recipient), you are 
hereby notified that any review, dissemination, distribution or copying or 
other use of this 

Re: [Koha] Koha glacially slow

[Mark Tompsett]

Greetings,

I wrote:

"Version 3.22 is still a month or so away from release.
Because from a software perspective,
I think Koha running Plack is your only hope.
And that will be a feature available out of the box, if I am not 
mistaken."


Craig Butosi replied:

Really?


-- Really.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13791
Status: PUSHED TO MASTER.


Craig Butosi exclaimed:

This is fantastic.


-- Indeed!

GPML,
Mark Tompsett 


___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Re: [Koha] Circulation Problem

[Bob Ewart]

Hi Liz

That fixed bug 14952 and it works on a small test case I built using the 
default data.


There were a number of differences in my database structure from the 
fresh created one, so I wrote a little perl program to fix them.  My 
'permissions'  and 'userflags' tables had some differences in content 
which I changed.


However, I'm still having the original problem of the people on the 
circulation desk being logged out when trying to check an item  out.  
The item is checked out!


Also if they look at the current books checked out, it comes up with a 
message saying "Loading.  You may continue scanning" and never finds the 
items checked out.


Any suggestions?




On 10/06/2015 04:44 PM, Liz Rea wrote:

Hi Bob,

It's totally that "STRICT_TRANS_TABLES" that's doing this. I just tested
on my MariaDB (same v. as yours) with that and I get the errors too now.

Cheers,
Liz

On 07/10/15 02:06, Bob Ewart wrote:

Thanks Liz and Katrin

I'm beginning to think that it may be a problem with mariadb or
something else that was updated recently.

I'm currently running openSUSE 13.2 with mariadb 10.0.21  with Koha
3.18.10 built from a tar ball.

I tried to setup 3.18.11 and selected "install all optional data" in
the web installer for a test case.  This generated two errors (see bug
14952 
)  This was working when I created a test database on 3.18.09 last
month for my Donor Tracking plugin.  It's now failing even on 3.18.08.

I know there was a problem with changes made to mysql's
STRICT_TRANS_TABLES variable reported in bug 13523
 in
January and am wondering if there are any other recent changes.

I'm setting up a couple of fresh installs of openSUSE 13.2 and will
try to reproduce the problem.

I am also going to check my current database structure with the fresh
installs.  Our database was created somewhere around Koha 3.0 and has
been upgraded skipping a few releases.  It may be that some changes to
the structure or system variables have not be made.




___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha


___
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha