Log spamming after update to 10.7.0

After upgrade OC server to 10.7.0 everything works fine except I get tons of messages in log file which looks like this:

ignoring lock release with type 1 for files/f41ba94156601520b14cf6fbd69d4f88. Lock hasn’t been acquired before

Last week my log file grow up to 50Mb and I can’t figure out what’s going on. Messages like that didn’t appear before update. Is anyone have same issue?

Server configuration

Operating system: Ubuntu 20.04.2 LTS

Web server: Apache/2.4.41

Database: MariaDB 10.3.25

PHP version: PHP 7.4.3

ownCloud version: 10.7.0

That’s “known”. We’re trying to be a bit more strict with the locks, so we’ve added those logs to detect situations which shouldn’t happen. Please, try to describe what you were doing in order to reproduce the problem.

Note that the log is harmless, so there is no real action you need to take. You can change the log level if it bothers you.

Actually I know what log is.

I don’t do anything special, just everyday usage. These messages started appear right after OC update.

If you’re confident about applying patches, you can try https://github.com/owncloud/core/pull/38574/files
(formal patch in https://patch-diff.githubusercontent.com/raw/owncloud/core/pull/38574.patch)
Note that I normally recommend to wait for the next upgrade since an isolated patch might have side effects. It shouldn’t have in this case, but you never know.

1 Like

Wow! Thank you!

// Good to know it’s not the issue with my hadns and Redis/php config…

Hello,
I’m seeing these logs a lot too. Just did a fresh install of owncloud 10.7.0. Sent 3053 files and 548 folders to the server using regular synchronization : copy/paste everything in 2 batches,

  • from windows 10 host client 2.5.1 build 10807 (just noticed it’s not the last version; i’ll update the client)
  • to raspberry pi OS server (debian 10).

I got 13073 occurences of “ignoring lock release with type 1 for files” so it’s several of them for each file. Typically 4 logs in a row for each file:

{"reqId":"96d8e0e2-13c4-4150-a330-c43492afb0a5","level":2,"time":"2021-04-13T21:43:31+00:00","remoteAddr":"192.168.x.x","user":"myuser","app":"core","method":"PUT","url":"\/remote.php\/dav\/files\/myuser\/path\/file","message":"ignoring lock release with type 1 for files\/onelongid. Lock hasn't been acquired before"}
{"reqId":"96d8e0e2-13c4-4150-a330-c43492afb0a5","level":2,"time":"2021-04-13T21:43:31+00:00","remoteAddr":"192.168.x.x","user":"myuser","app":"core","method":"PUT","url":"\/remote.php\/dav\/files\/myuser\/path\/file","message":"ignoring lock release with type 1 for files\/anotherlongid. Lock hasn't been acquired before"}
{"reqId":"96d8e0e2-13c4-4150-a330-c43492afb0a5","level":2,"time":"2021-04-13T21:43:31+00:00","remoteAddr":"192.168.x.x","user":"myuser","app":"core","method":"PUT","url":"\/remote.php\/dav\/files\/myuser\/path\/file","message":"ignoring lock release with type 1 for files\/yetanotherlongid. Lock hasn't been acquired before"}
{"reqId":"96d8e0e2-13c4-4150-a330-c43492afb0a5","level":2,"time":"2021-04-13T21:43:31+00:00","remoteAddr":"192.168.x.x","user":"myuser","app":"core","method":"PUT","url":"\/remote.php\/dav\/files\/myuser\/path\/file","message":"ignoring lock release with type 1 for files\/yetanotherlongid. Lock hasn't been acquired before"}

Quick check with the desktop client and basic syncing: I couldn’t reproduce the issue with the patch.
As said, if you’re confident applying patches, feel free to apply the patch mentioned above, otherwise wait until the next server version. You can also set the log level to “error” as a temporary workaround.

Hello @jvillafanez . thanks for looking at it. I haven’t installed the patch. I can wait until the next release. Just wanted to help with your little experiment :slight_smile:
I have installed the latest client and created a single empty file. it produced the log (one time).
I understand that the issue is fixed by the patch or will be fixed (probably) in the next release