- Koha - lists.katipo.co.nz

Is this an error about Koha?
by Luis Moises Rojas 02 Aug '17

02 Aug '17

Hello everybody, Our server only have Koha, this critical error: The "HTTP: Apache Struts 2 Remote Code Execution (CVE-2017-5638)" . I said this, because struts (as you know) is for MVC programing structure. Thanks. -- *Luis Moisés Rojas P.*

2 1

Impossible to renew items
by mpw 02 Aug '17

02 Aug '17

I'm running Koha version 17.05.01 on Debian 8.8. I'm setting up a new library. I have checked out eight books. In the renewable column they are all listed as "Not renewable (0 of 0 renewals remaining)". Several people have suggested removing all the circulation and fine rules and creating a single rule the holds for all patron types and all item types. For example here: http://koha.1045719.n5.nabble.com/All-items-quot-not-renewable-quot-td59254… I've tried that several times but none of the tries ever made any difference. Right now I only have one rule: Patron category - All Item type - All Current checkouts allowed - 20 Renewals allowed - 3 Renewal period - 14 Automatic renewal - no Since somebody in the above mentioned thread said that this might be a bug, I opened a bug report but they referred me back to this list because it's supposedly just a configuration problem. I have set the option that enables the "Override renewal limit" checkbox so I can trick the system into renewing books, but that's just a workaround and I'd like to get to the root of the problem. I've been going around in circles here for well over a week. Can anybody point me in the right direction? -- View this message in context: http://koha.1045719.n5.nabble.com/Impossible-to-renew-items-tp5941578.html Sent from the Koha-general mailing list archive at Nabble.com.

3 5

Searching capability dies every few days - Zebra problem?
by mpw 02 Aug '17

02 Aug '17

I'm running Koha version 17.05.01 on Debian 8.8. I set up Koha a few months ago and we're still learning the system. One thing we've noticed that presumably is not normal is that every few days the searching capability dies for some reason or other. My guess is that it has something to do with Zebra. I occasionally get a message from my logrotate cronjob: Zebra already stopped for instance xxx. When I check, there are no koha or zebra processes running. I can restore the search capability by restarting Koha with "invoke-rc.d koha-common restart". Presumably some daemon or other dies but I haven't been able to figure out which one. Maybe it happens during the regular cronjobs? Does anybody have any idea how I can figure out what's happening? One workaround I'm considering is setting up a regular cronjob to restart koha-common regularly, but that doesn't strike me as being a very elegant solution. -- View this message in context: http://koha.1045719.n5.nabble.com/Searching-capability-dies-every-few-days-… Sent from the Koha-general mailing list archive at Nabble.com.

3 3

Results of the poll "Ready to help the Koha community?"
by Jonathan Druart 02 Aug '17

02 Aug '17

Hello everybody, I have published the results of the poll, launched at the beginning of the 17.11 development release cycle. https://koha-community.org/answers-of-the-poll-ready-to-help-the-koha-commu… There are the results, and a list of remarks and notes that people did. I tried to give them answers. I let you comment, if you have something to add. Regards, Jonathan

2 1

After Upgrade no biblio_metadata and mo marcxml
by gevos 01 Aug '17

01 Aug '17

Overyesterday We have updated ubuntu server and the koha was updated too. Apparently because of the mysql 5.7 the script somehow failed and we have landed to a point where only from 30.000 books only 2 books landed to the book_metadata. and we don't have now the original column marcxml in biblioitems :((((((((((((((((( -- View this message in context: http://koha.1045719.n5.nabble.com/After-Upgrade-no-biblio-metadata-and-mo-m… Sent from the Koha-general mailing list archive at Nabble.com.

5 4

checkin problem
by Sahadeo Taware 01 Aug '17

01 Aug '17

Dear Friends When I checkin the book following error is shown Check in message The item has not been checked in due to a configuration issue in your system. You must ask an administrator to take a look at the about page <http://192.168.35.196:8080/cgi-bin/koha/about.pl#sysinfo> and search for the "data problems" section -- Sahadeo D. Taware Librarian, M.L.I.Sc., NET Thakur College of Science and Commerce Thakur Village, Kandivli(E), Mumbai 400101 Mob. No 9324912816 Office 28870627 Extn. 126

3 2

Slips and Notices
by Luis Moises Rojas 01 Aug '17

01 Aug '17

Hello everybody: There is not way, even the table: LETTER have data: 1. Nothing is display on the screen. 2. I can not save a new one. Any idea? Thanks -- *Luis Moisés Rojas P.*

1 0

how to run Koha server behind a proxy server
by Fahad Ubaid 01 Aug '17

01 Aug '17

Hi Guys, Can someone help me about how to run Koha server behind a proxy server? and also guide how to change database connection by changing the IP address of the database ... waiting for your positive response from Koha community. Best Regards Fahad Ubaid Resident Engineer Interactive Group of Companies, Islamabad Pakistan Cell # *923445505422*

1 0

Unable to place hold on any item
by ILOBWeb 01 Aug '17

01 Aug '17

Hello, I have successfully imported records in my library but when any patron try to place hold on an item, its giving error : 'Sorry, none of these items can be placed on hold.' Can someone guide which configurations I need to do? Regards, Gurpreet

3 3

Koha Check- Error -The item has not been checked in due to a configuration issue in your system.
by Admire Mutsikiwa 01 Aug '17

01 Aug '17

Hi I have upgraded my Koha to version . Now when I check in an item I am getting the following error: The item has not been checked in due to a configuration issue in your system. You must ask an administrator to take a look at the about page <http://uzlibraries.uz.ac.zw:8080/cgi-bin/koha/about.pl#sysinfo> and search for the "data problems" section. When I visit the About page, I am greeted with : Data problems Some of your tables have problems with their auto_increment values which may lead to data loss. You should not ignore this warning. The problem is that InnoDB does not keep auto_increment across SQL server restarts (it is only set in memory). So on server startup the auto_increment values are set to max(table.id)+1. See the related wiki page <https://wiki.koha-community.org/wiki/DBMS_auto_increment_fix> to know how to avoid this problem. Problems found Checkouts The following ids exist in both issues and old_issues tables: 2, 3 Warnings regarding the system configuration However, when I check the schema for old_issues, it has no auto-increment turn on for issue_id though it is the primary key I will appreciate any pointers Kind Regards, Admire Mutsikiwa (Mr) ICT Manager Libraries University of Zimbabwe Tel:+263-4-303276 Mob:+263771117777 "It is easy to dodge our responsibilities, but we cannot dodge the consequences of dodging our responsibilities." Josiah Charles Stamp <http://www.goodreads.com/author/show/4867406.Josiah_Charles_Stamp>

2 1