- Koha-bugs - lists.koha-community.org

[Bug 25790] New: [OMNIBUS] warnings removal
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25790 Bug ID: 25790 Summary: [OMNIBUS] warnings removal Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: trivial Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: nugged(a)gmail.com Reporter: nugged(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)bugs.koha-community.org, slavashishkin(a)gmail.com, stalkernoid(a)gmail.com Depends on: 25440, 25491, 25506, 25533, 25695 This is an omnibus report to group tickets/tasks related to cleaning up of warnings, mostly now emitted in logs in various cases after "use warnings" added and also where something suspicious going on. Let's clean up our beautiful Universe from noise and potential bugs! <3 :P Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25440 [Bug 25440] Remove undef and CGI warnings and fix template variables list in circulation rules https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25491 [Bug 25491] Perl warning at the login page of installer https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25506 [Bug 25506] Perl undef warning on the "About Koha" page https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25533 [Bug 25533] Perl "not numeric" warning on the "Holds" page https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25695 [Bug 25695] Missing logging of $@ in onboarding.pl after eval block -- You are receiving this mail because: You are watching all bug changes.

1 87

[Bug 39155] New: plack.psgi does not start if a logfile in log4perl.conf is not writable
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39155 Bug ID: 39155 Summary: plack.psgi does not start if a logfile in log4perl.conf is not writable Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org Just stumbled over this while looking at bug 39153. Your plack-error.log will have lots of: Error while loading /etc/koha/plack.psgi: Can't load application from file "/usr/share/koha/api/v1/app.pl": Can't open /var/log/koha/myclone/sip.log (Permission denied) at /usr/share/perl5/Log/Log4perl/Appender/File.pm line 151. Compilation failed in require at (eval 1988) line 1. Child process 5032 exited with status 13 What is the issue here? I created sip.log with owner root and mode 600. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 31613] New: koha-z3950-responder doesn't log (apart from YAZ logging in theory)
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31613 Bug ID: 31613 Summary: koha-z3950-responder doesn't log (apart from YAZ logging in theory) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl While we pass a log file to koha-z3950-responder, that is just used by the YAZ toolkit. That's why issues like bug 28364 can't be seen. We're not logging what happens in the actual koha-3950-responder or its child processes. Most of the time that is fine... except when you have an error. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 41527] New: Add logging for SFTP connections
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41527 Bug ID: 41527 Summary: Add logging for SFTP connections Initiative type: --- Sponsorship --- status: Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org SFTP connection opened with {Serverhost} SFTP connection failure with {Serverhost}, waiting x seconds, trying again SFTP connection disconnected with {Serverhost} -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 37220] New: Add logging for uncaught exceptions in autorenewal cron
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37220 Bug ID: 37220 Summary: Add logging for uncaught exceptions in autorenewal cron Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz It would be nice if uncaught exceptions in the autorenewal cron logged to action logs that job stopped with error instead of only showing starts and no stops.c -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 36191] New: Logs format should be consistent
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36191 Bug ID: 36191 Summary: Logs format should be consistent Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Koha logs are hard for tracking things. The main problem is they are inconsistent: api-error.log: [2022/07/06 12:01:26] indexer-error.log: 20240201 18:50:39 indexer-output.log -> NO DATE intranet-error.log.1 -> [Wed Feb 21 00:05:46.156462 2024] plack-api-error.log -> [2024/02/25 03:47:47] plack-error.log -> NO DATE plack-intranet-error.log -> [2024/02/25 15:17:15] plack.log -> 159.65.246.210 - - [25/Feb/2024:00:00:05 -0300] plack-opac-error.log -> [2024/02/25 00:12:27] sip.log -> NO DATE worker-error.log -> 20240201 18:50:29 worker-output.log -> no tiene fecha z3950-error.log -> [2024/01/23 15:21:58] z3950.log -> NO DATE zebra-error.log -> 20220222 16:10:50 zebra-output.log -> 22:15:17-18/09 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 12855] Scripts that support logging should enable logging by default
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12855 Martin Renvoize (ashimema) <martin.renvoize(a)openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |42837 Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42837 [Bug 42837] Improve and extend systems/developer facing logging in Koha -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 15538] Use Koha::Logger in longoverdue.pl
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15538 Martin Renvoize (ashimema) <martin.renvoize(a)openfifth.co.uk> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |42837 CC| |martin.renvoize(a)openfifth.c | |o.uk Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42837 [Bug 42837] Improve and extend systems/developer facing logging in Koha -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 16329] New: Koha::Logger->sql(). Unified interface to log SQL statements OR use DBIx::Log4perl
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16329 Bug ID: 16329 Summary: Koha::Logger->sql(). Unified interface to log SQL statements OR use DBIx::Log4perl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Instead of whenever needing to log SQL statements, making a custom logging output/function, introduce a centralized subroutine to handle all sql-statement logging. How the SQL-statements should be logged remains to be seen, but currently simply presenting very simple formatting we can discuss about. SQL libraries (DBI, DBIx) also allow logging SQL-statements but lack the fine-grained control Log4perl offers. Or maybe Log4perl can be integrated better to DBI / DBIx with this: https://metacpan.org/pod/DBIx::Log4perl Because I am not a huge fan of DBIx and also integrating that to Koha::Object is a lot of work, will not pursue that track further. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 16304] New: Koha::Logger, lazy load loggers so environment can be properly set.
by bugzilla-daemon＠bugs.koha-community.org 12 Jun '26

12 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16304 Bug ID: 16304 Summary: Koha::Logger, lazy load loggers so environment can be properly set. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org If you instantiate Koha::Loggers before having set the C4::Context->interface, their interface defaults to 'opac'. This is rather undesired especially for 'commandline' scripts such as cronjobs. A solution to this is to lazyLoad loggers when they are really needed. LazyLoading might also have a performance boost when using packages that initialize a package-level logger but which never gets used. see t/Koha/Logger.t on how to replicate this issue, but here is a nutshell of how to replicate this issue: @@ file A.pm package A; use Koha::Logger; my $logger = Koha::Logger->get({category => __PACKAGE__}); #interface unknown sub doStuff { $logger->error('My interface is always "opac"'); } @@ script run.pl use C4::Context; C4::Context->interface('commandline'); use A; A::doStuff(); #error is logged using the "opac"-interface instead #of the "commandline"-interface -- You are receiving this mail because: You are watching all bug changes.

1 15