- Koha - lists.katipo.co.nz

Re: [Koha] What's up with That?
by David Nind 21 Dec '13

21 Dec '13

Hi Phillip. I think I will leave it up to the more experienced people who install on Ubuntu to comment on the ins and outs of Apache configuration for Koha on Ubuntu, as this is where I think the issue is. Here is a link to the instructions: > http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages > The message that I'm getting is just that the apache web server is > active. This takes place anytime I use the browser with: http://ipaddress: > 80. I'll have to wait until I go back into work to find get the original > message. > > Thing in your email that may fix the problem: > > I did not disable the default web browser site. > The server is not listening on port 8080 only on port 80. > I would tend to go with the koha-community wiki instructions. Note: I think they need to be updated to clarify the port numbers and Apache configuration. On a default installation the public catalogue runs on port 80 and the administration interface (also called the staff client) runs on port 8080. I will work on updating the wiki when I get a chance, unless someone else beats me to it. > Other instructions indicate that I should delete the default web site > also. > One set of intructions says I should delete the koha website and then > start a new one under the name of my instance as shown below. ( > http://wiki.lib.sun.ac.za/index.php/Koha/Installation) > I think the difference with these instructions is in step 4 where it says 'sudo apt-get install koha koha-common bibutils etckeeper' - normally you only go 'sudo apt-get install koha-common' rather than 'sudo apt-get install koha koha-common'. I think you are only supposed to do one or the other, not both. If you are only running Koha on the server then you do need to disable the default site. If you are running other sites on the same server then the assumption is you will know what you are doing and know how to configure Apache correctly. With a default Koha installation (on Debian anyway) an Apache configuration file is only created when you create an instance. This configuration file needs to be updated with the correct port numbers/server names. Then the ports.conf file needs to be updated with the correct port numbers for Apache to listen on. If you are installing Koha on a networked server and have a server name assigned to the server IP address then the server, Apache and the Koha Apache configuration file needs to be configured appropriately for this. I'm sure someone will correct me if I'm wrong about any of this. > I'm going back in to try this again tonight. > > Hope the port issue solves the problem.... Note: with the mailing list you need to reply all for any responses to be sent to the list, forgot to do this for my initial response! Regards.

1 0

Re: [Koha] What's up with That? (installing on Ubuntu)
by David Nind 21 Dec '13

21 Dec '13

Note: copy to list as I forgot to 'reply all'. Hi Phillip. I installed Ubuntu 12.04 and then following the instructions on the Koha > website, I installed Koha not once but three times while trying to get it > to work. > Could you provide a link to the instructions you used? Did you install using the packages? (The recommended way for most standard installations)? > On the third time I installed Lynx and tried to connect to Koha directly > on the box but all I could get was what looked like an apache web page as > the webbrowser said: "Its working but there's no data when I tried to > connect using the localhost and then the server IP Address. > What is the exact message you are getting? If you have used the packages for installation you need to disable the default Apache configuration, make sure your site configuration is enabled, and enable listening on port 8080. On Debian (not sure for Ubuntu, but I think it is similar and assuming you have sudo installed rather than using root) it is: sudo a2dissite default sudo vi (or nano) /etc/apache2/ports.conf and add Listen 8080 after the Listen 80 entry make sure your site configuration is enabled under /etc/apache2/sites-enabled (sudo a2ensite nameofyoursiteconfig) sudo /etc/init.d/apache2 restart David Nind | david.nind(a)gmail.com PO Box 12367, Thorndon, Wellington, New Zealand 6144 h. +64 4 9720 600 | m. +64 21 0537 847 | w. +64 4 8906 098

1 0

problem with bulk imported data
by Babu_koha 21 Dec '13

21 Dec '13

Hi, in bulk import of data, i have used the tags *942$c and 952$y* for Item Type, but they not displayed in staff client and opac search. in edit items screen, selected the *Item Type* as *Books* from the drop down list and saved. then the values automatically displayed in staff client and opac search. please see the screen shots. any help............ <http://koha.1045719.n5.nabble.com/file/n5781747/1staff_client.jpg> <http://koha.1045719.n5.nabble.com/file/n5781747/2opac.jpg> <http://koha.1045719.n5.nabble.com/file/n5781747/3edit.jpg> <http://koha.1045719.n5.nabble.com/file/n5781747/4edit.jpg> <http://koha.1045719.n5.nabble.com/file/n5781747/5opac.jpg> <http://koha.1045719.n5.nabble.com/file/n5781747/6staff.jpg> -- View this message in context: http://koha.1045719.n5.nabble.com/problem-with-bulk-imported-data-tp5781747… Sent from the Koha-general mailing list archive at Nabble.com.

3 4

Conference stuff
by BWS Johnson 20 Dec '13

20 Dec '13

Salvete! Funny you mention mid Spring >:) The 2014 International Evergreen Conference is 19 - 22 March in Bean Town. They sent us bshum and gmcharlt, so we should crash their party at some point. Or at least not slate over it. Though coughing up $220 or $270 is less than appealing to me, BUT David Weinberger. I _am_ tempted to ninja plan summat for mid Spring of 2015. Spring is substantially more expensive here than Fall, BUT cherry blossoms. 2015 is also more attractive to me as a host, since it's NOT any ilk of major elections year. August is unappealing to me, since it's silly season for me AND hotter than heck for most attendees. This is why I don't want to bid on next year's North American Conference, since a decision has already been taken to have Conference then. July and September work much better for me. So basically, let's play a game. I'm throwing a Conference at some point, and glaws is prolly coming. If I can add two more out of town names* to that list, then I'll definitely do eet. So if you're interested, write me off list or just say "I'll prolly go" on list. The workflow I'm using is this: 1. Gauge interest 2. Toss out dates that work for me, don't conflict with KohaCon, ALA, or Evergreen, and then see if they work for y'all too 3. Secure a venue 4. Wrangle some speakers Cheers, Brooke (*I consider you an out of towner if you're not from Southern Maryland, Da Fancy Pants District of Columbia, or the Great Commonwealth of Northern Fake Virginia. If you're an in towner, you've prolly already met me. But if you haven't, let's have coffee or lunch or whatevahs.) >________________________________ > From: glaws <glawson(a)rhcl.org> >To: BWS Johnson <abesottedphoenix(a)yahoo.com> >Cc: Galen Charlton <gmc(a)esilibrary.com>; Scott Kushner <skushner(a)mplmain.mtpl.org>; kohana(a)lists.bywatersolutions.com >Sent: Wednesday, December 18, 2013 11:45 AM >Subject: Re: [Koha] Koha Users of North America Email List > > > >1. I'll bring the coffee. > >2. Mid spring and through the summer are good event times for me. Things start getting busy in early fall. > >3. Two day conferences are better than just one. Amortizing fixed costs like airfare over two days is a better investment than just one day. > >Greg Lawson >Network Administrator >Rolling Hills Consolidated Library >1912 N. Belt Highway >St. Joseph, MO 64506 >816-232-5479 x2303 >----------------------------------------------------------------- > > > > > >On 12/18/2013 10:16 AM, BWS Johnson wrote: > >Salvete! >>One thing to consider is that it doesn't have to take much to host a one-day or even half-day local Koha event. If you're located in an area where there's at least one other Koha library within reasonable driving distance, all you really need to host an unconference [1] is time, a meeting room, and the desire to promote the event. Everything else, including internet access and even coffee and snacks, is optional. This can scale up. There are certainly larger geographic areas in North America where there's a high enough concentration of Koha users to support a regional event. And if somebody wants to run such an event... go for it: speak up, say what you want to do, and gather some like-minded people to help. [1] http://en.wikipedia.org/wiki/Unconference >> Once again, my arm can be twisted to host at whatever level. Doesn't even require that much twisting, I just don't want to throw a party and have no one show. :) All I ask is that y'all let me pick dates, or let me in on the voting so that I can express whether they are inconvenient to me or no. #justsayin Cheers, Brooke _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha > > >-- > >

