https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20077 Chris Nighswonger <cnighswonger@foundations.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cnighswonger@foundations.ed | |u --- Comment #7 from Chris Nighswonger <cnighswonger@foundations.edu> --- (In reply to Sven H. from comment #3)
I have a similar problem.
When I try to print the patron cards, the /usr/share/koha/intranet/cgi-bin/patroncards/create-pdf.pl does not finish and runs with 100% CPU load.
In plack-error.log I find the following lines: Use of uninitialized value $batch_id in concatenation (.) or string at /usr/share/koha/intranet/cgi-bin/patroncards/create-pdf.pl line 68. Use of uninitialized value in multiplication (*) at /usr/share/koha/lib/C4/Patroncards/Patroncard.pm line 239. Use of uninitialized value in addition (+) at /usr/share/koha/lib/C4/Patroncards/Patroncard.pm line 256. Use of uninitialized value in multiplication (*) at /usr/share/koha/lib/C4/Patroncards/Patroncard.pm line 288. Use of uninitialized value in multiplication (*) at /usr/share/koha/lib/C4/Patroncards/Patroncard.pm line 239. Use of uninitialized value in addition (+) at /usr/share/koha/lib/C4/Patroncards/Patroncard.pm line 256. Use of uninitialized value in multiplication (*) at /usr/share/koha/lib/C4/Patroncards/Patroncard.pm line 288. Use of uninitialized value in multiplication (*) at /usr/share/koha/lib/C4/Patroncards/Patroncard.pm line 239. Use of uninitialized value in addition (+) at /usr/share/koha/lib/C4/Patroncards/Patroncard.pm line 256.
The problem first appeared in February 2018 after I started the Ubuntu updates. Unfortunately I don't remember what has been updated.
snip
Unfortunately I am not able to print patron cards at the moment. It would be great if there was a solution for this soon.
I'm not sure what is going on in this particular instance, but taking the same steps on my production system results in a PDF containing the expected cards and nearly zero CPU usage. Unless someone else can confirm the problem, I would look at something local. Perhaps a Koha update did not apply well or some such, resulting in a script not being updated. Also, this appears to be a different problem than the one the OP reported. It would be good to open a new bug for it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.