-
Notifications
You must be signed in to change notification settings - Fork 158
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
SQL query faults #1133
Comments
This is the actual PSQL error:
Looking at the subquery:
This indeed returns three rows:
|
Any update on this matter, Greenbone is not usable this way. Job stale during the SQL failts. If you need any information, please ask. More then willing to provide it to you. |
This looks like an issue with products being installed in multiple locations on the same host or maybe detected multiple times due to vhosts sharing an IP address. |
It indeed is a master / slave (2) setup. Jobs with the same targets are used on both the slaves. Great to hear it's known issue. I'll be most happy if you can implement a fix so I can run again. |
The patch has solved those SQL errors, but I get new errors: #1148 |
Expected behavior
No SQL errors in gvmd.log
Actual behavior
I've had these SQL errors before, but to elimitate possible mistakes by myself I started with a fresh new DB. And agein fte rrunning for a few weeks, these errors start to popup during scans. If they appear, jobs get stuck.
I have multiple jobs, NVT and CVE's. I have some excludes setup. It's a master slave setup with one master and two slaves. I did not delete any host from assets, as it looks like the query searches for a unknown host.
Steps to reproduce
I think it has something to do with the overrides or master/slave things not going right.
GVM versions
gsa: Greenbone Security Assistant 9.0.1git-a2e4e3cd3-gsa-9.0
gvm: 9.0.1~git-5a976c58-gvmd-9.0
openvas-scanner: OpenVAS 7.0.1
gvm-libs: gvm-libs 11.0.1
Environment
Operating system:
Linux xxxxxxxxx 4.15.0-101-generic 102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.4 LTS"
The text was updated successfully, but these errors were encountered: