[Bug]: nextcloud-init-sync.lock considered as extra file by the scanner #2070
Comments
|
I didn't rerun the scan after changing the file owner, now the error disappeared, but still I should not have to change myself the owner of this file. |
|
This file isn't created by Nextcloud, but by community Docker image's How are your underlying volume mounts defined in your Docker? Either your Docker compose or command-line? Because the resulting ownership should be more like: And are you by chance running Docker under a different user or rootless? Related: #2057 |
|
Thanks fo₹your answer @joshtrichards and the mounts are done like this (docker compose extract): |
|
What is your underlying host OS/version, host hardware platform, When you restart the Nextcloud app container are there any interesting bits in the Docker logs for the container during startup? |
|
I'm running Nextcloud on a Raspberry Pi 4 with RaspberryPi OS After a docker restart on the container, I don't get anything interesting in the logs (knowing that the error disappeared since I chmoded myself the file) |
joshtrichards
added
the
needs review
|
Have you had this reoccur since? (Outside of v30.0.0 which was unrelated and due to an upstream change that is fixed in the upcoming v30.0.1). Outside of the recent regression (which we know the cause of), there haven't been any similar reports since your report. |
|
No, I didn't... I have it currently with 30.0.0 but I don't think I had it before (although I didn't check this for quite a long time) |
|
Alright. I'm going to close this since there haven't been other reports either so there isn't anything actionable at this point. |
Bug description
I get a warning that some file don't pass the integrity checks and when I look at the details, I get:
Looking at the logs, I can see:
but this file is created by nextcloud itself in the container so it's weird
Checking the file permissions inside the container:
-rw------- 1 root root 0 Sep 23 08:02 /var/www/html/nextcloud-init-sync.lockI changed the ownership to www-data:www-data in the container and the above error disappeared but the integrity check continue to fail
Steps to reproduce
Expected behavior
This file should not be considered in the integrity check
Installation method
Community Docker image
Nextcloud Server version
27
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 22 to 23)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
{ "system": { "installed": true, "datadirectory": "***REMOVED SENSITIVE VALUE***", "instanceid": "***REMOVED SENSITIVE VALUE***", "htaccess.RewriteBase": "\/", "default_language": "fr", "default_locale": "fr_FR", "knowledgebaseenabled": true, "default_phone_region": "FR", "apps_paths": [ { "path": "\/var\/www\/html\/apps", "url": "\/apps", "writable": false }, { "path": "\/var\/www\/html\/custom_apps", "url": "\/custom_apps", "writable": true } ], "memcache.local": "\\OC\\Memcache\\APCu", "memcache.distributed": "\\OC\\Memcache\\Redis", "memcache.locking": "\\OC\\Memcache\\Redis", "redis": { "host": "***REMOVED SENSITIVE VALUE***", "password": "***REMOVED SENSITIVE VALUE***", "port": 6379 }, "mail_sendmailmode": "smtp", "mail_smtpmode": "smtp", "mail_smtphost": "***REMOVED SENSITIVE VALUE***", "mail_smtpport": "587", "mail_smtpauth": true, "mail_smtpauthtype": "LOGIN", "mail_smtpname": "***REMOVED SENSITIVE VALUE***", "mail_smtppassword": "***REMOVED SENSITIVE VALUE***", "mail_from_address": "***REMOVED SENSITIVE VALUE***", "mail_domain": "***REMOVED SENSITIVE VALUE***", "passwordsalt": "***REMOVED SENSITIVE VALUE***", "secret": "***REMOVED SENSITIVE VALUE***", "twofactor_enforced": "false", "twofactor_enforced_groups": [ "admin" ], "twofactor_enforced_excluded_groups": [], "overwritehost": "nextcloud.<my domain>", "overwrite.cli.url": "https:\/\/nextcloud.<my domain>", "overwriteprotocol": "https", "trusted_domains": [ "localhost", "192.168.1.8", "nextcloud.<my domain>", "blog.<my domain>" ], "trusted_proxies": "***REMOVED SENSITIVE VALUE***", "dbtype": "mysql", "version": "27.1.1.0", "dbname": "***REMOVED SENSITIVE VALUE***", "dbhost": "***REMOVED SENSITIVE VALUE***", "dbport": "", "dbtableprefix": "oc_", "mysql.utf8mb4": true, "dbuser": "***REMOVED SENSITIVE VALUE***", "dbpassword": "***REMOVED SENSITIVE VALUE***", "logtimezone": "Europe\/Paris", "loglevel": 2, "maintenance": false, "app_install_overwrite": [ "audioplayer", "previewgenerator", "keeweb" ], "theme": "", "mail_smtpsecure": "TLS" } }List of activated Apps
Nextcloud Signing status
Nextcloud Logs
24MB, only adding related errors: {"reqId":"zDBWUSdnTLLbD8uhFxoM","level":3,"time":"2023-09-23T10:04:31+02:00","remoteAddr":"","user":"--","app":"PHP","method":"","url":"--","message":"hash_file(/var/www/html/nextcloud-init-sync.lock): Failed to open stream: Permission denied at /var/www/html/lib/private/IntegrityCheck/Checker.php#211","userAgent":"--","version":"27.1.0.7","data":{"app":"PHP"},"id":"650ea3672af6f"}Additional info
No response
The text was updated successfully, but these errors were encountered: