Bug 1475180

fixed by running openvas-check-setup --v9

rodomonte@rod:~/Documents/openvas/OpenVas-Management-Scripts$ service openvas-manager status
Redirecting to /bin/systemctl status  openvas-manager.service
● openvas-manager.service - OpenVAS Manager
   Loaded: loaded (/usr/lib/systemd/system/openvas-manager.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2017-12-06 11:22:30 CET; 9h ago
  Process: 29751 ExecStart=/usr/sbin/openvasmd $OPTIONS (code=exited, status=0/SUCCESS)
 Main PID: 29752 (openvasmd)
    Tasks: 1 (limit: 4915)
   CGroup: /system.slice/openvas-manager.service
           └─29752 openvasmd

Dec 06 11:22:30 rod systemd[1]: Starting OpenVAS Manager...
Dec 06 11:22:30 rod systemd[1]: Started OpenVAS Manager.
rodomonte@rod:~/Documents/openvas/OpenVas-Management-Scripts$ sudo ./openvas-check-setup --v9
openvas-check-setup 2.3.3
  Test completeness and readiness of OpenVAS-9

  Please report us any non-detected problems and
  help us to improve this check routine:
  http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss

  Send us the log-file (/tmp/openvas-check-setup.log) to help analyze the problem.

  Use the parameter --server to skip checks for client tools
  like GSD and OpenVAS-CLI.

Step 1: Checking OpenVAS Scanner ... 
        OK: OpenVAS Scanner is present in version 5.1.1.
        OK: OpenVAS Scanner CA Certificate is present as /var/lib/openvas/CA/cacert.pem.
        OK: OpenVAS Scanner server certificate is valid and present as /var/lib/openvas/CA/servercert.pem.
        OK: redis-server is present in version v=4.0.2.
        OK: scanner (kb_location setting) is configured properly using the redis-server socket: /tmp/redis.sock
        OK: redis-server is running and listening on socket: /tmp/redis.sock.
        OK: redis-server configuration is OK and redis-server is running.
        OK: NVT collection in /var/lib/openvas/plugins contains 56694 NVTs.
        WARNING: Signature checking of NVTs is not enabled in OpenVAS Scanner.
        SUGGEST: Enable signature checking (see http://www.openvas.org/trusted-nvts.html).
        OK: The NVT cache in /var/cache/openvas contains 56695 files for 56694 NVTs.
Step 2: Checking OpenVAS Manager ... 
        ERROR: OpenVAS Manager too old or too new: 7.0.2
        FIX: Please install OpenVAS Manager 6.1.

 ERROR: Your OpenVAS-9 installation is not yet complete!

Please follow the instructions marked with FIX above and run this
script again.

If you think this result is wrong, please report your observation
and help us to improve this check routine:
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
Please attach the log-file (/tmp/openvas-check-setup.log) to help us analyze the problem.

rodomonte@rod:~/Documents/openvas/OpenVas-Management-Scripts$ uname -a
Linux rod 4.8.6-300.fc25.x86_64 #1 SMP Tue Nov 1 12:36:38 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux


doesnt seems true to me.

also it used to works before, and on system startup it cant start (it say something like, starting service, stopping service 4-5 times), i attach the /tmp/openvas-check-setup.log here: http://sprunge.us/NTbQ

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.