is this a joke? for what do we have a distribution wehn depending packages are not taken care of? [root@openvas:~]$ system-errors.sh Oct 4 11:26:15 openvas systemd[1]: openvas-scanner.service: Failed with result 'exit-code'. Oct 4 11:26:15 openvas systemd[1]: Failed to start OpenVAS Scanner. Oct 4 11:26:17 openvas systemd[1]: openvas-scanner.service: Failed with result 'exit-code'. Oct 4 11:26:17 openvas systemd[1]: Failed to start OpenVAS Scanner. Oct 4 11:26:18 openvas systemd[1]: openvas-scanner.service: Failed with result 'exit-code'. Oct 4 11:26:18 openvas systemd[1]: Failed to start OpenVAS Scanner. Oct 4 11:26:19 openvas systemd[1]: openvas-scanner.service: Failed with result 'exit-code'. Oct 4 11:26:19 openvas systemd[1]: Failed to start OpenVAS Scanner. Oct 4 11:26:20 openvas systemd[1]: openvas-scanner.service: Failed with result 'exit-code'. Oct 4 11:26:20 openvas systemd[1]: Failed to start OpenVAS Scanner. Oct 4 11:26:21 openvas systemd[1]: openvas-scanner.service: Failed with result 'exit-code'. Oct 4 11:26:21 openvas systemd[1]: Failed to start OpenVAS Scanner. Oct 4 11:26:15 openvas openvassd[414]: /usr/sbin/openvassd: symbol lookup error: /usr/sbin/openvassd: undefined symbol: nvticache_free Oct 4 11:26:17 openvas openvassd[570]: /usr/sbin/openvassd: symbol lookup error: /usr/sbin/openvassd: undefined symbol: nvticache_free Oct 4 11:26:18 openvas openvassd[617]: /usr/sbin/openvassd: symbol lookup error: /usr/sbin/openvassd: undefined symbol: nvticache_free Oct 4 11:26:19 openvas openvassd[627]: /usr/sbin/openvassd: symbol lookup error: /usr/sbin/openvassd: undefined symbol: nvticache_free Oct 4 11:26:20 openvas openvassd[660]: /usr/sbin/openvassd: symbol lookup error: /usr/sbin/openvassd: undefined symbol: nvticache_free [root@openvas:~]$ rpm -qa | grep openvas openvas-scanner-5.1.1-4.fc27.x86_64 openvas-cli-1.4.5-6.fc28.x86_64 openvas-libraries-9.0.2-3.fc28.x86_64 openvas-manager-7.0.2-4.fc28.x86_64 openvas-gsa-7.0.2-5.fc28.x86_64
Same on Fedora 29: $ rpm -qa | grep openvas openvas-libraries-9.0.2-3.fc29.x86_64 openvas-manager-7.0.2-5.fc29.x86_64 openvas-libraries-devel-9.0.2-3.fc29.x86_64 openvas-cli-1.4.5-7.fc29.x86_64 openvas-scanner-5.1.1-4.fc27.x86_64 openvas-gsa-7.0.2-6.fc29.x86_64 $ /usr/sbin/openvassd /usr/sbin/openvassd: symbol lookup error: /usr/sbin/openvassd: undefined symbol: nvticache_free I noticed the package "openvas-scanner" has "fc27" in the release name, maybe it should be updated?
FWIW, I am getting precisely the same results as Robert and Harald. Linux 4.19.10-300.fc29.x86_64 #1 SMP Mon Dec 17 15:34:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
cool that you update and maintain openvas-libraries but without openvas-scanner for F28 worthless https://koji.fedoraproject.org/koji/buildinfo?buildID=1179047 * Sat Jan 12 2019 josef radinger <cheese> - 9.0.3-1 - bump version - cleanup spec-file - use -delete instead of -exec rm in find
fresh packages are in the making. sorry for the long delay. @harald reindl: libraries are always updated first
could you consider a versioned Requires so that at least non-working upgrades as they now happen are not possible? it's really annoying when things after dist-upgrades just don't work, you need to grab older packages from koji and manually set excludes to avoid breakage everytime "dnf upgrade" is running
the other builds are fine but "openvas-gsa-7.0.3-3.fc28.x86_64" is horrible broken https://openvas.thelounge.net/ https://openvas.thelounge.net/login/ The request contained an unknown or invalid Host header. If you are trying to access GSA via its hostname or a proxy, make sure GSA is set up to allow it. -------------------- https://openvas.thelounge.net/login/login.html this one works works fine so the babble about unknown host header is nonsense and instead should redirct properly as before as i don't want to be treated remember the full url all the time or hope it's in the browser history -------------------- [root@openvas:~]$ rpm -qa | grep openvas openvas-libraries-9.0.3-1.fc28.x86_64 openvas-manager-7.0.3-1.fc28.x86_64 openvas-scanner-5.1.3-1.fc28.x86_64 openvas-gsa-7.0.3-3.fc28.x86_64 openvas-cli-1.4.5-8.fc28.x86_64
oh and after login (gsad main:MESSAGE:2019-01-18 11h21.47 utc:393775: Authentication success for 'root' from **.**.**.**) and redirect to "https://openvas.thelounge.net/omp" the same "The request contained an unknown or invalid Host header. If you are trying to access GSA via its hostname or a proxy, make sure GSA is set up to allow it." nonsense again
Same problem as Robert de Bock on Fedora 29 openvas-scanner package is missing and the only available (openvas-scanner-5.1.1-4.fc27.x86_64) is broken on 29 openvassd: symbol lookup error: openvassd: undefined symbol: nvticache_free
openvas-manager-7.0.3-6.fc28 openvas-gsa-7.0.3-10.fc28 openvas-cli-1.4.5-13.fc28 openvas-scanner-5.1.3-6.fc28 openvas-libraries-9.0.3-6.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2019-7d56145030
openvas-cli-1.4.5-13.fc28, openvas-gsa-7.0.3-10.fc28, openvas-libraries-9.0.3-6.fc28, openvas-manager-7.0.3-6.fc28, openvas-scanner-5.1.3-6.fc28 has been pushed to the Fedora 28 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-7d56145030
openvas-cli-1.4.5-13.fc28, openvas-gsa-7.0.3-10.fc28, openvas-libraries-9.0.3-6.fc28, openvas-manager-7.0.3-6.fc28, openvas-scanner-5.1.3-6.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report.