davo
January 23, 2025, 6:55am
1
This issue relates to some recent undocumented dependency changes due to package clashes between heimdal-dev and libkrb5-dev
The workaround is to swap libkrb5-dev for krb5-multidev , and for the smb scanner swap heimdal-dev to heimdal-multidev
This 2025 build script addresses the problem and works with Debian 12 and Ubuntu 24:
Dependencies for openvas-scanner :
bison libglib2.0-dev libgnutls28-dev libgcrypt20-dev libpcap-dev libgpgme-dev libksba-dev rsync nmap libjson-glib-dev libcurl4-gnutls-dev libbsd-dev python3-impacket libsnmp-dev pandoc pnscan krb5-multidev
Dependencies for openvas-smb :
gcc-mingw-w64 libgnutls28-dev libglib2.0-dev libpopt-dev libunistring-dev heimdal-multidev perl-base
For more detail see issue links here:
opened 01:11AM - 22 Jan 25 UTC
closed 02:17PM - 23 Jan 25 UTC
bug
duplicate
<!--
If reporting an issue please try to provide the information asked below.
B… efore reporting an issue please:
1. Be aware that this is not a support forum. If your issue is rather a question
than a bug report, please use our community forum at
https://community.greenbone.net/c/gse instead.
2. Make sure that you're using the latest published GVM components for the
release you are using: https://community.greenbone.net/t/about-the-source-edition-gse-category/176
3. Check the list of issues whether it isn't already reported.
4. Read 1. again and if you still believe you found a software bug please
continue to file this issue. If you are in doubt use
https://community.greenbone.net/c/gse instead.
Thanks for your help to keep the communication channels clean and consistent!
-->
### Expected behavior
Product should build and install, then be available for scanning after following source build instructions
### Actual behavior
This has been broken for some months now. Everything seems to install without error following the community source build instructions exactly. After the build the application never becomes ready for scanning. Feeds status permanently shows _"Synchronization issue: Could not connect to scanner to get feed info"_
Note: In my troubleshooting, there seem to be errors in the openvasd source build documentation: see here for details: https://forum.greenbone.net/t/openvasd-source-build-docs-correction/20169 but applying these corrections also prodcuces the exact same outcome
Several others have been reporting the exact same issue to the community forum for some months, but this issue remains unanswered: https://forum.greenbone.net/t/cannot-update-nvt-feed/19467
### Steps to reproduce
1. Follow the community build docs with or without the above corrections.
### GVM versions
All latest builds, and also seems to affect build from around Sept 2024 onwards:
OPENVAS_SCANNER_VERSION=23.15.3
GSA_VERSION=24.2.0
GVM_LIBS_VERSION=22.15.2
GSAD_VERSION=24.1.1
OPENVAS_SMB_VERSION=22.5.6
PG_GVM_VERSION=22.6.7
GVMD_VERSION=24.2.0
OSPD_OPENVAS_VERSION=22.7.1
OPENVAS_DAEMON=23.15.3
### Environment
Debian 12 or Ubuntu 22 & 24
### Logfiles
No logfiles in /var/log/gvm are created as the scanner never really comes up after install. Only `ospd-openvas.log` is created, and this contains only the following lines:
```
OSPD[48101] 2025-01-22 00:45:00,707: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48128] 2025-01-22 00:46:01,201: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48150] 2025-01-22 00:47:01,703: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48173] 2025-01-22 00:48:02,200: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48200] 2025-01-22 00:49:02,695: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48225] 2025-01-22 00:50:03,205: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48242] 2025-01-22 00:51:03,700: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48259] 2025-01-22 00:52:04,194: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48278] 2025-01-22 00:53:04,704: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48305] 2025-01-22 00:54:05,200: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48326] 2025-01-22 00:55:05,714: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
```
and here:
opened 01:11AM - 22 Jan 25 UTC
closed 02:17PM - 23 Jan 25 UTC
bug
duplicate
<!--
If reporting an issue please try to provide the information asked below.
B… efore reporting an issue please:
1. Be aware that this is not a support forum. If your issue is rather a question
than a bug report, please use our community forum at
https://community.greenbone.net/c/gse instead.
2. Make sure that you're using the latest published GVM components for the
release you are using: https://community.greenbone.net/t/about-the-source-edition-gse-category/176
3. Check the list of issues whether it isn't already reported.
4. Read 1. again and if you still believe you found a software bug please
continue to file this issue. If you are in doubt use
https://community.greenbone.net/c/gse instead.
Thanks for your help to keep the communication channels clean and consistent!
-->
### Expected behavior
Product should build and install, then be available for scanning after following source build instructions
### Actual behavior
This has been broken for some months now. Everything seems to install without error following the community source build instructions exactly. After the build the application never becomes ready for scanning. Feeds status permanently shows _"Synchronization issue: Could not connect to scanner to get feed info"_
Note: In my troubleshooting, there seem to be errors in the openvasd source build documentation: see here for details: https://forum.greenbone.net/t/openvasd-source-build-docs-correction/20169 but applying these corrections also prodcuces the exact same outcome
Several others have been reporting the exact same issue to the community forum for some months, but this issue remains unanswered: https://forum.greenbone.net/t/cannot-update-nvt-feed/19467
### Steps to reproduce
1. Follow the community build docs with or without the above corrections.
### GVM versions
All latest builds, and also seems to affect build from around Sept 2024 onwards:
OPENVAS_SCANNER_VERSION=23.15.3
GSA_VERSION=24.2.0
GVM_LIBS_VERSION=22.15.2
GSAD_VERSION=24.1.1
OPENVAS_SMB_VERSION=22.5.6
PG_GVM_VERSION=22.6.7
GVMD_VERSION=24.2.0
OSPD_OPENVAS_VERSION=22.7.1
OPENVAS_DAEMON=23.15.3
### Environment
Debian 12 or Ubuntu 22 & 24
### Logfiles
No logfiles in /var/log/gvm are created as the scanner never really comes up after install. Only `ospd-openvas.log` is created, and this contains only the following lines:
```
OSPD[48101] 2025-01-22 00:45:00,707: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48128] 2025-01-22 00:46:01,201: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48150] 2025-01-22 00:47:01,703: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48173] 2025-01-22 00:48:02,200: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48200] 2025-01-22 00:49:02,695: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48225] 2025-01-22 00:50:03,205: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48242] 2025-01-22 00:51:03,700: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48259] 2025-01-22 00:52:04,194: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48278] 2025-01-22 00:53:04,704: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48305] 2025-01-22 00:54:05,200: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
OSPD[48326] 2025-01-22 00:55:05,714: ERROR: (ospd_openvas.db) openvas executable not available. Please install openvas into your PATH.
```
cfi
January 23, 2025, 9:19am
2
@davo Only for clarification, the users here are using the Docker Containers (thus in the “Community Containers” category and also described in the postings) so any solution involving build scripts seems irrelevant / off-topic.
1 Like
DeeAnn
January 24, 2025, 12:11pm
3
(moderator note- moved from Cannot update NVT feed so the thread might look disconnected)
2 Likes
Hi,
Did you find a solution? I read the following:
“The workaround is to swap libkrb5-dev for krb5-multidev , and for the smb scanner swap heimdal-dev to heimdal-multidev ”
but i am not sure how to do it on my existing installation. I had the server running since October to avoid the problem until last week due to maintenance.
xinmpg
January 27, 2025, 11:59am
6
Thank you! Your workaround is working for me nicely with Docker on Ubuntu 24.04.1 LTS.
1 Like
Hi @xinmpg
how did you apply the workaround?