Summary: | Can't open __LOG_DIR__/opac-error.log (No such file or directory) | ||
---|---|---|---|
Product: | Koha | Reporter: | Claudio Costales <costalc> |
Component: | Architecture, internals, and plumbing | Assignee: | Bugs List <koha-bugs> |
Status: | CLOSED WORKSFORME | QA Contact: | Testopia <testopia> |
Severity: | major | ||
Priority: | P5 - low | CC: | dcook, magnus |
Version: | 20.05 | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Attachments: | log4perl |
Description
Claudio Costales
2021-02-14 17:41:37 UTC
Sounds like a bad log4perl.conf file. Can you share the /etc/koha/sites/<instance>/log4perl.conf file for your problematic instance? Created attachment 116869 [details]
log4perl
Hi David! See file attached please. Thanks! That is very weird... If you replace __LOG_DIR__ with /var/log/koha/fbarcelo and run "koha-plack --stop fbarcelo" and "koha-plack --start fbarcelo", you should be fine. It looks to me like you must have had a bad config file for quite some time, but the upgrade to 20.05 made it more noticeable. Thank you so much David! I've made the changes and it works fine again. (In reply to Claudio from comment #5) > Thank you so much David! I've made the changes and it works fine again. That's great to hear. I'll close this one for now, but I'll be keeping my eyes open for similar reports... (In reply to David Cook from comment #6) > I'll close this one for now, but I'll be keeping my eyes open for similar > reports... I have seen this too. On a server with lots of instances, one of them had this problem. I must confess I fixed it without investigating further. This should reveal any instances that have this problem: $ sudo grep "__LOG_DIR__" /etc/koha/sites/*/log4perl.conf (In reply to Magnus Enger from comment #7) > I have seen this too. On a server with lots of instances, one of them had > this problem. I must confess I fixed it without investigating further. Good to know! Based on the error, my guess is that there must've been a bug in the past that made the log4perl.conf not get generated correctly, but it went unnoticed. So in theory it shouldn't affect anyone that wasn't affected by that bug, but it's tough to know who is affected without checking everyone. That said... maybe it is worth writing some kind of patch to look for and fix this problem... |