Hi pls im a librarian from the philippines and we encountered a problem in accessing our koha ils, please help us with the following issues that appear in the browser when trying to open it: "Software error: Can't call method "do" on unblessed reference at /usr/share/koha/lib/C4/Context.pm line 816. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 88. Compilation failed in require at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 25. BEGIN failed--compilation aborted at /usr/share/koha/intranet/cgi- bin/mainpage.pl line 25. For help, please send mail to the webmaster ([no address given]), giving this error message and the time and date of the error." Hope you could help us in resolving the issues. Best regrads, Israelex Velena
On 05/28/15 11:12, Lex wrote:
Hi pls im a librarian from the philippines and we encountered a problem in accessing our koha ils, please help us with the following issues that appear in the browser when trying to open it:
"Software error:
Can't call method "do" on unblessed reference at /usr/share/koha/lib/C4/Context.pm line 816. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 88.
OK, it looks like something is wrong in the authentication system. What version of koha did you try to install? Then someone can look up what lines 816 and 88 try to do on http://git.koha-community.org/ and make a better guess. Line 88 of C4/Auth might be trying to pull in the Auth_with_cas module - are you trying to use cas and how is it configured? Look at the koha-error_log file for that library's virtual host (maybe somewhere in /var/log/koha or /var/log/apache if I remember correctly) and see if there are any more details. Hope that helps, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op http://koha-community.org supporter, web and library systems developer. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire (including development) at http://www.software.coop/
Lex schreef op do 28-05-2015 om 10:12 [+0000]:
Hi pls im a librarian from the philippines and we encountered a problem in accessing our koha ils, please help us with the following issues that appear in the browser when trying to open it:
Can you provide more information? * How have you installed Koha? * What version of Koha have you installed? * What Linux distribution and version is it on? * Did it ever work, and if so, what has changed since then? -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
Hi all! This was already figured out. It was because of the server being bloated because of the opac-error.log. There's this weird crawler from Russia that takes up a considerable amount in the log= http://www.abuseipdb.com/check/188.143.232.41 [Fri May 29 07:59:33.658328 2015] [cgi:error] [pid 3686] [client 188.143.232.41:44932] AH01215: [Fri May 29 07:59:33 2015] opac-suggestions.pl: Use of uninitialized value $borrowernumber in n$ [Fri May 29 07:59:33.658414 2015] [cgi:error] [pid 3686] [client 188.143.232.41:44932] AH01215: [Fri May 29 07:59:33 2015] opac-suggestions.pl: Use of uninitialized value $borrowernumber in n$ [Fri May 29 07:59:33.658484 2015] [cgi:error] [pid 3686] [client 188.143.232.41:44932] AH01215: [Fri May 29 07:59:33 2015] opac-suggestions.pl: Use of uninitialized value $borrowernumber in n$ I don't know if it's related with the error - that since the server is bloated it can not even be accessed. Anyway: the koha version is 3.18, debian package, and installed in Amazon free AWS' Ubuntu. I know the server was optimized following this guideline: http://wiki.koha-community.org/wiki/Koha_Tuning_Guide. In relation to this post, did anybody in the Koha community experienced such weird web crawlers. Thanks and cheers! -- View this message in context: http://koha.1045719.n5.nabble.com/Help-Software-Error-tp5842000p5842197.html Sent from the Koha-general mailing list archive at Nabble.com.
And oh yes once the bloated error log was deleted and the server restarted, the Koha ILS was already accessible. I'm particularly curious if that really is the case. -- View this message in context: http://koha.1045719.n5.nabble.com/Help-Software-Error-tp5842000p5842198.html Sent from the Koha-general mailing list archive at Nabble.com.
schnydszch schreef op vr 29-05-2015 om 05:17 [-0700]:
And oh yes once the bloated error log was deleted and the server restarted, the Koha ILS was already accessible. I'm particularly curious if that really is the case.
It's quite plausible. All manner of things can go wrong when you run out of disk space, at the very least I'd expect mysql to throw a bit of a fit. For the servers we monitor, part of that monitoring by default is keeping an eye on disk space, usually warning when it gets below about 70% free and erroring at 80%. Often the final 10% of a disk is reserved for the superuser only in order to make it possible for them to log in and repair things. As for webcrawlers, they can be a real problem every once in a while. We slow down the well behaving ones with robots.txt to prevent them putting too much load on the server, and if we spot one that's not obeying that, we firewall it off. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
participants (4)
-
Lex -
MJ Ray -
Robin Sheat -
schnydszch