http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13135 Bug ID: 13135 Summary: cancel_expired_holds.pl/CancelExpiredReserves() logging improvements to catch evasive bugs in production. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs@lists.koha-community.org Reporter: olli-antti.kivilahti@jns.fi QA Contact: testopia@bugs.koha-community.org CC: gmcharlt@gmail.com, kyle.m.hall@gmail.com We have issues with the Calendar giving bad expiration dates for waiting holds. So far unable to isolate the bug, which appears to appear only in prodcution. This logging improvement gives a lot more information about the cronjob internals in varying levels. (L1) Logs expired holds which have expirationdate overdue. (L1) Logs holds waiting too long, those that did get cancelled and (L2) those that didn't. (L3) Logs the used Calendar-objects content ** * * * ** * TEST PLAN * ** * * * ** 0a. Set the ReservesMaxPickUpDelay-syspref to 6 days. 0b. Create reservations, with expirydate in the past, and in the future, and now. Catch some of those to a borrower. 0c. Create reservations without an expirationdate and catch them to borrowers. In the DB, set the waitingdate 2 days to the past for some of them, 4 days to the past for a portion, 6 days to past for some and 8 days past for the rest. 1. Run the cancel_expired_holds.pl-script with --verbose 3 Observe log entries of all the handled reservations and of all the used Calendars (not all Calendars, simply those that were needed). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.