5 5

What's up with That?
by Phillip Ponchot 20 Dec '13

20 Dec '13

I installed Ubuntu 12.04 and then following the instructions on the Koha website, I installed Koha not once but three times while trying to get it to work. On the third time I installed Lynx and tried to connect to Koha directly on the box but all I could get was what looked like an apache web page as the webbrowser said: "Its working but there's no data when I tried to connect using the localhost and then the server IP Address. The files that I had to configure look like this: koha-sites.conf: DOMAIN=".livingston.org" INTERPORT="80" INTRAPREFIX="" INTRASUFFIX="=intra" DEFAULTSQL="" OPACPORT="80" OPACPREFIX="" OPACSUFFIX="" ZEBRA_MARC_FORMAT="marc21" ZEBRA_LANGUAGE="en" I can ping the server so the network card interface is working. My Hosts File: 127.0.0.1 LocalHost 192.168.0.3 Web1.Livingston.org Web1 Listen 80 and NameVirtualHost *: 80 is in the ports.conf. My interface file and ifconfig shows that 192.168.0.3 is assigned to this server and the netmask and gateway is correct. personally, I think that although the install was good, Koha is not stating. (I did reboot the server just in case). I followed the instructions to the T! Does anyone have an ideas? I did not disable the primary web site as I didn't know if I was going to need it later, but according to one set of instructions, this is not necessary. Would it be better for me to download the Koha install tar.gz file and install from it? I tried connecting by: lynx http://192.168.0.3:80 and also tried 8080. I'm not quite sure at this point as to where I would start looking to find out why Koha is not working. Thanks, Phillip

