Skip to content
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

Open
aakerbeere opened this issue Nov 8, 2024 · 4 comments
Assignees

Comments

@aakerbeere
Copy link

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.

@lennartdohmann lennartdohmann self-assigned this Nov 19, 2024
@lennartdohmann
Copy link
Contributor

lennartdohmann commented Nov 19, 2024

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 Show details as shown on the screenshot? That would help a lot.
2024-11-19_11-32

It would also be very helpful to know:

  • In which environment is your Nextcloud instance running?
  • Which version are you using? (Antivirus app and Nextcloud server)
  • How often does the problem occur and after how long?

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!

@aakerbeere
Copy link
Author

aakerbeere commented Nov 20, 2024

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:
{"reqId":"NtLeP0uMAn4dLclGzIbT","level":3,"time":"2024-11-20T22:01:48+01:00","remoteAddr":"","user":"--","app":"gdatavaas","method":"","url":"--","message":"File 381191 could not be scanned with GData VaaS because there was a temporary upstream server error","userAgent":"--","version":"30.0.2.2","data":{"app":"gdatavaas"},"id":"673e4e553c85a"}

Nextcloud: 30.0.2.2 running on:
Raspberry Pi 4 Model B Rev 1.4, 8GB running Debian 12.8 (bookworm)
G DATA Antivirus, Version 30.1.2 (originating from app store)

cheers

@unglaublicherdude
Copy link
Member

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: {"reqId":"NtLeP0uMAn4dLclGzIbT","level":3,"time":"2024-11-20T22:01:48+01:00","remoteAddr":"","user":"--","app":"gdatavaas","method":"","url":"--","message":"File 381191 could not be scanned with GData VaaS because there was a temporary upstream server error","userAgent":"--","version":"30.0.2.2","data":{"app":"gdatavaas"},"id":"673e4e553c85a"}

Nextcloud: 30.0.2.2 running on: Raspberry Pi 4 Model B Rev 1.4, 8GB running Debian 12.8 (bookworm) G DATA Antivirus, Version 30.1.2 (originating from app store)

cheers

Can you send us the Sha256-Checksum of that file?

@aakerbeere
Copy link
Author

thx @unglaublicherdude

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.
At user level it is not recognized.
So no Sha256-Checksum available.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants