Transactional file locking should be configured to use memory-based locking

[hannesa2]

After I updated #41165 to recent 10.13.4.1 I see in Admin page

Ok, after reading the easiest way to enable it

sudo apt install php7.4-apcu
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
php7.4-apcu is already the newest version (5.1.23-1+ubuntu22.04.1+deb.sury.org+1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

and change config.php
https://doc.owncloud.com/server/10.13/admin_manual/configuration/server/caching_configuration.html#apcu-configuration

The message is still there. Does someone understand, what wrong here ?

This is my config report

{
    "basic": {
        "license key": "***REMOVED SENSITIVE VALUE***",
        "date": "Wed, 31 Jan 2024 11:33:36 +0000",
        "ownCloud version": "10.13.4.1",
        "ownCloud version string": "10.13.4",
        "ownCloud edition": "Community",
        "server OS": "Linux",
        "server OS version": "Linux Latitude 5.15.0-92-generic #102-Ubuntu SMP Wed Jan 10 09:33:48 UTC 2024 x86_64",
        "server SAPI": "apache2handler",
        "webserver version": "Apache\/2.4.52 (Ubuntu) Phusion_Passenger\/6.0.10 OpenSSL\/3.0.2",
        "hostname": "www.server.info",
        "logged-in user": "hannes"
    },
    "stats": {
        "users": {
            "Database": {
                "total_count": 5,
                "guest_count": 0,
                "seen": 5,
                "logged in (30 days)": 3
            }
        },
        "groups": {
            "OC\\Group\\Database": 2,
            "OCA\\Guests\\GroupBackend": 1
        }
    },
    "config": {
        "filelocking.enabled": true,
        "memcache.local": "\\OC\\Memcache\\APCu",
        "updatechecker": false,
        "instanceid": "ocr8mbf8x3zx",
        "passwordsalt": "***REMOVED SENSITIVE VALUE***",
        "secret": "***REMOVED SENSITIVE VALUE***",
        "trusted_domains": [
            "www.server.info"
        ],
        "datadirectory": "\/daten\/owncloud\/data",
        "overwrite.cli.url": "https:\/\/www.server.info\/owncloud",
        "dbtype": "pgsql",
        "version": "10.13.4.1",
        "dbname": "owncloud",
        "dbhost": "localhost",
        "dbtableprefix": "oc_",
        "dbuser": "***REMOVED SENSITIVE VALUE***",
        "dbpassword": "***REMOVED SENSITIVE VALUE***",
        "logtimezone": "UTC",
        "installed": true,
        "mail_from_address": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpmode": "smtp",
        "mail_domain": "***REMOVED SENSITIVE VALUE***",
        "loglevel": 2,
        "maintenance": false,
        "theme": "",
        "updater.secret": "***REMOVED SENSITIVE VALUE***",
        "allow_user_to_change_mail_address": "",
        "files_antivirus.av_path": "\/usr\/bin\/clamscan",
        "mail_smtphost": "***REMOVED SENSITIVE VALUE***",
        "mail_smtpport": "465"
    },
    "integritychecker": {
        "passing": true,
        "enabled": true,
        "result": []
    },

[DeepDiver1975]

did you restart apache to load the newly installed php extension?

[hannesa2]

@DeepDiver1975
Restart: sure !
load php extension: no, in https://doc.owncloud.com/server/10.13/admin_manual/configuration/server/caching_configuration.html#apcu-configuration there was no such point. Or I missed it

Please can you point me to this.

Btw, thix https://markus-blog.de/index.php/2018/05/30/how-to-install-apcu-object-cache-in-php7-and-integrate-in-nextcloud/ changes in /etc/php/7.x/apache2/php.ini broke a sudo systemctl status apache2

[DeepDiver1975]

Restarting Apache loads the extension. It was meant as an explanation why restart is necessary.

[hannesa2]

Link #252 but doesn't help

[hannesa2]

I added in /etc/php/7.4/apache2/php.ini

apc.enabled=1
apc.file_update_protection=2
apc.optimization=0
apc.shm_size=256M
apc.include_once_override=0
apc.shm_segments=1

apc.ttl=7200
apc.user_ttl=7200
apc.gc_ttl=3600
apc.num_files_hint=1024
apc.enable_cli=0
apc.max_file_size=5M
apc.cache_by_default=1
apc.use_request_time=1
apc.slam_defense=0
#apc.mmap_file_mask=/tmp/apc/apc.XXXXXX
apc.stat_ctime=0
apc.canonicalize=1
apc.write_lock=1
apc.report_autofilter=0
apc.rfc1867=0
apc.rfc1867_prefix =upload_
apc.rfc1867_name=APC_UPLOAD_PROGRESS
apc.rfc1867_freq=0
apc.rfc1867_ttl=3600
apc.lazy_classes=0
apc.lazy_functions=0

sudo systemctl restart apache2

cd <your ownloud directory>
sudo wget https://raw.githubusercontent.com/krakjoe/apcu/master/apc.php

Then call the script in your domain via your browser, call https://<your-domain>/apc.php

but message is still there

[hannesa2]

I've no clue about php, otherwise I would debug into it and look why this message is there.

[iasdeoupxe]

This is a support question and thus should really go to https://central.owncloud.org/ (Remember this is a bug tracker for bugs in ownCloud, not a support channel how to configure it :-) ).

Short hint: You are configuring the "Memory Caching" with APCu:

https://doc.owncloud.com/server/10.13/admin_manual/configuration/server/caching_configuration.html#configuring-memory-caching

but you need to configure "Transactional File Locking" with Redis as the message is stating:

https://doc.owncloud.com/server/10.13/admin_manual/configuration/server/caching_configuration.html#configure-transactional-file-locking

[hannesa2]

Ok, pointing the other to some texts:

When I read about cache types, https://doc.owncloud.com/server/10.13/admin_manual/configuration/server/caching_configuration.html#cache-types I understand this either ...or, and not "I need all of them"

https://doc.owncloud.com/server/10.13/admin_manual/configuration/server/caching_configuration.html#apcu

The easiest cache to use is APCu,

So my idea was, lets go with APCu only ....
There was no word about redis

When I understand you right, I need now APCu and Redis, am I right ?

[iasdeoupxe]

https://central.owncloud.org/ -> For support questions (doesn't look like a bug in ownCloud to me)
https://github.com/owncloud/docs-server/issues -> If the docs are not clear enough

😉

[hannesa2]

Let's see if there is more will to solve it https://central.owncloud.org/t/transactional-file-locking-should-be-configured-to-use-memory-based-locking-unsolved/46934

[iasdeoupxe]

This is not about will, just about choosing the correct place 😉

• Here / GitHub: Bugs / Feature requests
• Central: Support / configuration questions link this