Home
My Page
Projects
OpenVAS

[#1326] missing feaddback whether deamon is startet

Date:
2010-03-16 09:27
Priority:
3
State:
Open
Submitted by:
Hartmut Goebel (htgoebel)
Assigned to:
Nobody (None)
Architecture:
None
Product:
OpenVAS
Operating System:
All
Component:
None
Version:
3.0.0
Severity:
major
Resolution:
None
Hardware:
All
URL:
 
Summary:
missing feaddback whether deamon is startet

Detailed description
openvasad does not give feedback whether started successfully.

openvasmd does not give feedback whether started successfully.

gasd does not give feedback whether started successfully.



This is very annoying since one can not seen if the server started successfully or simply failed starting.



When starting openvas-scanner, if counts the plugins. okay.

Followup

Message
Date: 2010-03-30 16:54
Sender: Hartmut Goebel

I just got bugged by another annoyance here: I has some
certificate issues, but the the scanners error message did
only show up when running

openvassd --port 9391 --foreground
...
[7435] failed to verify certificate: The peer certificate is
invalid
[7435] failed to verify certificate: The peer certificate
was signed using an insecure algorithm

It will not be logged into openvassd.dump nor into
openvassd.messages.
Date: 2010-03-16 10:48
Sender: Felix Wolfsteller

I have a patch for optional syslog logging here, but could not test properly yet. If we are lucky, get accepted for gsoc and a student wants to do it, we could allow the user to use syslog with the newer daemons (manager, administrator, gsad).
Date: 2010-03-16 10:30
Sender: Hartmut Goebel

IMHO:
- the default logging config should display startup and stop messages.
- when running in foreground, status messages should be send to stderr.

This is the behavior many other daemons have.

(I personally am not used to configure logging in some config files. This is rarely used since most daemons (in my experience) use syslog).
Date: 2010-03-16 10:04
Sender: Felix Wolfsteller

The idea was that none of the daemons uses stdout and stderr (much like other "system" daemons).

Thus, reporting only log-files is intentional (not a "bug" as such). You can change this behavior by fiddling with the log-config files.

However, many people are annoyed by that. Especially, if started in foreground (-f) or verbose it is unclear if status messages are expected or not.

Personally, I am undecided.

Btw, also openvas-scanner might not be started even if you saw the list of loaded plugins.


This bug is related to bug https://bugs.openvas.org/1327 .

Attached Files:

Changes:

No Changes Have Been Made to This Item


This site is hosted by Intevation GmbH