[Bug]: User username still has unscanned files after running background scan, background scan might be stopped prematurely

[ostasevych]

⚠️ 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 OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

Hi! I am constantly getting warning message for one of users (out of 25):
User username still has unscanned files after running background scan, background scan might be stopped prematurely
And this happens once per an hour.

Steps to reproduce

1. Just observ in logs the warning message User username still has unscanned files after running background scan, background scan might be stopped prematurely

Expected behavior

No warning message or more explanation added.

Installation method

Community Web installer on a VPS or web space

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?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

[matti-owl]

28.0.2 same

[JohanBoshoffWebAware]

I also have this problem, only with one user. Is there any way to fix it while waiting for a fix?

[dohlin]

Would be so great if this could be resolved. Been a bug for the last few releases, yesterday I literally gave up and nuked my old install and re-installed using the new AIO method. Today I'm back to getting the same error for the same user. The only thing I use NC for is tasks, and accessing files remotely via my NAS mounted as an SMB/CIFS external storage. Don't understand why this is happening, even on a brand new fresh install.

[JohanBoshoffWebAware]

You will need to revert to using Nextcloud 26 or early versions of 27, before 27.1.5 and using the Desktop Client of the 3.11 range if you want to use a fresh install.

It is frustrating that the bug has been logged so long ago, two new releases and still no fix. If only the Temporary Files Lock app had a command to remove all file locks that do not get removed or add it to the cron job if there are stuck files then it would be moving forward at least.

Obviously, testing is not done properly before releasing new versions and the bugs persist, but Nextcloud is already busy with version 29 Beta. Why push version upgrades when old bugs remain on older versions?

Just stick to one version to get is stable, get all the bugs fixed, and then move on to new features and version upgrades.

[dohlin]

You will need to revert to using Nextcloud 26 or early versions of 27, before 27.1.5 and using the Desktop Client of the 3.11 range if you want to use a fresh install.

It is frustrating that the bug has been logged so long ago, two new releases and still no fix. If only the Temporary Files Lock app had a command to remove all file locks that do not get removed or add it to the cron job if there are stuck files then it would be moving forward at least.

Obviously, testing is not done properly before releasing new versions and the bugs persist, but Nextcloud is already busy with version 29 Beta. Why push version upgrades when old bugs remain on older versions?

Just stick to one version to get is stable, get all the bugs fixed, and then move on to new features and version upgrades.

100% agree. I'm am glad I'm not the only one seeing this bug, but I have to agree that it's really unfortunate bugs like this persist so long when new releases are being shoved down the pipe.

[CDSWambo]

so it's a known bug?

[metronidazole]

I'm getting this error with my read only external storage mount

[CDSWambo]

@metronidazole wait, you mean with an external hdd connected to your server? I have one that's through sata connected to my zimaboard so it shouldn't be a problem. The ro fs is set in your fstab?

[metronidazole]

@metronidazole wait, you mean with an external hdd connected to your server? I have one that's through sata connected to my zimaboard so it shouldn't be a problem. The ro fs is set in your fstab?

No with a external storage (nextcloud feature) configured. The file system is not read only, it's just configured as read only in nextcloud settings.

[joshtrichards]

This isn't a bug (at least this message alone isn't) per se. It's just a warning that the background scanner didn't finish on the last user. The question is, in each of your cases, why it's not completing?

Please do the following:

• Check your Nextcloud log for the time period immediately before this warning is logged (it may have errors/exceptions/etc related to the scan - at least if you have a default loglevel of 2 or lower)
• Try doing a scan of unscanned files from the command line (basically what this background job does) with verbose mode on and seeing what happens (occ files:scan --unscanned -vvv [user])

[metronidazole]

This isn't a bug (at least this message alone isn't) per se. It's just a warning that the background scanner didn't finish on the last user. The question is, in each of your cases, why it's not completing?

Please do the following:

* Check your Nextcloud log for the time period immediately before this warning is logged (it may have errors/exceptions/etc related to the scan - at least if you have a default `loglevel` of `2` or lower)

* Try doing [a scan of unscanned files from the command line](https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/occ_command.html#scan) (basically what this background job does) with verbose mode on and seeing what happens (`occ files:scan --unscanned -vvv [user]`)

My log level is 2, there is no other log messages other than the described one being spammed every 10-15.

The second command doesn't work as the user doesn't exist anymore "Unknown user 1 4a286a0f-142b-3242-98e0-9cfdc9f443bd.

If I run it for all users (--all), then it does list some files (for an existing user) but with no errors

+---------+-------+-----+---------+---------+--------+--------------+
| Folders | Files | New | Updated | Removed | Errors | Elapsed time |
+---------+-------+-----+---------+---------+--------+--------------+
| 56 | 406 | 0 | 0 | 0 | 0 | 00:00:04 |
+---------+-------+-----+---------+---------+--------+--------------+

The log messages seem to have stopped however, so it looks like the issue for me at least is resolved.