-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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. |
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: