[Koha-bugs] [Bug 13431] Shared FastMmap file causes issues

bugzilla-daemon at bugs.koha-community.org bugzilla-daemon at bugs.koha-community.org
Thu Dec 11 19:31:59 CET 2014


http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13431

--- Comment #6 from Jacek Ablewicz <abl at biblos.pk.edu.pl> ---
Ouch, after testing this on the production server for a little while I realized
that fixing it in that way is not such a good idea after all :(, it has some
unforseen side effects. Problem is that with Cache::FastMmap we are caching
some things (like MARC frameworks) persistently and indefinitely: they never
expire from the cache (like e.g. authorized values do, after 5 seconds AFAIRC).
Cached MARC frameworks are only explicitly invalidated and updated to the new
values after introducing some changes to them via web interface. So if there is
separate copy of the cache file being used by command line scripts, MARC
frameworks cached there would sadly never get updated. I dont know how to fix
it properly.. perhaps setting 'unlink_on_exit' to 1 (and/or setting expire_time
to something other then 0), when GATEWAY_INTERFACE environment variable is not
defined, would be somehow acceptable solution (?). As a quick & dirty fix,
'chmod 666 /tmp/sharefile-koha-koha' seems to work as well, but that's probably
not a very good idea :).

Also, regarding multi-tenant servers: apparently setting up different
namespaces for different tenants may still be much desired thing to do,
regardless of this particular bug manifesting itself or not. This error only
has a chance to immediately show itself in such setups where there is different
UID being used for each tenant (I guess this is how things are set up by
default in the packaged version ?). But in manually configured multi-instance
servers, when there is a same UID in use on the WWW server side for different
tenants - and they don't have their own separate namespaces defined properly
yet - after the upgrade, there would be no error visible, but still more and
more important per-instance Koha settings (frameworks, authorized values, ...)
may possibly end up being unintentionally shared between 2+ tenants.

-- 
You are receiving this mail because:
You are watching all bug changes.


More information about the Koha-bugs mailing list