I am still seeing some issues with the variable "lockdir" in the koha-conf.xml file. I'm getting the message: The configured <lockdir> entry in your koha-conf.xml file points to a non-writable directory (/var/lock/koha). What is unclear is *WHO* needs to write to this directory, which might change where I say the lockdir directory is located. In my case, on boot up, the ownership of /var/lock/koha is set to root with mode 755. So, there, few have ability to write to the directory. But, there may be subdirectories that can be updated, depending upon who needs access. No combinations have yet worked for me, however. There is no mention of lockdir in the documentation for 20.11 and the only thing we could find was some bugzilla updates. And yet, it is seen as something to warn about. Can whoever added it to the code also add it to the documentation? And explain what it is supposed to be used for and who needs the write access? Thanks, Tom -- *Tom Hanstra* *Sr. Systems Administrator* hanstra@nd.edu
On 2021-03-19 3:31 p.m., Tom Hanstra wrote:
I am still seeing some issues with the variable "lockdir" in the koha-conf.xml file. I'm getting the message:
The configured <lockdir> entry in your koha-conf.xml file points to a non-writable directory (/var/lock/koha).
lockdir should have the instance name (e.g. library) at the end of the path. <lockdir>/var/lock/koha/library</lockdir> This directory should be writeable for the koha instance user. GPML, Mark Tompsett
Hi I also am missing the lockdir setting. In the intranet Home/About Koha/System Information "Warnings regarding the system configuration": XML configuration file Warning: You are missing the <lockdir> entry in your koha-conf.xml file. Please add it, pointing to your Koha instance's lock dir. I looked at koha-conf-site.xml.in and saw: <zebra_lockdir>/var/lock/koha/__KOHASITE__</zebra_lockdir> <lockdir>/var/lock/koha/__KOHASITE__</lockdir> My site XML sites/libtest2/koha-conf.xml just had: <zebra_lockdir>/var/lock/koha/libtest2</zebra_lockdir> So I added on the line immediately after that: <lockdir>/var/lock/koha/libtest2</lockdir> What services do I need to restart or what to do for the system to pickup this change? The Home/About Koha/System Information still says I am missing this setting. Thanks Mike Lake On 2021-03-21 00:45, Mark Tompsett wrote:
On 2021-03-19 3:31 p.m., Tom Hanstra wrote:
I am still seeing some issues with the variable "lockdir" in the koha-conf.xml file. I'm getting the message:
The configured <lockdir> entry in your koha-conf.xml file points to a non-writable directory (/var/lock/koha).
lockdir should have the instance name (e.g. library) at the end of the path.
<lockdir>/var/lock/koha/library</lockdir>
This directory should be writeable for the koha instance user.
GPML, Mark Tompsett
_______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Hi, if you restarted plack, then I wonder if it could be in memcached, try restarting it and tell us how it goes. After restarting memached I think you need to restart plack one more time to flush the caches there as well. Joonas On 21/04/2021 13:34, Mike Lake wrote:
Hi
I also am missing the lockdir setting. In the intranet Home/About Koha/System Information "Warnings regarding the system configuration": XML configuration file Warning: You are missing the <lockdir> entry in your koha-conf.xml file. Please add it, pointing to your Koha instance's lock dir.
I looked at koha-conf-site.xml.in and saw: <zebra_lockdir>/var/lock/koha/__KOHASITE__</zebra_lockdir> <lockdir>/var/lock/koha/__KOHASITE__</lockdir>
My site XML sites/libtest2/koha-conf.xml just had: <zebra_lockdir>/var/lock/koha/libtest2</zebra_lockdir>
So I added on the line immediately after that: <lockdir>/var/lock/koha/libtest2</lockdir>
What services do I need to restart or what to do for the system to pickup this change? The Home/About Koha/System Information still says I am missing this setting.
Thanks Mike Lake
On 2021-03-21 00:45, Mark Tompsett wrote:
On 2021-03-19 3:31 p.m., Tom Hanstra wrote:
I am still seeing some issues with the variable "lockdir" in the koha-conf.xml file. I'm getting the message:
The configured <lockdir> entry in your koha-conf.xml file points to a non-writable directory (/var/lock/koha).
lockdir should have the instance name (e.g. library) at the end of the path.
<lockdir>/var/lock/koha/library</lockdir>
This directory should be writeable for the koha instance user.
GPML, Mark Tompsett
_______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
-- Joonas Kylmälä Tietojärjestelmäasiantuntija Kansalliskirjasto Kirjastoverkkopalvelut PL 15 (Unioninkatu 36) 00014 Helsingin yliopisto
Thanks Joonas I restarted memcached (/etc/init.d/restart) and now System Information show "No warnings." This is the first I have heard of plack. A list of the processes running show that its not running. I do see "koha-plack --help" shows it is installed but not enabled or running. Maybe best for that to be in a separate post later on :-) Thanks. --- Mike Lake On 2021-04-21 20:54, Joonas Kylmälä wrote:
Hi,
if you restarted plack, then I wonder if it could be in memcached, try restarting it and tell us how it goes. After restarting memached I think you need to restart plack one more time to flush the caches there as well.
Joonas
On 21/04/2021 13:34, Mike Lake wrote:
Hi
I also am missing the lockdir setting. In the intranet Home/About Koha/System Information "Warnings regarding the system configuration": XML configuration file Warning: You are missing the <lockdir> entry in your koha-conf.xml file. Please add it, pointing to your Koha instance's lock dir.
I looked at koha-conf-site.xml.in and saw: <zebra_lockdir>/var/lock/koha/__KOHASITE__</zebra_lockdir> <lockdir>/var/lock/koha/__KOHASITE__</lockdir>
My site XML sites/libtest2/koha-conf.xml just had: <zebra_lockdir>/var/lock/koha/libtest2</zebra_lockdir>
So I added on the line immediately after that: <lockdir>/var/lock/koha/libtest2</lockdir>
What services do I need to restart or what to do for the system to pickup this change? The Home/About Koha/System Information still says I am missing this setting.
Thanks Mike Lake
On 2021-03-21 00:45, Mark Tompsett wrote:
On 2021-03-19 3:31 p.m., Tom Hanstra wrote:
I am still seeing some issues with the variable "lockdir" in the koha-conf.xml file. I'm getting the message:
The configured <lockdir> entry in your koha-conf.xml file points to a non-writable directory (/var/lock/koha).
lockdir should have the instance name (e.g. library) at the end of the path.
<lockdir>/var/lock/koha/library</lockdir>
This directory should be writeable for the koha instance user.
GPML, Mark Tompsett
_______________________________________________
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
participants (4)
-
Joonas Kylmälä -
Mark Tompsett -
Mike Lake -
Tom Hanstra