1 0

(no subject)
by K B Madhu 20 Dec '13

20 Dec '13

Dear friends, How can we delete the no items record in catalog. With regards, Madhu KB Library BITS-Pilani, Hyderabad Campus.

1 0

Now CILEA is CINECA (new company name)
by Zeno Tajoli 20 Dec '13

20 Dec '13

Hi to all, I write thosr lines for update my company name. For now the only change that I need is to change the name 'CILEA' with CINECA. For now telephone, web site and contact don't change. Thank yoy very much. Bye Zeno Tajoli -- Dr. Zeno Tajoli Dipartimento Gestione delle Informazioni e della Conoscenza z.tajoli(a)cineca.it fax +39 02 2135520 CINECA - Sede operativa di Segrate

1 0

Koha Rebuild and Upgrade - If I only had a brain!
by Phillip Ponchot 20 Dec '13

20 Dec '13

I'm having to build a new koha server and then move koha files over to the new server (which will be an upgraded version). My situation is that Koha is tied to the web server and of course most of the data is in the Koha databases. As I understand, I have to: 1. Install Koha. 2. Upgrade Koha. 3. Dump the Koha Database. 4. Copy it to a pen drive (the old server is no longer connected to the intranet). 5. Import the Koha Database 6. It is my understanding at this point that I have to do something to get the New Koha to recognize the imported database as the format will still be in the old Koha Format. Can anyway tell me what commands and how to to this? 7. Also all the web pages are done via Koha (maybe via WordPress). Does anyone know the procedures to get this back up and working? I've got a good feeling about this but I know from technical experience with other programs that doing things in the right steps is crucial. I do read the instructions but sometimes there are little catches that are not included. Thanks for any help and thanks to everyone who replied to my previous post. Our Koha is down hard and I'm determined to get it back up and running ASAP. Phillip

3 2

bug upgrading koha 3.12.3 to 3.14?
by Hugo Agud 20 Dec '13

20 Dec '13

Hi We are upgrading koha 3.12.3 to koha 3.14, and we are facing one error that we think it could be a bug, does anybody found something similar? In the database there is not any borrower or any patronimage at koha 3.12.3, browsing bugzilla we have found bug 10636 http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10636<http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10636> it is the same error, but we can't see why it is happeing in the update process.. . One interesting issue is that the updatedatabase.pl thinks the source version is 3.13 Update report : - Status: 500 - Content-type: text/html - - <h1>Software error:</h1> - <pre>DBD::mysql::db do failed: Error on rename of './koha_etnologic/patronimage' to './koha/#sql2-8f59-18b' (errno: 152) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.plline 7243. - </pre> - <p> - For help, please send mail to the webmaster (<a href="mailto: webmaster@icub">webmaster@icub</a>), giving this error message - and the time and date of the error. - - </p> Update errors : - [Thu Dec 19 23:28:21 2013] updatedatabase.pl: DBD::mysql::db do failed: Duplicate column name 'borrowernumber' at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.plline 7224. - [Thu Dec 19 23:28:21 2013] updatedatabase.pl: DBD::mysql::db do failed: Error on rename of './koha/patronimage' to './koha/#sql2-8f59-18b' (errno: 152) at /usr/share/koha_etnologic/intranet/cgi-bin/installer/data/mysql/ updatedatabase.pl line 7243. - [Thu Dec 19 23:28:21 2013] updatedatabase.pl: DBD::mysql::db do failed: Error on rename of './koha_etnologic/patronimage' to './koha/#sql2-8f59-18b' (errno: 152) at /usr/share/koha/intranet/cgi-bin/installer/data/mysql/updatedatabase.plline 7243. thanks to all! -- *Hugo Agud - Orex Digital * *www.orex.es <http://www.orex.es>* Director Passatge de la Llançadera, 3 · 08338 Premià de Dalt - Tel: 93 539 40 70 hagud(a)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.

1 0

Re: [Koha] New Serials Documentation
by Francois Charbonnier 19 Dec '13

19 Dec '13

Hi Nicole, The locale option is useful when you want to display days, month or season. If you have a german serial, you can use the german locale option to display days, etc. in german. It doesn't work actually but this patch fixes the problem : http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11262 The inner counter doesnt tell system when the number should go back to 1. It is used when you need a "circular" pattern to tell koka how many issues you received or would have received after the beginning of the "circle". If you start receiving issues in the middle of a circular pattern, it helps the system to fall back on the correct numbering when the numbering go back to 1. (Sorry for my broken english....) Check the example in the attached file. It should helps! ;) Francois

4 8