Bug 26114

Summary:	Cannot use Openvas/GSAD with my mageia 7.1
Product:	Mageia	Reporter:	Nicolas PEYRESAUBES <nicolas>
Component:	RPM Packages	Assignee:	Guillaume Rousse <guillomovitch>
Status:	RESOLVED OLD	QA Contact:
Severity:	critical
Priority:	Normal	CC:	nicolas
Version:	7
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	openvas-manager-7.0.3-1.mga7.src.rpm	CVE:
Status comment:

Description Nicolas PEYRESAUBES 2020-01-21 17:46:19 CET

Description of problem:

After installing all package bellow and following the openvas-check-setup --v9  instruction, I cannot start openvas-manager with the comment systemctl start openvas-manager.service 

[root@rivendell ~]# systemctl status openvas-manager.service
● openvas-manager.service - OpenVAS Manager
   Loaded: loaded (/usr/lib/systemd/system/openvas-manager.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Tue 2020-01-21 16:59:54 CET; 3s ago
  Process: 24456 ExecStart=/usr/sbin/openvasmd $MANAGER_LISTEN $MANAGER_PORT $SCANNER_LISTEN $SCANNER_PORT $MANAGER_OTP (code=exited, status=1/FAILURE)

janv. 21 16:59:54 rivendell systemd[1]: openvas-manager.service: Service RestartSec=1s expired, scheduling restart.
janv. 21 16:59:54 rivendell systemd[1]: openvas-manager.service: Scheduled restart job, restart counter is at 5.
janv. 21 16:59:54 rivendell systemd[1]: Stopped OpenVAS Manager.
janv. 21 16:59:54 rivendell systemd[1]: openvas-manager.service: Start request repeated too quickly.
janv. 21 16:59:54 rivendell systemd[1]: openvas-manager.service: Failed with result 'exit-code'.
janv. 21 16:59:54 rivendell systemd[1]: Failed to start OpenVAS Manager.


During the check process I get the following message when openvasmd is invoqued
"Oops, secure memory pool already initialized"

If launching openvasmd from a prompt shell I also get this message but the process stays in background and I can launch the UI.
Unfortunately when I try to connect  I get the following message

"Login failed. Waiting for OMP service to become available."

Version-Release number of selected component (if applicable):
openvas-cli-1.4.5-2.mga7
openvas-gsa-7.0.3-1.mga7
lib64openvas9-9.0.3-2.mga7
openvas-scanner-5.1.3-1.mga7
openvas-manager-7.0.3-1.mga7
openvas-libraries-9.0.3-2.mga7


How reproducible:
Starting from a clean install I still have same result



Steps to Reproduce:
1.urpmi all openvas package
2.run "openvas-check-setup --v9" and follow instruction step by step
3.still the same issue on Mageia 7.1 (tested on different installs) but natively working on a debian 10

Comment 1 Lewis Smith 2020-01-21 21:45:38 CET

All the packages listed are SRPMs in their own right, so I do not know which to put in the bug heading; guess.
They are all in the hands of guillomovitch, so assigning the bug to you.

Source RPM: (none) => openvas-manager-7.0.3-1.mga7.src.rpm
Assignee: bugsquad => guillomovitch

Comment 2 Nicolas PEYRESAUBES 2020-01-21 22:31:40 CET

To me the problem seems to come from openvas-manager ... the Oops  occurs when openvasmd is invoqued

Nicolas PEYRESAUBES 2020-01-21 22:32:21 CET

CC: (none) => nicolas

Comment 3 Aurelien Oudelet 2021-07-06 13:17:00 CEST

Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.

Comment 4 Marja Van Waes 2021-09-07 14:11:28 CEST

Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

Resolution: (none) => OLD
Status: NEW => RESOLVED