File 381191 could not be scanned with GData VaaS because there was a temporary upstream server error #158
Comments
|
Hi @aakerbeere , thanks for reporting your problem, I will look into it. I can't recreate the problem though. Could you send me a detailed log message from the Nextcloud log reader, on the context menu and then It would also be very helpful to know:
The more details you can give me, the more likely it is for me to see your problem as well. Thanks again for reporting it! |
|
thx @lennartdohmann for spending time. After posting i disabled VAAS. After enabling it takes few minutes for the error to come up again and now is recorded approx. every 5 min. Raw data: Nextcloud: 30.0.2.2 running on: cheers |
Can you send us the Sha256-Checksum of that file? |
|
The object "381191" can only be recognized at file system level represented by "/var/www/nextcloud/data/appdata_oc97vfin04v4/preview/c/e/b/5/9/a/9/381191" and is a empty folder. I don't know how it got there, what it is and if it does something. |
This is weird as it should not scan folders. Is this possibly a symbolic link in your directory structure? Can you send us the output of a |
|
thx @unglaublicherdude |
|
This is strange, because we specifically select the items from the _files-table, that are not directories. Are you familiar with SQL? We would like you to run a Query to get some further data for this issue. The first would be this: SELECT
fileid,
(SELECT
mimetype
FROM oc_mimetypes
WHERE oc_filecache.mimetype = oc_mimetypes.id) as mimetype
FROM oc_filecache
WHERE fileid = 381191 \GThe table prefix (in this example the default oc_) might differ for you, The result should be something like this: So we can see, what the actual mimetype your nextcloud filecache is. In our query we already have this part to omit directories, but the strings might differ. |
|
The command "\G" at the end of the "WHERE"-clause is considered invalid (PG 17.2) and without it, the statement returns nothing. Also maybe syntax error (don't know, statements bracketing) cheers |
|
OK. Does the exact error still occur or has the ID in the error changed? |
|
I just enabled VaaS again and the error comes up after about 5min. But the file-ID has changed. Result is the same (Invalid command for "\G", empty output without "\G": |
|
I actually recognize the file ID to be different on every item. |
|
Multiple errors are actually listed for different files: |
|
What's weird is, that you also cannot find the files with these ids in the database, because we basically get all the ids from the database. Does your Nextcloud instance have highly fluctuating data? So maybe the file is already gone, when the actual scan is done, because there is a time in between the query and the actual scan depending on where the fileid is in the list and how long the scans before that fileid actually take. But to avoid having this error in the logs, we can at least introduce some checks before the scan so you don't get that error anymore. |
|
No higly fluctuating data. I am the one and only user :) Since one hour, no more errors of this type did show up. If the scan continues after the error, i don't mind about it. I believed it stopped because VaaS UI does not update anymore the output of "Files scanned: 45761 / 66239". But this is probably because all the work has already been done. |
|
Just do be sure that we don't just don't know about a mimetype that is in your DB, can you provide the output of the following query? SELECT * FROM oc_mimetypes |
|
Returns nothing. Doing something wrong? |
|
I don't know how psql works with multiple command but i would suggest selecting the db with the command line parameter --dbname and then send only the SELECT command. sudo -i -u postgres psql --dbname=nextcloud --command='SELECT * FROM oc_mimetypes' |
|
sry. |
|
Ok. Nice. That is definetly alot more than we have in our database with just the base installation. We will look into them. Might it be possible that you also run the other query with the fileid again? |
|
With the last corresponding error showing up few minutes before last midnight i get |
|
So this should definetly be a file by this Filetype. Is it the same for the file that you found to actually be a directory? |
|
|
Ok. Thank you for all the effort. So it seems that both ids are saved as files in your Nextcloud database. That's a good thing because that means our query IS correct. I let that information cook the next days and come back to you when I have an idea how to proceed with that information. |
After having set up VaaS it worked as expected for some time. At a given moment it stopped with logging errors as seen in post title. I found somewhere in the documentation in this case to restart the server.
I don't want to frequently do this only because connection is lost.
The text was updated successfully, but these errors were encountered: