Re: [Koha] Some very sad news.
Greetings, Condolences to her family and those who were particularly close to her. Thank you for letting the broader community know, Chris. On 11/18/2022 10:19 AM, Paul Poulain wrote: [SNIP] @community : May I suggest that we name the next release "Koha 22.11 Rosalie" ? an emphatic +1 !! Le 17/11/2022 à 08:09, Chris Cormack a écrit : Tēnā koutou It is with great sadness that I pass on to you all the news that Rosalie Blake has passed away. Rosalie was the Head Librarian at Horowhenua Library Trust when Koha was started and without her Koha would not exist. But more than this Rosalie was an amazing person, a librarian who always thought outside the box, a gifted potter, a friend to many and a beloved mother and grandmother. Details around the funeral and memorial note should be available tomorrow. But I am sure you will all join me holding Rosalie's family and friends in your thoughts. Tiwhatiwha te pō, tiwhatiwha te ao. Chris Grace, Peace, Mercy, and Love, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] lockdir variable in koha config file
On 2021-03-19 3:31 p.m., Tom Hanstra wrote: I am still seeing some issues with the variable "lockdir" in the koha-conf.xml file. I'm getting the message: The configured entry in your koha-conf.xml file points to a non-writable directory (/var/lock/koha). lockdir should have the instance name (e.g. library) at the end of the path. /var/lock/koha/library This directory should be writeable for the koha instance user. GPML, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha make test
Greetings, Those instructions have not been revised in a while (see the reference to Ubuntu 14.04?). Why are you follow those instructions and not https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages or even more preferably https://wiki.koha-community.org/wiki/Koha_on_Debian? If you are merely looking to help sign things off, perhaps even just use a sandbox: https://wiki.koha-community.org/wiki/Sandboxes There is also the https://wiki.koha-community.org/wiki/KohaDevBox or https://gitlab.com/koha-community/koha-testing-docker/ Hope these pointers are helpful. GPML, Mark Tompsett From: Koha on behalf of ravikumar c Sent: December 16, 2020 7:19 PM To: koha@lists.katipo.co.nz Subject: [Koha] Koha make test Hi Tried following steps mentioned at https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_git No matter what I do at the end when I open http://127.0.1.1:8080 after following all the steps, page says "The connection was reset" and Try again. Not sure what is wrong. Couldn't find any details as well in log file. Not sure how to proceed further. Appreciate any help Regards Ravi ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Taking patron images out of db into a directory
Greetings, I wrote: Ouch! We were stuck on that version for the longest time. May you have success in coding and implementing your patch! To which Mengu Yazicioglu replied: Why do you think that we may not? We're supporting Koha since v.2, and we also did similar thing in 16.11. I apologize, I misread. I thought you were still on 3.20 for that patch. Upgrading patches is not always easy. I was offering best wishes and good will if that was the case. I also apologize for clearly not expressing myself well enough, such that I keep being understood as saying mean things. I'll go back to being silent now. Grace, Peace, Mercy, and Love to everyone... Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Taking patron images out of db into a directory
Greetings, Tomas Cohen Arazi wrote: The first step: write the tests! +1000 By writing the tests first, you know what you are coding towards, and have full test coverage for what you are going to provide a patch for. This makes everything easier for reviewing. The test plan becomes: run the tests, they have full code coverage. GPML, Mark Tompsett P.S. El sáb., 11 de abril de 2020 17:47, Mengu Yazicioglu escribió: We've developed this kind of feature first for 3.20 version with more than 1,600,000 users in the past. Ouch! We were stuck on that version for the longest time. May you have success in coding and implementing your patch! ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Taking patron images out of db into a directory
Greetings, I wrote: Mmmm... no. Owen replied: This kind of comment is completely counterproductive to meaningful cooperation. Please be constructive without being dismissive. If that had been all I wrote, then your comment would be valid in my mind. However, you didn't include the rest of the comment which explained why no: "People doing backups might forget to supplement the default Koha backup with that specific directory, and come a system failure and a restore later... they discover the photos are no more." I also said: "Putting the files in another collection that gets backed up differently would be okay." So... over all, I do not think I was dismissive, and apologize if people read it that way. I was sharing worries, because I believe someone (probably me and others), somewhere, somehow will forget to configure something, and then something bad will happen, because they forgot or didn't realize. After all, the original poster did ask, "What is your idea?" which I took to mean, "What do you think?" Sharing worries and gut reactions are valid answers to the question, though as Owen noted not useful for trying to find a good direction. +1 to Tomas' comment about command line utilities to keep sync. Katrin wrote: Afaik we already have an option to include index files and uploaded files in the backups - I think it should not be hard to add another option. If we do, that's great. If not, we have a functionality gap to solve. Additionally, system level things are usually beyond the access of librarians and only IT. Katrin addressed my concern: We could make the switch between database and directory storage a syspref maybe. +1 to this idea. Hope this clarifies. Peace, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Taking patron images out of db into a directory
Greetings, We'd like to write a patch to move patron images out of db into a directory in the server. Mmmm... no. People doing backups might forget to supplement the default Koha backup with that specific directory, and come a system failure and a restore later... they discover the photos are no more. 1. The size of database backup will be decreased, by this way one may store db backups more. Only if the pictures are on a different server. 2. Database performance will increase Theoretically, yes. But I don't see how one tiny thing would speed it up that much, unless ... (goes to update his branches and see the schema) Oh... okay... yes, perhaps patron images should be in its own linked table, so that borrower.* won't be hindered with patronimage data. 3. It will be possible to put patron images in different disk in the server 4. Easily put images gathered from other systems like (university system, personnel system, etc) Putting the files in another collection that gets backed up differently would be okay. What is your idea? I prefer the notion of in DB or externally controlled by system preferences. I think system preferences, because librarians may not have access to the technical koha-conf.xml configuration settings file. And patron images would likely fall under the responsibility of librarians, not IT people. GPML, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Debian vs Ubuntu server for koha
Greetings, On Fri, Jul 26, 2019 at 10:42:19AM +0200, Michael Kuhn wrote: > Personally, I think I heard or anyway I feel like the developers are > usually using the newer Debian version (thus Debian 9) which results > in a smoother installation process. Yes, I believe this is true as well. From: Dave Sherohman > Note that Debian 10 (buster) was released on July 6, so stretch is > no longer the latest stable version. I would expect buster to > support koha (using the stretch packages if buster packages are > not yet available) with no problems, > but I haven't tried it myself. While Buster is the latest, I have tried installing Koha on it, and had some issues. I would recommend sticking with Stretch (Debian 9) or Bionic (Ubuntu 18.04 LTS). And given that Debian is the preferred Linux Distribution, if you wish to have a GUI, you can always install that after. The default desktop manager for Ubuntu 18.04 is gnome which can be installed from Debian's wiki instructions: https://wiki.debian.org/Gnome Though, it is strange to install a desktop on your server, because Koha is access via webclients, which can be on any computer which knows how to reach your server. The only use case that I could see is a small library with no budget for multiple computers, and only a single staff person doing all the check-ins and check-outs. 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] Install guide for current version
Greetings, It is there... Click Documentation Scroll down to Install and click It will take you to Koha on Debian in the Wiki. It isn't a menu item, it is a series of clicks. GPML, Mark Tompsett -Original Message- From: Narcis Garcia Sent: Tuesday, May 28, 2019 11:10 AM To: Koha list Subject: [Koha] Install guide for current version Some time ago I annotated this path: www.koha-community.org -> Documentation --> Install ---> Koha on Debian in my recipe for new installs. And today I was becoming crazy to find this, because I only was seeing Unsupported versions documentation. As a suggestion for website menus: Add a menu item instead of only depending on menu caption. ___ 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
Re: [Koha] Hardware Koha 18.11.03
Greetings, 200 administrative users?! Simultaneously? If so, I would go with more than 4GB. As has always been said, more memory is never bad. However, I do think the 2 CPU, 50GB Drive Space VM would otherwise do. Your problem will not be hosting the data. Your problem will be accessing the data. I typically assume 100MB per simultaneous user + 2GB for OS + 10KB* items (not biblios, items) * 4. It has generally been my experience there is a 100MB footprint for a Koha access with default Apache, no special tweaks. And while the memory leaks do recover over time, they don't recover quickly. But who has the time to figure out how to configure Apache even more optimally?! And while you probably can run your OS for less than 2GB, OS's do strange things like kill processes when it starts getting tight on memory and you don't have swap configured. The 10KB I believe is the maximum size of a MARC record. Ours typically run more like 4-5K, but we have some that are large. The 4 factor accounts for a full reindex, given that Zebra + MySQL + Both trying to cache. Yes, it's overkill. But you want some room, not squeeze and barely hobble along. To summarize with your variable value plugged in: Users: 100MB * 200 = 2000MB ~= 2GB OS: 2GB Data: 10KB * 5 * 4 ~= 2GB I would recommend more like 6GB, and then if 200 checkouts/searches/whatever's happened simultaneously, you will have no issues. You will, however, find that VM Host providers tend to like powers of 2, so you may need to jump to 8, which is way more than you will need. Now, if you aren't going to have 200 people accessing your Koha all at the same second (i.e. okay, everyone, click search in 3, 2, 1... NOW *the sound of 200 simultaneous clicks*), but rather just have than many administrative users, and only 20 are on duty at any given time, then plug in 20, not 200. And then you'll see that you probably will cope okay with 4GB. You'll need to also consider patron OPAC searches into this equation too. Just my suggestions. GPML, Mark Tompsett -Original Message- From: Victor Barroso Oliveira Sent: Tuesday, March 26, 2019 10:45 AM To: koha@lists.katipo.co.nz Subject: [Koha] Hardware Koha 18.11.03 what ideal configuration of a machine to use koha with 50,000 records and 200 administrative users accessing the adm interface for loans and returns? CPU Memory HD ___ 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
Re: [Koha] Koha is using 100% CPU
Greetings, How do you know this? And out of curiosity if you type 'top' and look at the process list, do you see 404.pl? Does the 404.pl not seem to go away? The other day, I was checking, and discovered that some bot was trying to DoS/Hack a client's OPAC. I blocked the IP address, and things returned to normal. I wasn't concerned about the IP address, as it was out of country for the library. GPML, Mark Tompsett -Original Message- From: Victor Barroso Oliveira Sent: Wednesday, March 20, 2019 12:51 PM To: Koha@lists.katipo.co.nz Subject: [Koha] Koha is using 100% CPU Koha is using 100% CPU and causing slow access. How can I solve this problem? ___ 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
Re: [Koha] Chat/Poetry for a Friday (Eastern US Time)
Greetings, Reminds me of hardware related poetry I tried my hand at when I was in university, Fred. I love my 6-5-0-2 I do. It's simple paths I know so well. The blazing speed it gives to me, while Orchid compiles to hell. It should be noted that Orchid was the name of a server that we would be compiling our projects on, and the night before the due date was always the worst. I remember learning 6502 assembler on my Apple ][ and it was fun to write code there compared to the hellishly slow churning of a server being flogged to near death by hundreds of students compiling. This poem may be shared with attribution, but not varied nor sold. I love my baby too much. Whatever that CC license is, apply it. :) 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] OPAC Search too slow in Koha 18.05.05
Greetings, I don't promise to be right, but here are a couple thoughts: 1) You can use Zebra Facets -- there's a koha-conf.xml line in there somewhere. 2) Also, do you have plack turned on? Plack increases response times considerably. 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] Self-Registering Patrons allowed to choose -any- patroncategory?
Greetings, > Except that on the self-registration screen, the new patron is allowed to > choose whatever patron category he wishes, including those that should be > staff or admin only. It should also be noted that patron category has nothing to do with system permissions. So fear not, if that is your concern. 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] squeeze vs. main
Greetings, [SNIP] > [SNIP] (http://download.koha-community.org) says[SNIP] > deb http://debian.koha-community.org/koha squeeze main [SNIP] > [SNIP] (https://wiki.koha-community.org/wiki/Debian) says[SNIP] > deb http://debian.koha-community.org/koha stable main [SNIP] > What is the difference between "squeeze" and “main”? You mean what is the difference between squeeze and stable. The former is historically what stable was. There even may still be an alias for it, so as to not break older repo setups. However, the latter is the current and proper way to set up the Koha repo references. 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] Koha and 2 factor authentication
Greetings, 2 Factor Authentication is a great idea. Google Authenticator would be nice. That does work for a majority of the organization(s) I work with. However, since they are spread all over the world, some places have Google blocked or limited. As such, perhaps the latter is better. GPML, Mark Tompsett -Original Message- From: Kyle Hall Sent: Thursday, April 19, 2018 1:52 PM To: Koha Subject: [Koha] Koha and 2 factor authentication There seems to be some interest in adding 2 factor authentication to Koha. We are trying to find out what would be the most practical and easiest way to implement 2fa for Koha combined with what would be most useful for libraries that would actually *use* 2fa. The bug report filed for it is https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20476 Basically, at this point we've come up with two ideas: 1) Use Auth::GoogleAuthenticator 2) Use PrivacyIdea ( https://www.privacyidea.org/ ) Implementing GoogleAuthenticator would be much simpler I think. However, my thought is the same users that are concerned about 2fa are the same users that are concerned about privacy, and may not be interested in it simply because it means giving at least some data to Google. PrivacyIdea on the other hand would be more work for both the developer and the system admin since it is a completely separate package that would require installation and maintenance independent of Koha itself. However, it is also much more powerful and can offer a myriad of 2FA options that GoogleAuthenticator cannot. On the developer side, OTRS which is also written in Perl has implemented and may or may not have something useful we can crib from it ( https://github.com/privacyidea/privacyidea/tree/master/authmodules/OTRS ). So, what does everything think? If you want 2FA, would GoogleAuthenticator be a reasonable solution? Kyle http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) ___ 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
Re: [Koha] Out of memory
Greetings,
If you are not running plack, then you are probably experiencing 1MB per
query leak with a default apache configuration with 100MB per query used.
Digital Ocean has a nice 3GB droplet for $15/month.
As someone else also mentioned, MySQL loves to cache which leads to hogging
memory. If you have implemented the auto-increment fix
(https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix),
then a weekly reboot isn't a bad idea. Also, use MariaDB over MySQL. :)
We were experiencing problems with our Koha, then I discovered my colleague
had set up pingdom to check on the status of the OPAC every minute from
multiple locations (the equivalent of really high use). We changed it to 15
minutes from one location, implemented the auto increment fix, cleaned up
the data manually, rebooted on Sundays, and upgraded to 3GB. We have not had
a problem since with our over 120K items. However, we have a relatively low
circulation, and small to moderate use compared to the number of items we
have.
As for how much memory you should have, take a look at
/var/spool/koha/{instance name} (I think) and see the size of the two files
for any given day. Take that size and multiply it by at least 3. This will
leave you room to run a full reindex, have MySQL cache things, and still
have space for a several page loads per minute. If you have much higher use
and/or circulation, you'll need to account for that. Imagine 100 students
simultaneously accessing OPAC (okay, everyone press enter on your search in
3,2,1... now), you probably want to have 10GB (100MB*100/1024 ~= 9.75GB) in
addition to amount you calculated before. Imagine 5 librarians cataloguing
simultaneously (okay, everyone click New Record in 3,2,1... now), you
probably want another 1GB (100MB*5/1024 ~= 488MB always ceiling round up) in
addition to amount you calculated before.
Currently, I do not recommend less than 2GB. Though, like Fred, I have had a
test system hobble with 512MB. That is not recommended at all.
Ideal Size = 2 GB + Backup Size in GB * 3 + (Number of Simultaneous Users *
100 / 1024) GB. Make sure to ceiling up to nearest GB size available.
That's my attempt at this question. :)
GPML,
Mark Tompsett
-Original Message-
From: RubenoFernández
Sent: Monday, March 19, 2018 2:12 AM
To: koha@lists.katipo.co.nz
Subject: [Koha] Out of memory
Hi all,
How much memory do you need to run Koha?
I run a database with about 22000 records on a virtual server on Digital
Ocean
with 1GB memory and very low usage, but the server is crashing very often.
With dmesg I find this kind of messages several times a day:
[Sun Mar 18 16:10:10 2018] addbiblio.pl invoked oom-killer:
gfp_mask=0x24201ca, order=0, oom_score_adj=0
[Sun Mar 18 16:10:10 2018] addbiblio.pl cpuset=/ mems_allowed=0
And then MySQL crashes and restarts:
Sun Mar 18 16:10:10 2018] Out of memory: Kill process 6539 (mysqld) score
222
or sacrifice child
[Sun Mar 18 16:10:10 2018] Killed process 6539 (mysqld) total-vm:1538124kB,
anon-rss:224948kB, file-rss:0kB
From /var/log/syslog:
Mar 18 16:10:11 biblioteko systemd[1]: mysql.service: Main process exited,
code=killed, status=9/KILL
Mar 18 16:10:11 biblioteko systemd[1]: mysql.service: Unit entered failed
state.
Mar 18 16:10:11 biblioteko systemd[1]: mysql.service: Failed with result
'signal'.
Mar 18 16:10:11 biblioteko systemd[1]: mysql.service: Service hold-off time
over, scheduling restart.
Mar 18 16:10:11 biblioteko systemd[1]: Stopped MySQL Community Server.
Mar 18 16:10:11 biblioteko systemd[1]: Starting MySQL Community Server...
Just yesterday the killed process was rebuild_zebra.p, which didn't restart,
and Koha was retrieving no results for searches.
The strange thing is that Digital Ocean's own monitoring tool never reports
such memory spikes: usage is usually high but never more than 80%. Maybe the
spikes are too short? What would you recommend for a more fine-grained
monitoring of memory?
Right now my memory is this:
root@biblioteko:~# free
totalusedfree shared buff/cache
available
Mem:1016056 555304 266328 14936 194424
292164
Swap: 0 0 0
On file /etc/mysql/mysql.conf.d/mysqld.cnf the value of
"innodb_buffer_pool_size" is 385M, if that's of any help.
Do I really need more physical memory on my server?
___
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
Re: [Koha] 4 Perl Modules Not Installed on Koha 17.05.03.000
Greetings, > HTTPD::Bench::ApacheBench (0.73) I'm fairly certain that is optional and only really needed for testing. Don't worry about it. > Test::DBIx::Class (0.42) This is only needed for testing, and is a pain to install. Unless you are trying to do development, don't worry about it. > Readonly::XS (0.01) Ignore the message. If you check with a dpkg -l you'll probably find the xs version is installed. The $VERSION isn't detected or told properly. If it is installed, it is very likely the right version, even if not detected properly. > WebService::ILS (0.07) On newer versions this is the only one that you will probably care about. I usually cpan2deb it, and then sudo dpkg -i it into place, but that may not be the best solution, if it isn't already available packaged in the default or koha repositories. BTW, I do believe this a problem with the kohadevbox too, but I didn't report it when I encountered it. GPML, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] How to handle the support providers list (was Re: Spam from BestBookBuddies (OpenLX))
Greetings, Nathan A. Curulla suggested: > Maybe we should change the listing to “contributing support companies” or > something like that. While I think that is a good idea, and then companies without community participation get removed, the problem still remains: people don't read. We've put a nice disclaimer that this is not an official list and has no official seal of approval meaning to the list, and yet people still use it that way. It is impossible to educate people who refuse to read, even though the preamble write up is a rather good explanation of how to look for a Koha support provider. As such, the only reasonable course of action is to delete the list, otherwise it will continue to be used that way, no matter what we put on the page(s). Owen Leonard wrote: > It would be a duplicate listing ... and should be rejected. Who determines it is a duplicate listing? Because last time I looked some other entries looked like duplicates to me, much like OpenLX/BBB. And cleaning up duplicates is a pain. Yet another reason to just delete the list already. 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] OPAC
Greetings, > I have this on my /etc/koha/koha-sites.conf > OPACPORT= “8080” [SNIP] > Why i can not see the OPAC, only the APACHE INFORMATION PAGE? Do you have something silly like the INTRAPORT="8080"? If so, whatever is on 8080 first is what likely comes up. The difference is when virtual named hosts are used. You have an apache configuration issue. /etc/apache2/sites-enabled contain apache configuration files of things enabled. I can not help beyond this. 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] OPAC access denied Code 403 in browser
Greetings, Jonathan Druart is correct in that 3.16. is old (3.16, 3.18, 3.20, 3.22, 16.05, 16.11, 17.05 -- 6 major versions out of date) My guess is there apache configuration is off. https://wiki.koha-community.org/w/index.php?title=Koha_on_ubuntu_-_packages#403_errors_for_Gitified_or_git_clone_installs Granted, the path in the directory tag likely needs tweaking, but if you installed it, you should know how to tweak it. GPML, Mark Tompsett -Original Message- From: Jonathan Druart Sent: Wednesday, July 12, 2017 10:29 AM To: koha@lists.katipo.co.nz Subject: Re: [Koha] OPAC access denied Code 403 in browser I have no idea if this tutorial is correct, but it is old (Koha 3.16). I recommend you to read the official documentation to install Koha on Debian: https://wiki.koha-community.org/wiki/Koha_on_Debian When you will run the koha-create command, specify the --letsencrypt flag to get a certificate with everything setup correctly to run over https. On Wed, 12 Jul 2017 at 11:01 dalmeida <divalme...@gmail.com> wrote: > Hi! Thank you very much for the feedback! > I've installed Koha using this tutorial > https://www.youtube.com/watch?v=mORxmDZ3OhI, and yes I've enabled SSL > Apache > module. > I used 000-default.conf in order to redirect the site from http to https > according to what I've read on the web, in several forum sites. There are > 3 > files that must be configured in the the Apache2/sites-enabled folder: > 000-default.conf, default-ssl.conf and library.conf. Koha.conf is in the > usr/share folder as well as lib and cgi-bin folders. The http redirection > went well but then I started to get the access denied message. > Thanks! > > > > -- > View this message in context: > http://koha.1045719.n5.nabble.com/OPAC-access-denied-Code-403-in-browser-tp5939918p5939973.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 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
Re: [Koha] Life cycle of a Koha software bug
Greetings, I like the attempt to make it a little more visual. The whole blocker logic doesn't quite fit, I think. Even before you decide if it is a suggestion (enhancement) or a bug (to be fixed), the notion of searching bugzilla for similar problems seems to be missed. And it is usually at that stage where you know if it is a blocker or not. If, for example, you can't even finish a fresh install, because the web installer loops, that's kind of critical, if not a blocker. The difference being whether there is an easy hack around. If a functionality that was working in the previous version stops working in this one, that's critical if not a blocker too. At bug reporting time, you usually know. Though, in some sense, there have been cases where a bugs severity has been elevated either by others testing, the QA folks, or the Release Maintainer/Manager. But a failure does not constitute a reason to increase the severity. https://wiki.koha-community.org/wiki/Development_workflow might be useful to confirm this too. Hope this is constructive enough to help improve your diagram. :) 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] I can not use OPAC URL without the port number
Greetings, When you specify a port other than 80, you have to put the port number. Apache documentation is useful reading. http://httpd.apache.org/docs/current/vhosts/ 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] Enquiry
Greetings, The best way to learn about Koha (not KOHA -- it isn't an acronym), is to read from official sources like: - wiki.koha-community.org - www.koha-community.org Ask questions on official channels: - this mailing list - the official IRC channel (found off of): https://koha-community.org/get-involved/irc/ And watch videos from reputable Koha solution providers such as: - [ByWater Solutions, USA] https://www.youtube.com/user/bywatersolutions/videos - [L2C2 Technologies, India] https://www.youtube.com/channel/UC8leMCuq5z1gwcLWxwRz_Gw Sorry, I'm sure I missed others. 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] https 403 Forbiden
Greetings, Koha can run in https and http simultaneously. I've done it. But it requires manually configuring your apache configuration. https://ip:80 and https://ip:8080 don't work. https is generally port 443. Forbidden errors sound like an apache configuration issue as well. https://wiki.koha-community.org/w/index.php?title=Koha_on_ubuntu_-_packages#403_errors_for_Gitified_or_git_clone_installs Granted, the path may need tweaking, but you installed the system, so you should know what to change it to. http://httpd.apache.org/docs/current/ is a long, but useful read. 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] is koha right for our project run by volunteers?
Greetings, I would say yes! My 7 year old son was able to understand how to catalog some of his books using Z39.50 (https://tml.tulongaklatan.ph/). Though, he has some books through Scholastic which issue their own ISBN numbers for existing books, so you have to get a little creative in finding it by the Title, and then adding the extra ISBN number, but that really is about the most complex we've had to do. Generally, the ISBN search has worked well, though sometimes we had to search both the ISBN-13 and ISBN-10 numbers before finding something. The Z39.50 functionality of Koha makes entry easy, by importing the entries from an external source which already has the entered data. I would recommend trying that. You will need to go item by item, but given that you have to manually catalog the whole library, I don't think that is going to be a big problem. GPML, Mark Tompsett -Original Message- From: Rebecca Shtasel Sent: Tuesday, March 07, 2017 9:29 AM To: koha@lists.katipo.co.nz Subject: [Koha] is koha right for our project run by volunteers? Hello We are a small group of volunteers (one of whom is a retired school librarian) who run our synagogue's library in the UK. We would like to produce an online catalogue and are interesting in using Koha for this purpose as we haven't much money. The library has about 4000 books covering a variety of classifications (fiction, history etc) all related to Judaism. The original accessions book was lost when the library had to be moved a year ago and we have a notebook with handwritten entries for the accessions we have received since the library moved to its new home. Looking at the information to do with koha it appears very technical and we are wondering if we will be able to use it for our catalogue. We would literally be taking books off the shelves to input their information, not importing the data from elsewhere and none of us has anything more than basic computing knowledge. Given this, do you think koha is too complicated for us to use or amongst all the information related to using koha is there a very basic guide that would suit beginners like us? If you think we would struggle using koha, could you advise us on software that you think would be more user-friendly and is not too expensive? Thanking you all very much in advance for any advice you can give. Rebecca (on behalf of the group) ___ 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
Re: [Koha] problem Installing koha on ubuntu 12.04
Greetings, The newer versions of Koha are not supported on Ubuntu 12.04. Use a newer version Ubuntu, though Debian is the primary recommended OS. https://wiki.koha-community.org/w/index.php?title=Koha_on_Debian GPML, Mark Tompsett -Original Message- From: Subhranil Bhattacharyya Sent: Sunday, February 19, 2017 1:32 AM To: koha@lists.katipo.co.nz Subject: [Koha] problem Installing koha on ubuntu 12.04 Dear sir, I have some problem during KOHA installation, i am using Ubuntu 12.04 desktop-i386, when i am writing the terminal, sudo apt-get install koha common, its shows following error messege root@koha-H81M-WW:/home/koha# sudo apt-get install koha-common Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: koha-common : Depends: libarchive-extract-perl but it is not installable Depends: libgd-perl but it is not installable Depends: libsereal-decoder-perl but it is not installable Depends: libsereal-encoder-perl but it is not installable E: Unable to correct problems, you have held broken packages. root@koha-H81M-WW:/home/koha# sudo apt-get install -f Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. root@koha-H81M-WW:/home/koha# sudo apt-get install koha common Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package koha E: Unable to locate package common root@koha-H81M-WW:/home/koha# please give my suggesion, what can I do ___ 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
Re: [Koha] Common error handling in KOHA
Greetings, [SNIP] > when the application shows some error like > "BEGIN failed--compilation aborted at > /usr/share/koha/intranet/cgi-bin/events/add_event.pl line 172" -- If you are giving an actual example of an error message you see, then you should be aware that no such code exists in the Koha code-base. I just checked master: $ git grep add_event > could you please help me out to redirect > to a common page whenever the above mentioned error occurs. In a standard installation the apache site is enabled and the configuration file has: ErrorDocument 400 /cgi-bin/koha/errors/400.pl ErrorDocument 401 /cgi-bin/koha/errors/401.pl ErrorDocument 403 /cgi-bin/koha/errors/403.pl ErrorDocument 404 /cgi-bin/koha/errors/404.pl ErrorDocument 500 /cgi-bin/koha/errors/500.pl You could modify the apache configuration file to point elsewhere, but that isn't going to catch the specific "failed--compilation" case only. Contact the person who customized this file. If you encounter this type of error in your logs, you should be reporting them on bugzilla. Though, again, if these are not part of the Koha code-base, you will need to contact the person who wrote them in the first place. 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] Hosting options for Koha installation
Greetings, > ... install Koha for > ... a small association... we > have no ... IT team. good back story. > After some research I found providers offering "root servers" or "managed > servers" > which are a little costly (about € 30,- a month). Well, I'll pipe in another voice for Digital Ocean. We host on the $20/month server and we're starting to bloat. I think we'll be bouncing up to $40/month for the extra ram (we're operating like a consortium). From what you say, I'd recommend starting with the $10/month. > - Are there any recommended hosting companies and products? > It would be best if they were in Austria or Germany but also abroad ist > ok. Digital Ocean has Frankfurt servers. I recently had the pleasure of our backup system failing, and needing to migrate our backup processes. We chose Frankfurt, because Digital Ocean let's you attach Block Storage. This would also be handy if you plan on hosting a lot of PDF's, etc. for your 856$u references. :) > - If I get a root server will I be able to install it only with the > Installation instructions? > I am proficient with the command line and > I already installed and set up Koha on a "virtual machine". If you have succeeded at setting up on a virtual machine on a desktop, a host setup with any "root servers" (as you call them) is going to essentially be the same. > - Is there a better/easier way? Not that gives you *dramatic voice* ultimate power *regular voice* over your data and configuration settings. The beauty of hosting is as another person pointed out: snapshots and backups. Also, they provide and maintain the hardware for your software. No more budgeting to buy a new server every 5 years. And another benefit, offsite backups. If your building floods, burns down, or is destroyed... your data is safe. Granted, taking a backup and storing it locally would be good too, but effectively the "offsite backup" portion of a good backup plan would already be handled. I've heard stories of horrible data loss due to poor backup plans. May you succeed in finding what you want to meet your hosting needs. 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] Barcode length
Greetings, This question reminded of of a blog entry. http://blog.l2c2.co.in/index.php/2016/09/12/down-the-rabbit-hole-making-cardnumber-field-in-koha-longer-than-16-characters-limit/ It also reminded me of a bugzilla entry. https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15690 I think perhaps another patch might be in order as well. 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] Repeat this Tag not working
Greetings, You didn't notice a difference? What log files were you checking? Perhaps you aren't looking at the right ones, check others. GPML, Mark Tompsett -Original Message- From: anjoze Sent: Thursday, December 22, 2016 9:54 AM To: koha@lists.katipo.co.nz Subject: Re: [Koha] Repeat this Tag not working I've tried to raise the Debug level and found this: http://koha.1045719.n5.nabble.com/Bug-14167-New-Add-Koha-Logger-based-on-Log4perl-tp5839348p5842972.html Then I edited */etc/koha/sites/koha/log4perl.conf * and changed: log4perl.logger.intranet = *WARN*, INTRANET to log4perl.logger.intranet = *TRACE*, INTRANET but didn't note the difference. Tried *DEBUG* also with same result. - Koha version: 16.05.05 - - José Anjos -- View this message in context: http://koha.1045719.n5.nabble.com/Repeat-this-Tag-not-working-tp5914615p5914938.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 mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Field 773 $t not editable in any framework
Greetings, The field may not be editable directly, but when I encountered something similar (not this field specifically) the other day, I discovered that there was a little icon beside the field that popped up a page which let me build what was needed to fill in the data. That's just my suggestion without looking, so take with a grain of salt. Though, if true, it is far better than directly editing the data. :) 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] Z39.50 - internal server error
Greetings, My guess is that the local changes probably create a circular use. Which is why the qualification with C4:... is necessary. Did the local changes include any use statements? :) 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] KohaCon17 Dates
Greetings, I don't speak officially, but last rumour was June 13-17. June 12 is Philippine Independence Day and a national holiday. So, don't quote me on anything. GPML, Mark Tompsett -Original Message- From: Brendan Gallagher Sent: Saturday, October 29, 2016 11:31 AM To: Bob Birchall Cc: koha@lists.katipo.co.nz Subject: Re: [Koha] KohaCon17 Dates Any dates known yet? There are very cheap tickets on Singapore Airlines from San Francisco to Manila right now - I'd love to know if the dates conflict with our family plans for June now - so I can purchase the tickets or not. Thank you very much planning committee and Good luck! Thanks, Brendan On Sat, Aug 20, 2016 at 10:07 PM, Bob Birchall <b...@calyx.net.au> wrote: > Hi, > I'm reaching out to the organizers of KohaCon17 about the dates of the > conference. > > I'd urge you to set the dates as soon as possible. The earlier air travel > can be booked, the better will be the fares available. > > You've indicated that June is the likely month. There is a conference in > Canberra that we will be attending, from 23-25 June 2017. If your dates > could avoid those days and a couple either side, that will really help us. > > I'm sure others around the world will have their preferences. I wanted to > get in early. :) > > Congratulations on winning the opportunity to host KohaCon and best wishes > for your preparations. > > Thanks and regards, > Bob Birchall > Calyx > ___ > Koha mailing list http://koha-community.org > Koha@lists.katipo.co.nz > https://lists.katipo.co.nz/mailman/listinfo/koha > -- --- Brendan A. Gallagher ByWater Solutions CEO Support and Consulting for Open Source Software Installation, Data Migration, Training, Customization, Hosting and Complete Support Packages Office: Portland, OR - Office: Redding, CT Phone # (888) 900-8944 http://bywatersolutions.com i...@bywatersolutions.com ___ 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
Re: [Koha] Zebra Index stopping daily
Greetings, logrotate runs at 7:35, change your cron to 7:55. Also, there was a discussion of this, which led to https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16885 GPML, Mark Tompsett -Original Message- From: Martin House Sent: Thursday, September 15, 2016 12:24 PM To: KOHA Subject: [Koha] Zebra Index stopping daily Hey Everyone, There has been a strange issue with my install over the past 12 months or so. The Zebra index seems to stop daily. A crontab has been setup to run it daily at 7am -* 7 * * * koha-start-zebra library Despite this, I have to manually restart zebra. Any ideas? I'm currently at the latest version of Koha as I hoped it would resolve this issue. Thanks, Martin Martin House martin.ho...@gmail.com www.martindhouse.com "An unexamined life is not worth living." ___ 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
Re: [Koha] HTTPD::Bench::ApacheBench error
Greetings, Some times the version number does not report back correctly. If you have confirmed that you have installed the loader, then don't worry about the wrong number. You will notice that HTTPD::Bench::ApacheBench is not required. Unless you plan on running tests, there is no need to install it. If you have done: $ sudo apt-get install koha-perldeps koha-deps Then you should have what you need. 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] search quits working
Greetings,
If you were going to supplement your issues with a cron job, 6:00am wouldn't
fix your problem for a whole day. Since logrotate runs at around 7:35AM, it
would make more sense to trigger something like around 7:55AM. Sure it's 20
minutes of index-less-ness, but you can be assured it will be there.
Trying to start zebra again with the appropriate scripts will not cause a
hiccup. Though, you'll want to redirect output to /dev/null, so you don't
get flooded with cronjob emails.
GPML,
Mark Tompsett
-Original Message-
From: Scott Owen
Sent: Monday, August 22, 2016 8:27 AM
To: koha
Subject: Re: [Koha] search quits working
Hi all,
I still seem to be having some issues with logrotate and the zebra service
starting up
I have tried both of the options discussed in bug #
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16885
(modify postrotate, and modify koha-stop-zebra)
In my case, neither (or both) of them seems to be a "reliable" fix.
Is there any way I could kludge together some sort of CRON job to reload
the zerbra service daily ?? (at say 6:00AM) or would this be a bad thing to
do . ie: if zebra IS running, will trying to load it again cause a
major hiccup ??
any other ideas on this ?? With students returning soon, I'd really like to
get this off my "to-do" list. :-)
Thanks,
-S
On Tue, Aug 9, 2016 at 11:45 AM, Scott Owen <so...@edzone.net> wrote:
> Still no joy on this.
>
> Zebra still seems to not reload correctly.
>
> my /usr/sbin/koha-stop-zebra file looks like the following:
>
>
>
>
>
> #!/bin/sh
> #
> # koha-stop-zebra - Stop Zebra for named Koha instances
> # Copyright 2010 Catalyst IT, Ltd
> #
> # This program is free software: you can redistribute it and/or modify
> # it under the terms of the GNU General Public License as published by
> # the Free Software Foundation, either version 3 of the License, or
> # (at your option) any later version.
> #
> # This program is distributed in the hope that it will be useful,
> # but WITHOUT ANY WARRANTY; without even the implied warranty of
> # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
> # GNU General Public License for more details.
> #
> # You should have received a copy of the GNU General Public License
> # along with this program. If not, see <http://www.gnu.org/licenses/>.
>
> set -e
>
> # include helper functions
> if [ -f "/usr/share/koha/bin/koha-functions.sh" ]; then
> . "/usr/share/koha/bin/koha-functions.sh"
> else
> echo "Error: /usr/share/koha/bin/koha-functions.sh not present." 1>&2
> exit 1
> fi
>
> stop_zebra_instance()
> {
> local instancename=$1
>
> local PIDFILE="/var/run/koha/${instancename}/${instancename}-
> koha-zebra.pid"
> echo "Stopping Zebra server for $instancename"
>
> if start-stop-daemon --pidfile ${PIDFILE} --stop --quiet
> --retry=TERM/30/KILL/5; then
> return 0;
> else
> return 1;
> fi
>
> }
>
> usage()
> {
> local scriptname=$0
> cat < Stops Zebra for Koha instances.
>
> Usage: $scriptname instancename1 instancename2...
>
> EOF
> }
>
> # Parse command line.
> #[ $# -ge 1 ] || ( usage ; die "Missing instance name..." )
>
> # Loop through the instance names
> for name in "$@"
> do
> if is_instance $name ; then
> if is_zebra_running $name; then
> if ! stop_zebra_instance $name; then
> warn "Something went wrong stopping Zebra for $name."
> fi
> else
> warn "Zebra already stopped for instance $name."
> fi
> else
> warn "Unknown instance $name."
> fi
> done
>
> exit 0
>
> --
>
>
>
>
>
>
>
>
>
> On Mon, Aug 8, 2016 at 8:58 AM, Scott Owen <so...@edzone.net> wrote:
>
>> OK...I tried this, and it seems to have made no difference ?
>>
>> I'm rebooting the Koha server now, to make sure I have a clean
>> startI'll try letting it sit for a day or two and see how it goes.
>>
>> (Maybe after I made the file changes the system needs a bounce ?)
>>
>> -S
>>
>>
>> On Sat, Aug 6, 2016 at 8:03 AM, Mark Tompsett <mtomp...@hotmail.com>
>> wrote:
>>
>>> Greetings,
>>>
>>> And now for the off-list, WRONG way of doing it, because you don’t want
>>>
Re: [Koha] unable to locate koha-common
Greetings, The instructions are very clear. Open a terminal window $ sudo ls [output cut – will need to type a password] $ echo deb http://debian.koha-community.org/koha stable main | sudo tee /etc/apt/sources.list.d/koha.list [output cut] $ wget -O- http://debian.koha-community.org/koha/gpg.asc | sudo apt-key add - [output cut] $ sudo apt-get update [output cut ] $ sudo apt-get upgrade [output cut – clearly the answer is yes for an initial install] $ sudo apt-get clean [don’t think there is output, but it is cut, if there is any] $ sudo apt-get install koha-common Did any of these commands fail? Is the machine properly networked? The general goal of the Ubuntu package instructions (https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages) was that a cut and paste (except for editing files) of the boxes (they are blue in my browser) should get you a working base install, from which you could tweak the apache settings latter if you wanted to go live to the internet. Perhaps you could explain exactly what steps you are taking? GPML, Mark Tompsett From: shankar reddy Kolle<mailto:stko...@gmail.com> Sent: Saturday, August 13, 2016 4:39 AM To: Mark Tompsett<mailto:mtomp...@hotmail.com> Subject: Re: [Koha] unable to locate koha-common Dear sir, I tried using 14.04 also again same problem i am facing. "unable to locate koha-common" Thanking you, yours sincerely, Shankar Reddy On Sat, Aug 13, 2016 at 10:10 AM, shankar reddy Kolle <stko...@gmail.com<mailto:stko...@gmail.com>> wrote: Dear sir, Thank you i will try with ubuntu 14.04 and thanks for information On Sat, Aug 13, 2016 at 10:05 AM, Mark Tompsett <mtomp...@hotmail.com<mailto:mtomp...@hotmail.com>> wrote: Greetings, shankar reddy Kolle<stko...@gmail.com<mailto:stko...@gmail.com>> wrote: > I have installed Ubuntu 12.0.4 for installation of Koha using package > method. Currently, Ubuntu 14.04 LTS is the recommendation for Koha, not Ubuntu 12.04 LTS. (https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Introduction) shankar reddy Kolle<stko...@gmail.com<mailto:stko...@gmail.com>> wrote: > but i got the error "unable to locate koha-common " while > installation process. Next, did you add the appropriate repositories? https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Add_A_Koha_Community_Repository shankar reddy Kolle<stko...@gmail.com<mailto:stko...@gmail.com>> wrote: > Please let me know, how to fix it. Hope these links provide you the information to address your issues. GPML, Mark Tompsett -- Best regards Dr. Shankar Reddy Kolle Assistant Librarian (University of Horticultural Sciences, Bagalkot) College of Horticulture, Kolar Cell no.9742749018 -- Best regards Dr. Shankar Reddy Kolle Assistant Librarian (University of Horticultural Sciences, Bagalkot) College of Horticulture, Kolar Cell no.9742749018 ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] unable to locate koha-common
Greetings, shankar reddy Kolle<stko...@gmail.com> wrote: > I have installed Ubuntu 12.0.4 for installation of Koha using package > method. Currently, Ubuntu 14.04 LTS is the recommendation for Koha, not Ubuntu 12.04 LTS. (https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Introduction) shankar reddy Kolle<stko...@gmail.com> wrote: > but i got the error "unable to locate koha-common " while > installation process. Next, did you add the appropriate repositories? https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Add_A_Koha_Community_Repository shankar reddy Kolle<stko...@gmail.com> wrote: > Please let me know, how to fix it. Hope these links provide you the information to address your issues. 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] [Koha-devel] General IRC Meeting 3 August 2016 / Kohacon 2017 bidder information
Greetings, It has come to my attention that the National Library of the Philippines is still under renovation, and thus the Philippines is withdrawing its bid. Sorry. GPML, Mark Tompsett -Original Message- From: Chris Cormack Sent: Monday, August 01, 2016 5:13 PM To: koha Cc: koha-de...@lists.koha-community.org Subject: Re: [Koha-devel] General IRC Meeting 3 August 2016 / Kohacon 2017 bidder information Hi All I just want to second Mirko's email about Kohacon17, at the moment we only have the one bid (For the Philippines) as Kohacon was in Europe this year and can't be in the same continent within 3 years. However there is a real lack of information, or contact with any people in Philippines about their bid. For example the hosting organisations are named as the National Library and Onstrike, but the community has had no contact with anyone from either organisation. So we really need either a mail to the list of them to show at the next meeting. Also I would heartily recommend any organisation outside of Europe or Africa (the last 2 continents) to propose also. It isn't too late, but we do need an actual contact so we can be sure things will happen. Thanks Chris On 29 July 2016 at 20:56, Mirko Tietgen <mi...@abunchofthings.net> wrote: > Hi everyone, > > the next general IRC meeting is next week, 3 August 2016, 10:00 UTC. > > Conversion to your local time: > http://www.timeanddate.com/worldclock/fixedtime.html?msg=Koha+IRC+General+Meeting=20160803T10 > > You can find the agenda here: > https://wiki.koha-community.org/wiki/General_IRC_meeting_3_August_2016 > > This is the last meeting before we close bidding to host Kohacon > 2017. It would be nice if bidders would join us at the meeting and > tell a little about their plans. > > If the meeting is not an option, please send a message to the > mailing list explaining that you are still interested in hosting > Kohacon 2017, and please update your proposals in the Koha wiki now > if necessary: Narrow down the proposed dates if possible, update > conference locations, add contact emails(!). > https://wiki.koha-community.org/wiki/KohaCon17_Proposals > > We are still open for proposals to host Kohacon 2017 until 10 August > 2016 UTC. > > Cheers, > > Mirko > > > -- > > Mirko Tietgen > mi...@abunchofthings.net > http://koha.abunchofthings.net > http://meinkoha.de > > > > ___ > Koha-devel mailing list > koha-de...@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/ ___ Koha-devel mailing list koha-de...@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/ ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] search quits working
Greetings, https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16885 I believe my patch, however ugly it may be, accomplishes this much friendlier solution suggested by Tomas. GPML, Mark Tompsett -Original Message- From: Tomas Cohen Arazi Sent: Tuesday, August 02, 2016 10:55 AM To: Philippe Blouin ; Scott Owen ; Nombre Cc: koha Subject: Re: [Koha] search quits working Maybe we should tweak koha-stop-zebra so it returns when zebra is completely off, so people don't need to tweak their logrotate files. [SNIP] ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] search quits working
Greetings, Thank you for your zebra error logs. 20160703 07:36:05 dlpms-koha-zebra: client (pid 6341) killed by signal 15, stopping 20160705 07:36:05 dlpms-koha-zebra: client (pid 2725) killed by signal 15, stopping 20160710 07:36:06 dlpms-koha-zebra: client (pid 22889) killed by signal 15, stopping 20160712 10:32:11 dlpms-koha-zebra: client (pid 601) killed by signal 15, stopping 20160712 11:33:24 dlpms-koha-zebra: client (pid 559) killed by signal 15, stopping 20160712 11:56:11 dlpms-koha-zebra: client (pid 549) killed by signal 15, stopping 20160713 07:36:11 dlpms-koha-zebra: client (pid 526) killed by signal 15, stopping 20160713 07:40:07 dlpms-koha-zebra: client (pid 10116) killed by signal 15, stopping 20160717 07:36:07 dlpms-koha-zebra: client (pid 529) killed by signal 15, stopping I do know that the cron.daily runs at 7:35am, so you seem to be experiencing the same issue we have. I purposefully hacked a cronjob to start at 7:55am, since our library opens at 8:00am. I still, however, do not know the cause of this. Though, I don’t understand the 10:32, 11:33, or 11:56 ones. This should resolve the problem temporarily if the search quits working. $ sudo koha-start-zebra dlpms 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] Sorry, your Google login failed
Greetings, You didn't state anywhere that you actually had set your primary email address to match the one that you are authenticating with Google login. Is your Koha primary email for that local user you want to log in as matching the Google email address that you are authenticating with? GPML, Mark Tompsett -Original Message- From: tony.h Sent: Tuesday, July 12, 2016 3:44 AM To: koha@lists.katipo.co.nz Subject: [Koha] Sorry, your Google login failed Greetings, I'm having trouble getting the Google login to work since upgrading/rebuilding Koha (we rebuilt the VPS and followed the install guide: https://wiki.koha-community.org/wiki/Debian). *The problem:* 1) I can log in through my local account, no problem. 2) I then try to login through my Google account 3) After pressing allow from the accounts.google.com site, a message is displayed: /Sorry, your Google login failed. .../ The full message is below. "Log in to your account Google login Sorry, your Google login failed. The email address you are trying to use is not associated with a borrower at this library. Please note that the Google login will only work if you are using the e-mail address registered with this library. If you want to, you can try to log in using a different account Log in with Google If you do not have a Google account, but do have a local account, you can still log in:" There are no errors in the Apache log files. *Configuration* Since we had troubles, I'm following the testing guide to configure the OAuth login: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10988#c68 I removed the Google OAuth entries: DELETE FROM systempreferences WHERE variable LIKE 'GoogleO%'; I then ran the upgrade schema tool, as I did when I imported the db: sudo koha-upgrade-schema keiin_lib I added values back in admin panel (Home › Administration › System preferences > Google OpenID Connect I confirmed the 4 values are displayed in the MySQL DB: SELECT * FROM systempreferences WHERE variable LIKE 'GoogleO%'; Any thoughts? Tony -- View this message in context: http://koha.1045719.n5.nabble.com/Sorry-your-Google-login-failed-tp5895227.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 mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] [Koha-devel] Error on Koha Dev Git install
Greetings, https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#403_errors_for_Gitified_or_git_clone_installs 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] After upgrade to 16.5.00.000 - OPAC/Staff Client not showing results
Greetings, If you are running Ubuntu, you should be at version 14.04 LTS, not 12.04 LTS. There are issues with Ubuntu 16.04 LTS, and 14.04 is the recommended version of Ubuntu. 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] Configuring Koha Defaults Documentation
Greetings, If you merely expand out a few thoughts, perhaps getting a Wiki user id and password would be useful. You could then create sub-pages for explanatory sections that you have created. GPML, Mark Tompsett -Original Message- From: Peter Bradley Sent: Thursday, May 05, 2016 7:55 AM To: koha list Subject: [Koha] Configuring Koha Defaults Documentation I've written a document about configuring Koha defaults that expands on the couple of sentences provided in the Koha Debian installation instructions. It's turned out to be a rather longer document than I expected and so is probably not suitable as a replacement for what is there already, but could perhaps be linked to. Can anyone tell me who I should approach to get the document made available, if it's considered suitable? Thanks Peter -- Yn rhedeg 5k Caerdydd i Tomorrow's Generation <http://tomorrowsgeneration.co.uk/> Corriendo el 5k de Cardiff para Tomorrow's Generation <http://tomorrowsgeneration.co.uk/> Running the Cardiff 5k for Tomorrow's Generation <http://tomorrowsgeneration.co.uk/> JustGiving - Sponsor me now! <http://www.justgiving.com/tg-dyslexia> ___ 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
Re: [Koha] Webcrawler/spider
Greetings, I'm looking for a webcrawler/spider that I can use with Koha to check all my 856 fields. Why that way? You mean 856$u fields? Anyone have a recommendation? Why not create an SQL report showing the 856 field/subfields that you want and export it? That way you could get some other machine, other than your Koha server validating the URLs. This would prevent a denial of service attack from accidentally happening against your Koha server. 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] 942n flag and OpacHiddenItems setting
Greetings, Does the OpacHiddenItems setting auto set the 942n "Suppress in OPAC" flag? Two different things. It seems unlikely but thought I'd ask. 942 is at the Biblio level, as are the Framework visibility settings. OpacHiddenItems is at the Item level. 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] Strange character in bywater coverflow plugin
Greetings, I’m sorry, but does it even display properly in the staff client? When there is a problem in opac-detail and the opac-export, it is a problem that isn’t plugin specific. Are all your tables and db unicode? GPML, Mark Tompsett From: Hugo Agud Sent: Thursday, March 31, 2016 6:54 AM To: Mark Tompsett Subject: Re: [Koha] Strange character in bywater coverflow plugin hi Mark That's one of our demo server, always updated to koha 3.22.5 ; ) and yes, the data from mysql report is fine... I think it should be some part of the plugin, that it doesn't expect non english charset 2016-03-31 12:51 GMT+02:00 Mark Tompsett <mtomp...@hotmail.com>: Greetings, Is there a codification problem in the plugin or [] have [we] done something wrong with the configuration? http://demo2.orex.es/cgi-bin/koha/opac-detail.pl?biblionumber=136 I don't think it is a plugin issue. Which version of Koha are you using? And did you check your data was imported/entered properly? GPML, Mark Tompsett -Original Message- From: Hugo Agud Sent: Thursday, March 31, 2016 4:24 AM To: Koha list Subject: [Koha] Strange character in bywater coverflow plugin Good morning We have been testing the wonderful plugin coverflow from bywatersolutions, and we have seen that spanish charactes like á, é or í for example appears wrong in the coverflow You may take a look: http://demo2.orex.es/ Thanks a lot! -- *Hugo Agud - Orex Digital * *www.orex.es <http://www.orex.es>* <http://www.orex.es/> [image: http://orex.es] <http://orex.es> <http://www.orex.es> Director Passatge de la Llançadera, 3 · 08338 Premià de Dalt - Tel: 93 539 40 70 ha...@orex.es · http://www.orex.es/ No imprima este mensaje a no ser que sea necesario. Una tonelada de papel implica la tala de 15 árboles y el consumo de 250.000 litros de agua. Aviso de confidencialidad Este mensaje contiene información que puede ser CONFIDENCIAL y/o de USO RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni está autorizado a recibirlo por el remitente), no está autorizado a copiar, reenviar o divulgar el mensaje o su contenido. Si ha recibido este mensaje por error, por favor, notifíquenoslo inmediatamente y bórrelo de su sistema. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha -- Hugo Agud - Orex Digital www.orex.es Director Passatge de la Llançadera, 3 · 08338 Premià de Dalt - Tel: 93 539 40 70 ha...@orex.es · http://www.orex.es/ No imprima este mensaje a no ser que sea necesario. Una tonelada de papel implica la tala de 15 árboles y el consumo de 250.000 litros de agua. Aviso de confidencialidad Este mensaje contiene información que puede ser CONFIDENCIAL y/o de USO RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni está autorizado a recibirlo por el remitente), no está autorizado a copiar, reenviar o divulgar el mensaje o su contenido. Si ha recibido este mensaje por error, por favor, notifíquenoslo inmediatamente y bórrelo de su sistema. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] koha installation
Greetings, what is wrong with me You didn't provide enough background information. Firstly, that looks like you are attempting to install from source. What instructions are you following? What OS are you using? Which version of Koha are you attempting to install? Because that step with the Parser stuff is "ancient" history. Use Debian (7 if you have ICU indexing needs -- from what I recall) or Ubuntu (14.04 LTS), and use packages. It is much easier that way. https://wiki.koha-community.org/wiki/Debian https://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages (this has a little more explanation than the Debian version, but the Debian version is the one to follow first and foremost) 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] Redirect HTTP intranet to HTTPS
Greetings, [SNIP my less elegant solution using Rewrite rules http://httpd.apache.org/docs/current/rewrite/] I like Chris' solution better. Just to follow up with a reminder: make sure to set your StaffBaseURL and OPACBaseURL system preferences to match the proper protocols (versions 3.20.x and higher) GPML, Mark Tompsett -Original Message- From: Coehoorn, Joel Sent: Tuesday, January 26, 2016 2:55 PM To: koha@lists.katipo.co.nz Subject: [Koha] Redirect HTTP intranet to HTTPS We have our intranet staff client set to use port 8443. I have turned off port 8080. We want to require connections to the staff client use HTTPS. How can get koha or apache to redirect HTTP connections on port 8443 to the equivalent HTTPS url? Joel Coehoorn Director of Information Technology 402.363.5603 *jcoeho...@york.edu <jcoeho...@york.edu>* The mission of York College is to transform lives through Christ-centered education and to equip students for lifelong service to God, family, and society ___ 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
Re: [Koha] Upgrade from Koha version 2.5 to 3.x
Greetings, Indranil's suggested process direction seems good. Though, sometimes an upgrade is an opportunity to lose the junk. However, perhaps you may wish to take this opportunity to do a fresh install, and import cleaned MARC records into the fresh install? I would also take note of any other settings which might be useful (custom reports, branches, system preference settings, etc.). There is, after all, multiple ways to accomplish the same thing. :) 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] [Koha-devel] Getting an IP address for a koha server
Greetings, If this is a local network, then you have access to your router. Depending on your router’s model and make, you can configure it to always give the same IP address to a particular MAC address (the address of your machine’s NIC (ethernet card)). Beyond that suggestion, I can’t help you. 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] Koha 3.20.03 - koha-opac-error_log
Greetings, The file name is a partial misnomer. Warnings and errors go into this file. [Thu Oct 29 13:41:00 2015] opac-search.pl: C4::Context->userenv not defined! at /usr/share/koha/lib/C4/Items.pm line 1355. [Thu Oct 29 13:53:31 2015] opac-detail.pl: C4::Context->userenv not defined! at /usr/share/koha/lib/C4/Items.pm line 1355., referer: https://www.google.com.tr/ I searched these errors but I didn't found about it. What does these means? How can I solve these errors? These two messages are WARNINGS. If you had opac logins enabled, and you logged in, you would find that these messages would not be triggered. Yes, these will fill the logs, but that is the real problem to solve, not the messages themselves. Also, you didn't state what version of Koha you are using, because it is likely line 1363 in master. 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] Disable displaying items from other locations (independent branches)
Greetings, To follow up on Katrin's passing note, I believe the bug she was thinking about was: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10276 This would improve things, I think, but I'm not sure it solves every problem. 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] 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
Re: [Koha] Koha glacially slow
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] New Debian install - OPAC invisible
Greetings, Your apache settings have the default site first THEN the Koha site. Three solutions: 1) Pay a support company to set it up for you. Seriously, sometimes a bill for someone else's 30 minutes is cheaper than you spending an entire day trying to do it yourself. 2) Use name based access! You can do just a local machine access by name based access. This requires setting up a DNS entry OR the equivalent. -- As I posted in another post: "If you don’t know how to do that or the equivalent, I’ll call upon the ancient spirits of evil with the Windoze incantation of C:\windows\system32\drivers\etc\hosts. *casts the call a troll spell* *running away* THIS IS NOT HOW YOU SHOULD DO IT PERMANENTLY!" 3) Fixing the Apache order 3a) I don't know how off the top of my head, name based access is way easier! 3b) DON'T EVEN THINK ABOUT IT, BUT YOU ARE PROBABLY GOING TO DO IT. (ARG! Those were the first suggestions just posted) 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] New Debian install - OPAC invisible
Greetings,
We owe them the best solution. The best solution doesn't break others, and
disabling default has that capacity. That's why packages are name-based by
default. If Koha is accessed by IP, that's not default and requires Apache
and Networking configuration knowledge. Knowledge which is not easily
condensed to "a simple command that leads to the result people ask for".
Networking and Apache configuration is really running the boundary of Koha
support. This is subtly demonstrated by the express lack of networking
references on the Debian pages.
Why should default not be disabled? Perhaps there are other sites on the
machine, and disabling default isn't the only problem one, and disabling may
affect other web applications which the user is unaware of. If there are
others, one may find themselves at something other than "It Works!" but not
the OPAC either. So the suggested quick solution may not solve the problem
all the time.
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.
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?! That's the wrong
way to do networking, but best practices regarding networking is definitely
beyond scope. Again, a support company would be able to help deal with that.
The /etc/koha/koha-sites.conf file can help determine
http://{OPACPREFIX}{InstanceName}{OPACSUFFIX}{DOMAIN}:{OPACPORT}
and
http://{INTRAPREFIX}{InstanceName}{INTRASUFFIX}{DOMAIN}:{INTRAPORT}
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
if the CLIENT is a linux box: /etc/hosts
if the CLIENT is a windows box: C:\windows\system32\drivers\etc\hosts
-- even C: could be wrong. :( -- which is why networking advice is really
hard to do!
And even once tweaked, only that client will work for name-based access,
because the DNS entry wasn't set up. This is why the Ubuntu instructions do
it to the server's /etc/hosts file, and then proceed to use lynx on the
server to set Koha up.
Next, if someone decides to move their Koha on the internet, having already
set up for name-based access makes the transition easier.
Just think of an imaginary domain: forthepublic.com
Locally, it is hacked to have library.forthepublic.com.
Then one day forthepublic.com is set up with the appropriate DNS records as
required (and remove any hacks), and magically library.forthepublic.com is
hosted on the internet.
Not to mention, bookmarks will break when they aren't changed, but the ip
address has.
No one likes reading documentation. People rarely do.
http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#It_Works.21
(That points to the relevant Apache configuration documentation)
And imagine they disable the default site, and then install some software
that depends on and they can't get it working. So they ask that software
group for help. And they re-enable it. And now Koha breaks again. The
cleanest solution is to only touch what you need to touch. DNS entries and
name-based access are really, really clean.
If one insists on IP address access, I would avoid port 80 for the OPAC.
This ensures the default site is untouched, and Koha will not break or be
broken by another application which may or may not be installed in the
future.
I do apologize for the "longish rage emails" (frustration perhaps, not
rage), but I strongly feel that disabling default is the wrong solution and
should be avoided. So, this isn't an "Apache default website fetish". It is
an aim to reduce the amount of support needed long term, because of
potential horrible cross-interactions or server relocations. Less is more.
Less change and more default (pun intended) is good.
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] Hiding search results for a different library
Greetings, We have two libraries, and we'd like to kinda keep them separate. Then why not have two instances? If you installed using packages (the recommended way), each library being their own instance would keep things completely separate. http://wiki.koha-community.org/wiki/Commands_provided_by_the_Debian_packages The down side being you'd have to search two separate sites in order to look through both. 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] Self-checkout behavior
Greetings, Your inquiry also reminded me of: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10799 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14298 Log in cookies are based on domain name. Since the SCO has the same domain name as the OPAC, you will inevitably encounter the problem if you are not careful. GPML, Mark Tompsett -Original Message- From: uwe Sent: Saturday, September 12, 2015 11:22 AM To: koha@lists.katipo.co.nz Subject: [Koha] Self-checkout behavior Hello, I have a question to the self-checkout-module. As documentated I enabled in the preferences "AutoSelfCheckAllowed" with "AutoSelfCheckID" (a special user with circulation rights, for example "MyCheckoutRobot") and the "AutoSelfCheckPass". Then I log in in the OPAC as a another patron (e.g. "Uwe") without any rights and go to the self-checkout-page and log in too. If I now go back to the OPAC I'm suddenly logged in as the in the preferences defined user (in this example "MyCheckoutRobot"). Perhaps I don't understand the module. But how can I prevent the user change in the OPAC from "Uwe" to "MyCheckoutRobot"? What I only want is that a normal patron can use the self-checkout-system. Thanks and best wishes Uwe ___ 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
Re: [Koha] Koha error 2.2.8
Greetings, Koha no longer supports the native windows version 2.2.8 You can run Koha on Windows or Macs using VirtualBox or some other virtualization software. https://www.virtualbox.org/ Grab a debian ISO https://www.debian.org/distrib/ And once you have Debian running as a VM, follow current instructions. http://wiki.koha-community.org/wiki/Debian GPML, Mark Tompsett P.S. Don't run a production system virtualized on a Windows machine. It's not recommended. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Looking for a recommendation - SMS Service in Canada
Greetings, I'm setting up patron notifications by SMS but have no clue which SMS provider to use. Any Canadian libraries want to recommend one? I'm not a library, nor a librarian; I'm a developer. However, I am Canadian and about an 1.5 hours away it seems. Perhaps something like this link is useful to you? http://www.rogers.com/web/content/wireless-text/email_text_commands I found it while attempting to test this bug: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9021 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] Koha syck parser error
Greetings, For those thinking, Attachment 40979? 40442? The bug number is 10988. http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10988 And the current attachment number is 40979. And no, this is likely a data error caused by a poor manual edit rather than using 'git bz'. I would hate to think someone manually edited the YAML::Syck library. GPML, Mark Tompsett -Original Message- From: Tomas Cohen Arazi Sent: Wednesday, August 12, 2015 7:36 PM To: schnydszch Cc: koha Subject: Re: [Koha] Koha syck parser error Maybe I'm missing something, but: what are you trying to do? Are you testing a specific bug? Or is it a general problem you found in Koha? 2015-08-12 12:50 GMT-03:00 schnydszch eugen...@yahoo.com: In koha 3.20.2 3.18.9 debian package install tested for both, when editing the admin.pref in order to add the lines for google authentication, I'm getting the following errors when I go to Administration - Global System Preference - Administration: Software error: Syck parser (line 117, column 15): syntax error at /usr/lib/perl5/YAML/Syck.pm line 72. I followed either attachment 40979 and for the most part attachment 40442. I was able to make this work in 3.20.1 and 3.18.8 a month ago following attachment 40442. Is there something I'm missing? Or is there a bug somewhere? YAML syck is 0.71 and is a debian 7 server. Thanks! -- View this message in context: http://koha.1045719.n5.nabble.com/Koha-syck-parser-error-tp5849406.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 -- Tomás Cohen Arazi Prosecretaría de Informática Universidad Nacional de Córdoba ✆ +54 351 5353750 ext 13168 GPG: B76C 6E7C 2D80 551A C765 E225 0A27 2EA1 B2F3 C15F ___ 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
Re: [Koha] Bug in mainpage.pl?
Greetings, Many of those errors, I have been working on submitting patches as I run into them in areas I am working on. As the other response said they aren't a significant concern, except for floody logs (which I thoroughly deplore and aim to fix every chance I encounter them while working). GPML, Mark Tompsett -Original Message [CUT AND EDIT] - From: Angel Sent: Tuesday, July 21, 2015 10:04 AM search.pl: CGI::param called in list context from package main line 169, this can lead to vulnerabilities. See the warning in Fetching the value or values of a single named parameter at /usr/share/perl5/CGI.pm line 436. I was searchig for the warning, and it seems that mainpage.pl in koha-common needs to be fixed, but I don't know how. Or perhaps there is other way avoid the error. REgards and thanks in advanced ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Proposal to remove the 'Paid support' list
Greetings, Mirko Tietgenmi...@abunchofthings.net wrote: Do you think they will lie to git? How will they do that? :) I have various bugs submitted. For example, bug 5010. That was a major contribution I feel. However, I also have tiny contributions, like bug 14112. It's a contribution, but does that 2 byte patch carry the same worth as 5010? Imagine staying listed indefinitely because you find a 2 byte patch to write every other year? They won't lie to git, they'll lie to the client who is seeking to hire someone to handle a proposal. We're active in the community. We're on a list. 1) Will the client actual note the date? a) If so, great the client will know how hyped the community involvement is. b) If not, which is more likely since they aren't reading our beautiful disclaimer at the top of the paid support pages, they'll be duped. 2) Will the client read any beautiful disclaimer we put at the top? a) If so, great the client will know how hyped the community involvement is. b) If not, which is already the case, they'll be duped. And given the misuse of the list currently, this is why I proposed a tombstone, rather than keeping any kind of list. 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] Proposal to remove the 'Paid support' list
Greetings, Steve Sowdersow...@andrews.edu wrote: How about a list of providers that is recommended by _customers_? With a provider being removed one year after the last recommendation. I hate to sound pessimistic, but anyone can pretend to be a customer. The only easy to maintain list that can't be misunderstood by anyone in any culture is no list. Additional bonus: no legal liabilities. 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] Proposal to remove the 'Paid support' list
Greetings, It would be nice if people could find out I am contributing stuff without learning to understand bugzilla. Sadly, if a person's name continues to appear on a list in the same place, those requesting quotes for proposals will not pay attention and learn what the list is. The learning curve forces learning. I'm sorry it is harsh, but people tend to take the path of least resistance which includes remaining ignorant of how the list works. My proposal would be to have something similar to the »Patches pushed for release« thingy on http://dashboard.koha-community.org. Maybe a longer time span (like, people/ companies that have contributed over the last year), but no »all time contributers« list that would bring us lots of one time »contributions« for the sake of being listed forever. A list like Name/Organization, Country, Date of Last Accepted Patch capped since old stable initial release would be nice, but it opens it back up to this stupidity which we want to avoid, because marketing people may hype and lie. No list provides no opportunity for them to hype and lie. 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] Proposal to remove the 'Paid support' list
Tomas Cohen Arazitomasco...@gmail.com wrote: I propose we replace the current listing with (a) nothing or (b) some pie diagram with companies/institutions contributions (git log, or what best addresses the need) to the project. Nothing is a little harsh. A tombstone would be better. For example, We no longer list support providers, as this list was being used to exclude people from bidding on projects, and declaring themselves official or registered partners when Koha never had such a program or status. The list's purpose was to provide an easy list of people in various countries, not give any status to them or statement of quality about them. If you wish to see who is active in the community please search: - bugs.koha-community.org for submissions and comments by that person or company. - dashboard.koha-community.org for people who demonstrate themselves active in the community. - and if you are technical, feel free to look through the git log of the koha project cloneable from git://git.koha-community.org/koha.git We apologize for any inconvenience, but such ongoing, gross misrepresentations of the list required this list to be removed. The problem with (b) is it still provides a way for people to misrepresent. A variation on (a) in the only way. 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] Swapping Addresses
Greetings, Paul A wrote: Ummm... some of us have production cycles of two (maybe three) years (exceptions made for security) -- exactly... let's review security updates recently. Google koha security: 2013-07-29 - 3.12.3, 3.10.9, 3.8.16, 3.6.12 2014-02-07 - 3.14.3, 3.12.10, 3.10.13, 3.8.23 2014-12-10 - 3.18.1 2014-12-11 - 3.16.5 2015-06-23 - 3.20.1, 3.18.8, 3.16.12 Let's say you had 3.6.x in 2013. Less than a year, you would be upgrading to 3.6.12 and a few month later be forced to jump to 3.8.x Let's say you had 3.8.x in 2013. Less than a year, you would be upgrading to 3.8.16, and 3.8.23 less than a year after that. Anything less than 3.16.x in 2014 should have jumped to 3.16.5 less than a two year cycle from 3.6.12. There are 4 distinct security releases in the last 2 years. I'm sorry, but a 2 year production cycle is not realistic in terms of security. And if you argue they were as recent in previous year, I would argue that the quality level of Koha has been improving over time. Consider that debian packages in production were only as of 3.4! Have you seen the massive interface improvements since 3.6.x?! The underlying libraries and technologies have been improved as well. All these sorts of improvements include an increased testing and awareness of security issues. and only follow the minor/major releases on a sandbox to keep up with enhancements for the next production upgrade. The principle of if it ain't broke, don't fix it. -- security issues are by definition broken. So while I agree with the principle, the problem is reality is rather cruel and things break more frequently than we would like. 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] Swapping Addresses
Greetings, Via Vitae Solutions wrote: The simplest way to swap the field name as per your demand. But you can also run a script at MySql to swape the same. Indranil's suggestion of adding ARRIVE and LEAVE date patron attributes for the members in question, and then writing a script to swap them from a cronjob (e.g. the koha-common in cron.daily) is better than a one off solution. +1 for Indranil Das Gupta. :) 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] Diacritics displaying (or not) in Koha
Greetings, Jesse Lambertson asked: My next question has to do with indexing and choosing the ICU option to search in Arabic. Don't know how current this is but: http://wiki.koha-community.org/wiki/Correcting_Search_of_Arabic_records 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] Koha installation on Debian 6.5
Greetings, The latest version of Koha (3.20.x) does not install on Debian 6. Consider that Debian 8 is already out. If you are creating a new server for Koha, using the latest stable version of Debian is always recommended. If you are attempting to reuse an existing server, the question is: why haven't you upgraded it already? 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] Advice on barcode replacement/central catalog
Greetings, If you are merely importing MARC records, then why not batch update them in MARC Edit first, before importing into Koha? http://bywatersolutions.com/2012/01/18/using-marcedit-to-add-koha-items/ I'm not sure what functionality in MARC Edit would pre-append something to the barcode like SITEA, SITEB, SITEC, etc., but I'm pretty sure that functionality exists. 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] ًQuestions about 952 Field
Greetings, Useful links: http://wiki.koha-community.org/wiki/Holdings_data_fields_%289xx%29 http://bywatersolutions.com/2014/10/17/preparing-records-koha-import/ http://bywatersolutions.com/2012/01/18/using-marcedit-to-add-koha-items/ http://bywatersolutions.com/2012/02/29/altering-marc-records-in-marcedit-before-importing-in-to-koha/ 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] Problem uploading patrons
Greetings, I'm curious if this is a windows/linux CR/LF issue? Are the files the identical size? If not, then this might be a possibility. GPML, Mark Tompsett -Original Message- From: Elaine Bradtke Sent: Thursday, May 28, 2015 6:58 PM To: Robin Sheat Cc: koha Subject: Re: [Koha] Problem uploading patrons We get an export from our membership database, run it through some batch edits in another piece of software that spits out a .CSV file with the proper headers. The .CSV file she sent me is the one she tried to use. It works fine for me, and another colleague, and for me using her login (just to make sure it isn't her account). I'm thinking it may be something local to her computer. The file, and the permissions on her account seem to be just fine. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] [Koha-devel] Install Koha 3.20 with Single Command at Ubuntu 14.04LTS
Greetings, It is always better to follow the instructions on the wiki, as they are always more current (patches take longer to get into master). For example, in your script you have the old MySQL security tweak, but it is commented out. The new tweak: sudo mysql_secure_installation I do not recommend using a single step install script. This makes it more difficult to help you fix your problems when something goes wrong. Primary reference: http://wiki.koha-community.org/wiki/Koha_on_Debian Secondary reference (in the case of Ubuntu): http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages 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] Installed new server can no longer access KOHA.
Greetings, This is why I much prefer looking at the Wiki, because the warning is more ominous and fear inducing. Disable Default Site If you are running Drupal or any other web service on the same machine, do not disable the default site! If you are unsure, do not disable the default site! When in doubt, always talk with your system administrator, network administrator, or IT Department. The following is intentionally not boxed to prevent problems arising from improperly disabling the default site. If and only if Koha is the only thing on this server, then feel free to run this to disable the default site: sudo a2dissite 000-default Additionally, given people's laziness leading to just cut and past the boxes in, this command is generally overlooked. This is written for the librarian with no linux experience trying an Ubuntu install. The problem is the Ubuntu pages give a little more detail than the Debian in terms of intermediate steps, but approach it from the Oh shoot, this person knows nothing about networking or apache configuration. The Debian pages assume a higher level of networking and apache configuration understanding than that, last I checked. As for the INSTALL file, that update was way better than the previous version. :P GPML, Mark Tompsett -Original Message- From: MJ Ray Sent: Wednesday, May 20, 2015 7:11 AM To: koha@lists.katipo.co.nz Subject: Re: [Koha] Installed new server can no longer access KOHA. Boulier, Jack wrote: I have installed a new server with Ubuntu 14.04. Though I did the install of KOHA correctly. But now when I internet to the server I get the apache page and not the KOHA pages. Do need so help, but do not even know what to begin to ask the right questions. There is probably some other apache site configured with a higher priority than Koha. This is a choice you or Ubuntu made with your Apache configuration. It is not really a Koha problem, but http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=INSTALL.ubuntu;hb=HEAD#l415 says 415 Disable Default Site 416 = 417 418 These short instructions assume that the default site is 419 not needed. Talk with your system administrator, network 420 administrator, or IT Department to CONFIRM THIS BEFORE RUNNING 421 the following command: 422 sudo a2dissite 000-default Hope that informs, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op http://koha-community.org supporter, web and library systems developer. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire (including development) at http://www.software.coop/ ___ 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
Re: [Koha] Records Exported 0
Greetings, Is koha really your instance name? Perhaps you created another in your confusion? GPML, Mark Tompsett -Original Message- From: obaiah Sent: Wednesday, May 20, 2015 2:14 AM To: koha@lists.katipo.co.nz Subject: [Koha] Records Exported 0 Dear Friends, I am trying to import koha 3.14 database in to koha 3.18.06. When i run mysql dump command I got the following message. /home/library/koha_koha.sql Enter password: -- MySQL dump 10.13 Distrib 5.5.43, for debian-linux-gnu (x86_64) -- Host: localhostDatabase: koha_koha -- Server version 5.5.43-0ubuntu0.14.04.1 /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8 */; /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; /*!40103 SET TIME_ZONE='+00:00' */; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; /*!40103 SET TIME_ZONE=@OLD_TIME_ZONE */; /*!40101 SET SQL_MODE=@OLD_SQL_MODE */; /*!40014 SET FOREIGN_KEY_CHECKS=@OLD_FOREIGN_KEY_CHECKS */; /*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */; /*!40101 SET CHARACTER_SET_CLIENT=@OLD_CHARACTER_SET_CLIENT */; /*!40101 SET CHARACTER_SET_RESULTS=@OLD_CHARACTER_SET_RESULTS */; /*!40101 SET COLLATION_CONNECTION=@OLD_COLLATION_CONNECTION */; /*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */; -- Dump completed on 2015-05-20 0:59:43 But when I run the zebra index command it shows that it has exported 0 records. sudo koha-rebuild-zebra -v -f koha Zebra configuration information Zebra biblio directory = /var/lib/koha/koha/biblios Zebra authorities directory = /var/lib/koha/koha/authorities Koha directory = /usr/share/koha/intranet/cgi-bin Lockfile= /var/lock/koha/koha/rebuild/rebuild..LCK BIBLIONUMBER in : 999$c BIBLIOITEMNUMBER in : 999$d skipping authorities exporting biblio Records exported: 0 REINDEXING zebra CLEANING Zebra configuration information Zebra biblio directory = /var/lib/koha/koha/biblios Zebra authorities directory = /var/lib/koha/koha/authorities Koha directory = /usr/share/koha/intranet/cgi-bin Lockfile= /var/lock/koha/koha/rebuild/rebuild..LCK BIBLIONUMBER in : 999$c BIBLIOITEMNUMBER in : 999$d exporting authority Records exported: 0 REINDEXING zebra skipping biblios CLEANING Can somebody plz suggest me that how can I solve this problem..? Regards Obaiah B. Ashoka Trust for Research in Ecology and the Environment, Royal Enclave, Srirampura, Jakkur Post, Bangalore-560064 -- View this message in context: http://koha.1045719.n5.nabble.com/Records-Exported-0-tp5840766.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 mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] E: Sub-process /usr/bin/dpkg returned an error code (1)
Greetings, Vimal Kumar V. writes: May I know the reason behind the error? [SNIP] unable to locate Koha configuration file koha-conf.xml at /usr/share/koha/lib/C4/Context.pm line 373. unable to locate Koha configuration file koha-conf.xml at /usr/share/koha/lib/C4/Context.pm line 373. unable to locate Koha configuration file koha-conf.xml at /usr/share/koha/lib/C4/Context.pm line 373. [SNIP] Do you have $KOHA_CONF set to a non-existent or unreadable location before installing? Because that screams unset or poorly set $KOHA_CONF to me. Just thinking out loud. I don't know anything. Please don’t ask me anything further. :) 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] Installation problem
Greetings, romesh chander wrote: I am trying to install Koha on Ubuntu. While running following command sudo koha-create --create-db library I am encountering following: sudo: koha-create: command not found It only works if you are installing from packages, which is recommended. http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages Did you forget to sudo apt-get install koha-common? :) 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] Koha 3.18 on Debian 8 Jessie
Greetings, Before following any of the steps, I usually type 'sudo ls'. Why? So that the password prompting doesn't get confusing on the wget command mess. $ sudo ls ... $ wget -O- http://debian.koha-community.org/koha/gpg.asc | sudo apt-key add - ... Much smoother. 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] Running koha on Debian Jessie.
Greetings, I got my git dev install running on Debian Jessie. Is anyone aware of outstanding issues running this configuration? I encountered a 403 error trying to get past the web install step, but this helped: http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages#Gitified_install_returns_403_errors I also encountered zebra indexing issues, which Robin helped me by reminding me of: http://wiki.koha-community.org/wiki/Troubleshooting_Zebra#No_such_record_type Tweaking the two dom config files and a full reindex later, I'm rather happy. 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] Tomas Needs A Laptop!
Greetings, I too was unfamiliar with it until recently. However, since I know that Ruth Bavousett, a former Translation Manager here in Koha (as well as other things I'm sure) did successfully raise the funds with it for a campaign of hers, I do not see a problem dealing with it. GPML, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Tomas Needs A Laptop!
Greetings, +1 Helping Tomas get a laptop. Thanks, Kyle. GPML, Mark Tompsett -Original Message- From: Kyle Hall Sent: Wednesday, April 08, 2015 3:49 PM To: Koha ; Koha Devel Subject: [Koha] Tomas Needs A Laptop! As you all may know, our beloved Koha Release Manager unfortunately discovered that while he and his family were away, his home was broken into and his electronics were stolen, including his laptops. Let's see what we can do to help him replace his stolen electronics! Let's show everyone what the Koha community is all about! Thanks to everyone who's donated so far! Every bit counts! This is why I love being part of the Koha community so much! http://www.gofundme.com/TomasNeedsALaptop http://www.kylehall.info ByWater Solutions ( http://bywatersolutions.com ) Meadville Public Library ( http://www.meadvillelibrary.org ) Crawford County Federated Library System ( http://www.ccfls.org ) ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] koha-common | mpm-itk on wheezy
Greetings, Did you check for libapache2-mpm-itk? $ sudo apt-get install libapache2-mpm-itk $ sudo a2enmod mpm_itk GPML, Mark Tompsett -Original Message- From: mourik jan heupink Sent: Wednesday, April 01, 2015 7:43 AM To: koha@lists.katipo.co.nz Subject: [Koha] koha-common | mpm-itk on wheezy Hi, Trying to create a new site on wheezy, koha-common 3.18.05.1: root@data:~# koha-create --create-db --marcflavor unimarc --zebralang en test I get: Koha requires mpm_itk to be enabled within Apache in order to run. Typically this can be enabled with: sudo a2enmod mpm_itk root@data:~# a2enmod mpm_itk ERROR: Module mpm_itk does not exist! root@data:~# apt-get install apache2-mpm-itk Reading package lists... Done Building dependency tree Reading state information... Done apache2-mpm-itk is already the newest version. So, it seems I have apache2-mpm-itk installed, however nothing *itk* is present under /etc/apache2/mods-available, and I cannot enable it. Any ideas? ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] apache restart error
Greetings, apache2: Syntax error on line 268 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/sites-enabled/library: No such file or directory First, you did not provide a snippet of apache2.conf which includes line 268, so it is not possible to know for sure. Though, I might guess that you have a 'library.conf' file in sites-enabled, and that line 268 needs to be edited to match. Though, why did you even touch apache2.conf? I don't recally any instructions suggesting that. Of course, it's 1:30AM here, and I should be going to bed. GPML, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
[Koha] Fw: Please add us as new Paid Support for Asia - Philippines
Greetings, I notice Mirko's entry was added nearly immediately. Please add the following. I am included in the us, though as a silent technical partner. GPML, Mark Tompsett -Original Message- From: Manuel Tamayao Sent: Wednesday, February 04, 2015 12:18 AM To: koha@lists.katipo.co.nz Subject: [Koha] Please add us as new Paid Support for Asia - Philippines Good day Koha Community, Please add us as a new paid support for Philippines Company Name: Tulong Aklatan Contact Person: Manuel Tamayao Contact email: tulongakla...@gmail.com Home: Pinagkaisahan, Makati City, Philippines Website: www.tulongaklatan.ph Short description of your services: We offer training, installation, support, migration, and hosting solutions for Koha. Salamat po, Manny Tamayao ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] database error
Greetings, etaisil ineseliam schreef op do 12-03-2015 om 18:08 [+1300]: Ive done the DNS one but I also disabled default site. but now i got the system is down for maintenance page Robin Sheat wrote: However, you should be able to sudo koha-enable library -- library.conf (arg to annoying Apache 2.2 vs 2.4 things) ... I thought it was enabled by default but I could be wrong, I should check that and update the docs accordingly. It may be their first time installing and the DB may not be populated. If I'm wrong, I blame just waking up. :) GPML, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Support status on CentOS or RedHat
Greetings, The largest problem with running under a non-Debian-based distribution of Linux, such as RedHat variants, is support. The first headache you will encounter is installing the required libraries. Last I checked, it was around 18 or so of them require installation magic beyond a default installation on CentOS and/or Fedora. The second headache you will encounter is when you hit a problem, you may discover it is because of your non-Debian OS, because they did it differently that what the coders of Koha encountered using Debian-based OSes. Additionally, you may find only a few of people who use RedHat to run it, and they may or may not respond in a timely fashion to your problems. Debian, in particular, and Debian-based variations (Ubuntu is another popular one) are your best bet for finding support, and having a less painful installation. So is RedHat discouraged? Yes, why would we encourage headaches which we generally don't have the time to solve, because we mostly use Debian-based OSes? However, we believe in freedom, and if you wish to take on the mantle of pain, feel free. More power to you. :) For a more painful experience port it to run natively in Windows. ;) GPML, Mark Tompsett P.S. I did actually attempt the Windows, but gave up because the pain was worse than CentOS and Fedora. I only attempted them to see if it could be done, and yes, I was successful eventually. I don't recommend trying, unless you are seasoned Linux administrator. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Intro, and req for help :)
Greetings, http://marcedit.reeset.net/ MarcEdit is a Windows utility that can help you easily convert. It also can help you pre-validate the data and make sure it is good before importing. http://bywatersolutions.com/2012/02/29/altering-marc-records-in-marcedit-before-importing-in-to-koha/ I'm sure there are other great videos on the bywatersolutions website that might be helpful too. Also, you might want to make sure the data has the appropriate holdings fields too. :) http://wiki.koha-community.org/wiki/Holdings_data_fields_%289xx%29 Plus if you want to write your own. Coding is a fun challenge, right? :) http://search.cpan.org/~gmcharlt/MARC-XML-1.0.3/lib/MARC/File/XML.pm http://search.cpan.org/~gmcharlt/MARC-Record-2.0.6/lib/MARC/Record.pm GPML, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha ILS Driver for Vufind
Greetings,
The Koha did not write the driver. This is a VuFind issue.
I took a quick look by:
$ git clone https://github.com/vufind-org/vufind.git
$ vi ~/vufind/module/VuFind/src/VuFind/ILS/Driver/Koha.php
-- And around line 484:
// Koha uses MD5_BASE64 encoding to save borrowers' passwords, function
// 'rtrim' is used to discard trailing '=' signs, suitable for pushing
// into MySQL database
$db_pwd = rtrim(base64_encode(pack('H*', md5($password))), '=');
Correct that code on the VuFind repository and happiness should be restored.
Sorry, but how to correct these lines is left as an exercise for someone who
knows:
- how to provide patches to VuFind
- Koha, and
- PHP.
Sorry, but I don't know the first.
In summary, this is a VuFind issue, not a Koha issue.
GPML,
Mark Tompsett
P.S. I have an untested attempt at a re-write of the problematic function.
___
Koha mailing list http://koha-community.org
Koha@lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Error message at login: 'You do not have permission to access this page'
Greetings, There is no link (currently) between a patron category and patron permissions. 1) Login to staff client 2) Click Patrons 3) Click the letter of the person's last name (e.g. Frank Peters would be listed under 'P') 3a) if a list is given, click the name of the person, not Edit. 4) Click 'More' -- You should notice a 'Set Permissions' entry. 5) Click 'Set Permissions' Fix the permissions, save, and be glad you don't have to do that all the time. :) GPML, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Data Migration from Alice for Windows to Koha
Greetings, I don't know, but here is my guess. Those two file formats (.dat or .rtf) probably could be renamed as .mrc or .mrk. If you open those files in wordpad and see something like: --- BEGIN SNIPPET --- =020 \\$a971-508-125-8 =100 1\$aVirgilio S. Almario$eauthor =245 10$aIbong Adarna =260 \\$c1980 =300 \\$a32 =386 \\$b73$cPhp =500 \\$aThree princes went on a journey to catch the elusive and enchanting Adarna bird, to cure the sickness of their father, the King. One of the best known Filipino folk stories, Ibong Adarna is filled with adventure and magic. =500 \\$aTatlong prinsipe ang naglakbay upang hulihin ang mailap at kabigha-bighaning ibong Adarna, upang malunasan ang karamdaman ng kanilang amang hari. Isa sa mga kilalang kuwentong-bayan sa Filipino, ang kuwento ng Ibong Adarna ay puno ng abentura at mahika. =521 0\$a9+ =546 \\$aFilipino (Tagalog) with English translation =700 1\$aJordan Santos$eillustrator --- END SNIPPET --- Then it is a .mrk file If you open those files in wordpad and see something like: --- BEGIN SNIPPET --- 00582nam 2200157 a 45100070005001770080041000240940015[CUT OFF INTENTIONALLY] --- END SNIPPET --- This it is a .mrc file You could then use MarcEdit (http://marcedit.reeset.net/downloads) to clean up your data and make sure you have a .mrc file. You will need =952 fields to import nicely into Koha. I think http://bywatersolutions.com/2014/10/17/preparing-records-koha-import/ does a great job of describing some steps you likely need to do. Hope this helps. GPML, Mark Tompsett (http://www.tulongaklatan.ph) ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] es.koha-community.org Down
Greetings, http://www.downforeveryoneorjustme.com/es.koha-community.org It is down. GPML, Mark Tompsett -Original Message- From: Anthony Mao Sent: Friday, January 30, 2015 8:41 PM To: koha Subject: [Koha] es.koha-community.org Down Hi, Can some one confirm the availability of es.koha-community.org? I can not access it to download manual in pdf. -- 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 http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Cannot log in
Greetings, Julie Anderson wrote: Hello, since the first of the year we have not been able to login to our account. It is an old version of Koha. It says invalid login but I am certain we are entering our existing login. Please help. I cannot find any other way to contact Koha. Thank you. 1) How was Koha installed? 2) How are you trying to log in? 3) Did you do some sort of upgrade recently? Jump from something less than 3.12 to something after 3.12? -- I'm thinking password field size wrong and upgraded with bug 9611 included, but I'm not sure. 4) Is your caps lock on? 5) Is your keyboard starting to have keys fail? -- Two common problems I encountered recently. :) 6) How is your Koha configured to log in? directly? ldap? sip? something else? If you wish to ask questions, check out the mailing list, which I have CC'd. http://koha-community.org/support/koha-mailing-lists/ GPML, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Label creator error
Greetings, Is your problem similar to what is described in http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13263 GPML, Mark Tompsett -Original Message- From: cjwalke Sent: Monday, December 22, 2014 2:45 PM To: koha@lists.katipo.co.nz Subject: [Koha] Label creator error I'm running 3.18 and have a problem with my label creator incorrectly splitting call numbers. I'm using the Reference collection code and adding REF to the head of each call number for the items. Call numbers are populated by the data in the 050 field. Not all the call numbers on the label, but most, come out similar to this: REF .H D1401 M2 2002 I am not sure what is going on. Thanks. -- View this message in context: http://koha.1045719.n5.nabble.com/Label-creator-error-tp5823113.html Sent from the Koha-general mailing list archive at Nabble.com. ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha 3.18 - Label Creator - Call number volume statement displaying as 0?
Greetings, When you said enumchron, that got me thinking back to a bug I was dealing with. Long and short is, I found that template that came to mind and read: [% IF item.enumchron item.serialseq %] span class=enum[% item.enumchron %]/span [% IF ( item.serialseq item.enumchron!=item.serialseq ) %] span class=sep -- /span span class=serialseq[% item.serialseq %]/span [% END %] [% ELSIF item.enumchron %] span class=enum[% item.enumchron %]/span [% ELSIF item.serialseq %] span class=serialseq[% item.serialseq %]/span [% END %] [% IF ( item.publisheddate ) %] span class=pubdate([% item.publisheddate %])/span [% END %] You will see that serialseq is displayed just like enumchron in the two ELSIF's. Perhaps you might try serialseq instead? GPML, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Koha 3.18 - CSS information
Greetings, Relatively new to CSS customization and am learning the backend of Koha (latest version installed) on my own. Congratulations! :) Where would I look for the template information for Koha's bootstrap theme? I would like to use and apply the CSS information already contained in 3.18 to new code that requires CSS styling (e.g., a CSS left-hand menu in opacnavleft for hyperlinks. I'd like to keep font styles, headings, font weights, etc. as uniform as possible throughout the catalogue while coding. If you are attempting to customize Koha's appearance with CSS, you can create your own CSS file and set the appropriate system preference. Check out opaccolorstylesheet, opaclayoutstylesheet, and OPACUserCSS system preferences. If you are actually just trying to grab bits and pieces, the inspect element should suffice. Though, you can likely find the file in a directory somewhere similar to: /usr/share/koha/opac/htdocs/opac-tmpl/bootstrap/css GPML, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
Re: [Koha] Cloud-based Koha vs locally hosted Koha
Greetings, On 10 December 2014 7:06:37 am NZDT, BWS Johnson abesottedphoe...@yahoo.com wrote: [SNIP] The only difference I can spot might actually weigh as a positive in favour of cloud based service. When you have a physical server and suffer a local catastrophe, such as an earthquake, fire, sinkhole, et cetera, there goes your data. Actually another cost consideration is the hardware costs vs. hosting costs. Hardware dies over time and needs to be replaced. Budgets get cut, and a monthly hosting cost is less likely to be axed compared to a new server cost ever 4-5 years. So, in some sense, I think hosting externally and not on your own local hardware is better. And comparing costs, you may be able to find hosting that works well for a cost that when amortized over 4-5 years is actually cheaper. That is, $20/month (let's say) * 12 months * 4 years = $960 for 4 years. This is comparable to some cheaper machines which perfectly suffice, but I know I prefer to drool over the $2500+ machines. :) Sadly, you aren't likely to be continually upgrading components. After 4 years, a locally owned piece of hardware will have dropped from a middle class machine to low end machine, while the hosted environment may have progressed, because of hosting provider upgrades. :) And, you aren't having to do your own backups, if you hosting on the cloud. If you have locally hosted machine, you need to figure out how to back up elsewhere. A good backup plan has on-site same drive, on-site different drive, and off-site backups. A hosting provider tends to have these in place. Do you want the hassle of having that yourself? This is related to the point that BWS Johnson made. And what if your local machine dies? Sure you have a backup, but you actually have to spend the day rushing around buying a new server. With hosting, hardware failures like that are not your worry. No budget stresses, because you don't have the cash to go buy it now, and most service level agreements give you less than a hour downtime per year. GPML, Mark Tompsett ___ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
