On 9/30/25 17:48, Michael Hafen wrote:
Did MARC::Record get loaded from CPAN? Perhaps you have a newer version of that module then you had on the old server? That's kind of a shot in the dark, but my first reaction was along those lines too. Might be worth checking at least, if you haven't already.
Thanks, yes, there were a few that had to be found at CPAN (not by choice, just unavailability elsewhere.) This was not a "direct" CPAN, but could have been "updated' as a side-line or dependency. Tomorrow, I'll replace it with the original, if different. Again tnx and br Paul
On Tue, Sep 30, 2025 at 2:42 PM Paul A via Koha-devel <koha- devel@lists.koha-community.org <mailto:koha-devel@lists.koha- community.org>> wrote:
Kia ora, greetings -- from the past, some of you will remember me.
Nut shell : we have been running (charitable library, non lending) Koha catalogue since 2011 (v. 3.08.24 since July 2015). Rock solid until we got overwhelmed by DDoS and/or AI bots. Thermal protection on the Koha server (apache2 proxied from nginx) failed, literal meltdown.
Built a new server (12 core intel CPU, 64G memory, Ubuntu 14.04 LTS security mods - I know, please don't flame me), reinstalled from tar and backup. Apparently a dead-ringer copy of what we had for over a decade.
Public server perfect <https://opac.navalmarinearchive.com <https:// opac.navalmarinearchive.com>>. Mysql, Zebra, Pazpar have reconstituted over a hundred thousand biblios and items - no discernible errors, all public users happy (except hackers and AI bots mitigated at front end nginx.)
But ... Koha admin (intranet) works fine for everything (items, reports, logs, "about"...) EXCEPT Biblios won't edit nor write new (manual input, nor z3950) records.
ERROR : Can't call method "fields" on an undefined value at /usr/share/koha/lib/C4/Biblio.pm line 2483.
2482 # traverse through record 2483 MARCFIELD: foreach my $field ( $record->fields() ) { 2484 my $tag = $field->tag(); if elsif ....
We've spent nearly a week, finding minor variations in backups of Biblio.pm (occasional line renumbering and developers' signatures), nothing from a Perl logic perspective. We've done the obvious "diff's", permissions, ownerships, restarts, reboots, koha_perl_deps.pl <http://koha_perl_deps.pl>, SAX parser, perl modules, environment.
It's got to be something blazingly simple, after a decade of superb Koha service. Any and all assistance in saving my sanity would be truly appreciated,
Thanks and warmest regards, Paul
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org <mailto:Koha-devel@lists.koha- community.org> https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel <https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel> website : https://www.koha-community.org/ <https://www.koha- community.org/> git : https://git.koha-community.org/ <https://git.koha-community.org/> bugs : https://bugs.koha-community.org/ <https://bugs.koha- community.org/>
-- Michael Hafen Washington County School District Technology Department Systems & Security Analyst