0
No logs when config file lock blocks indefinitely
Source: nextcloud/server#35008 · opened by @jficz
⚠️ This issue respects the following points: ⚠️ • This is a bug, not a question or a configuration/webserver/proxy issue. • This issue is not already reported on Github _(I've searched it)_. • Nextcloud Server is up to date. See [Maintenance and Release Schedule]( for supported versions. • Nextcloud Server is running on 64bit capable CPU, PHP and OS. • I agree to follow Nextcloud's [Code of Conduct]( Bug description One of the first things that happens during start is loading and *locking* config file(s) with flock(). If, for whatever reason, the locking mechanism at the OS level blocks indefinitely, there is no way for the user to have any idea what's actually going on without resorting to advanced debugging. This is true for both normal operation (via fpm, mod, etc.) and for occ which makes the issue even more frustrating. The call to the function happens before any kind of reasonable logs are displayed. In my case config.php…
No pledges yet. Be the first to back this.
Comments
Similar requests
Possible DB indexes
0 votes · 0 comments
Locked files: not enough infos for end user, too much for admin
1 vote · 0 comments
Lock timeout
0 votes · 0 comments
File Locking and (S3) Object Storage or NFS (v3/v4)
2 votes · 0 comments
File scanner does not detect endless loops when scanning external storage
3 votes · 0 comments
No comments yet.