Re: [Openvas-discuss] openvasmd don't start after upgrade

[Reindl Harald]

my god come on - is it really so hard to automatically migrate existing 
installs at startup?


ERROR: Your OpenVAS certificate infrastructure did NOT pass validation.
FIX: Run 'openvas-manage-certs -a'.
ERROR: Your OpenVAS-9 installation is not yet complete!

[root@openvas:/var/log/openvas]$ openvas-manage-certs -a
ERROR: certtool binary not found!

Am 30.10.2017 um 14:39 schrieb Reindl Harald:



Am 30.10.2017 um 14:34 schrieb Brandon Perry:
On Oct 30, 2017, at 8:18 AM, Reindl Harald  
wrote:


Am 30.10.2017 um 14:03 schrieb Reindl Harald:

openvas-libraries-9.0.1-1.fc26.x86_64
openvas-manager-7.0.2-1.fc26.x86_64
openvas-cli-1.4.5-3.fc26.x86_64
openvas-gsa-7.0.2-2.fc26.x86_64
openvas-scanner-5.1.1-1.fc26.x86_64
it's not terrible helpful when a process exits with a error code and 
no message at all

[root@openvas:/etc/sysconfig]$ openvasmd
[root@openvas:/etc/sysconfig]$ openvasmd -f


ERROR: Database schema is out of date.
FIX: Run 'openvasmd —migrate'


You could try —rebuild is well


it could just create diretories below /var/lib as any other software

base gpgme:MESSAGE:2017-10-30 13h20.38 utc:2079: Setting GnuPG dir to 
'/var/lib/openvas/openvasmd/gnupg'
base gpgme:WARNING:2017-10-30 13h20.38 utc:2079: Setting GnuPG dir 
failed: No such file or directory
md  crypt:CRITICAL:2017-10-30 13h20.38 utc:2079: lsc_crypt_new: can't 
continue w/o a gpgme context
md   main:MESSAGE:2017-10-30 13h20.58 utc:2148:    OpenVAS Manager 
version 7.0.2 (DB revision 184)

md   main:   INFO:2017-10-30 13h20.58 utc:2148:    Migrating database.
md   main:   INFO:2017-10-30 13h20.58 utc:2148:    Migrating to 159

___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] openvasmd don't start after upgrade

[Reindl Harald]

Am 30.10.2017 um 14:34 schrieb Brandon Perry:

On Oct 30, 2017, at 8:18 AM, Reindl Harald  wrote:

Am 30.10.2017 um 14:03 schrieb Reindl Harald:

openvas-libraries-9.0.1-1.fc26.x86_64
openvas-manager-7.0.2-1.fc26.x86_64
openvas-cli-1.4.5-3.fc26.x86_64
openvas-gsa-7.0.2-2.fc26.x86_64
openvas-scanner-5.1.1-1.fc26.x86_64
it's not terrible helpful when a process exits with a error code and no message 
at all
[root@openvas:/etc/sysconfig]$ openvasmd
[root@openvas:/etc/sysconfig]$ openvasmd -f


ERROR: Database schema is out of date.
FIX: Run 'openvasmd —migrate'


You could try —rebuild is well


it could just create diretories below /var/lib as any other software

base gpgme:MESSAGE:2017-10-30 13h20.38 utc:2079: Setting GnuPG dir to 
'/var/lib/openvas/openvasmd/gnupg'
base gpgme:WARNING:2017-10-30 13h20.38 utc:2079: Setting GnuPG dir 
failed: No such file or directory
md  crypt:CRITICAL:2017-10-30 13h20.38 utc:2079: lsc_crypt_new: can't 
continue w/o a gpgme context
md   main:MESSAGE:2017-10-30 13h20.58 utc:2148:OpenVAS Manager 
version 7.0.2 (DB revision 184)

md   main:   INFO:2017-10-30 13h20.58 utc:2148:Migrating database.
md   main:   INFO:2017-10-30 13h20.58 utc:2148:Migrating to 159
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] openvasmd don't start after upgrade

[Brandon Perry]

> On Oct 30, 2017, at 8:18 AM, Reindl Harald  wrote:
> 
> 
> 
> Am 30.10.2017 um 14:03 schrieb Reindl Harald:
>> openvas-libraries-9.0.1-1.fc26.x86_64
>> openvas-manager-7.0.2-1.fc26.x86_64
>> openvas-cli-1.4.5-3.fc26.x86_64
>> openvas-gsa-7.0.2-2.fc26.x86_64
>> openvas-scanner-5.1.1-1.fc26.x86_64
>> it's not terrible helpful when a process exits with a error code and no 
>> message at all
>> [root@openvas:/etc/sysconfig]$ openvasmd
>> [root@openvas:/etc/sysconfig]$ openvasmd -f
> 
> ERROR: Database schema is out of date.
> FIX: Run 'openvasmd —migrate'

You could try —rebuild is well.

> 
> yeah if it would do something
> 
> [root@openvas:~]$ openvasmd --migrate
> [root@openvas:~]$ openvas-check-setup --v9
> openvas-check-setup 2.3.7
>  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: redis-server is present in version v=3.2.11.
>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 55675 NVTs.
>OK: Signature checking of NVTs is enabled in OpenVAS Scanner.
>OK: The NVT cache in /var/cache/openvas contains 56315 files for 55675 
> NVTs.
> Step 2: Checking OpenVAS Manager ...
>OK: OpenVAS Manager is present in version 7.0.2.
>OK: OpenVAS Manager database found in /var/lib/openvas/mgr/tasks.db.
>OK: Access rights for the OpenVAS Manager database are correct.
>OK: sqlite3 found, extended checks of the OpenVAS Manager installation 
> enabled.
>OK: OpenVAS Manager database is at revision 158.
>OK: OpenVAS Manager expects database at revision 184.
>ERROR: Database schema is out of date.
>FIX: Run 'openvasmd --migrate'.
> 
>> [root@openvas:/etc/sysconfig]$ systemctl status openvas-manager.service
>> ? openvas-manager.service - OpenVAS Manager
>>Loaded: loaded (/etc/systemd/system/openvas-manager.service; enabled; 
>> vendor preset: disabled)
>>Active: failed (Result: exit-code) since Mon 2017-10-30 14:00:06 CET; 
>> 2min 3s ago
>>   Process: 1339 ExecStart=/usr/sbin/openvasmd -f $MANAGER_LISTEN 
>> $MANAGER_PORT $SCANNER_LISTEN $SCANNER_PORT $MANAGER_OTP (code=exited, 
>> status=1/FAILURE)
>>  Main PID: 1339 (code=exited, status=1/FAILURE)
>> Okt 30 14:00:04 openvas.thelounge.net systemd[1]: openvas-manager.service: 
>> Failed with result 'exit-code'.
>> Okt 30 14:00:06 openvas.thelounge.net systemd[1]: openvas-manager.service: 
>> Service hold-off time over, scheduling restart.
>> Okt 30 14:00:06 openvas.thelounge.net systemd[1]: Stopped OpenVAS Manager.
>> Okt 30 14:00:06 openvas.thelounge.net systemd[1]: openvas-manager.service: 
>> Start request repeated too quickly.
>> Okt 30 14:00:06 openvas.thelounge.net systemd[1]: Failed to start OpenVAS 
>> Manager.
>> Okt 30 14:00:06 openvas.thelounge.net systemd[1]: openvas-manager.service: 
>> Unit entered failed state.
>> Okt 30 14:00:06 openvas.thelounge.net systemd[1]: openvas-manager.service: 
>> Failed with result 'exit-code'.
>> [root@openvas:/etc/sysconfig]$
> ___
> Openvas-discuss mailing list
> Openvas-discuss@wald.intevation.org
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss



signature.asc
Description: Message signed with OpenPGP
___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Re: [Openvas-discuss] openvasmd don't start after upgrade

[Reindl Harald]

Am 30.10.2017 um 14:03 schrieb Reindl Harald:

openvas-libraries-9.0.1-1.fc26.x86_64
openvas-manager-7.0.2-1.fc26.x86_64
openvas-cli-1.4.5-3.fc26.x86_64
openvas-gsa-7.0.2-2.fc26.x86_64
openvas-scanner-5.1.1-1.fc26.x86_64

it's not terrible helpful when a process exits with a error code and no 
message at all


[root@openvas:/etc/sysconfig]$ openvasmd

[root@openvas:/etc/sysconfig]$ openvasmd -f


ERROR: Database schema is out of date.
FIX: Run 'openvasmd --migrate'

yeah if it would do something

[root@openvas:~]$ openvasmd --migrate
[root@openvas:~]$ openvas-check-setup --v9
openvas-check-setup 2.3.7
  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: redis-server is present in version v=3.2.11.
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 55675 NVTs.
OK: Signature checking of NVTs is enabled in OpenVAS Scanner.
OK: The NVT cache in /var/cache/openvas contains 56315 files 
for 55675 NVTs.

Step 2: Checking OpenVAS Manager ...
OK: OpenVAS Manager is present in version 7.0.2.
OK: OpenVAS Manager database found in 
/var/lib/openvas/mgr/tasks.db.

OK: Access rights for the OpenVAS Manager database are correct.
OK: sqlite3 found, extended checks of the OpenVAS Manager 
installation enabled.

OK: OpenVAS Manager database is at revision 158.
OK: OpenVAS Manager expects database at revision 184.
ERROR: Database schema is out of date.
FIX: Run 'openvasmd --migrate'.


[root@openvas:/etc/sysconfig]$ systemctl status openvas-manager.service
? openvas-manager.service - OpenVAS Manager
    Loaded: loaded (/etc/systemd/system/openvas-manager.service; 
enabled; vendor preset: disabled)
    Active: failed (Result: exit-code) since Mon 2017-10-30 14:00:06 
CET; 2min 3s ago
   Process: 1339 ExecStart=/usr/sbin/openvasmd -f $MANAGER_LISTEN 
$MANAGER_PORT $SCANNER_LISTEN $SCANNER_PORT $MANAGER_OTP (code=exited, 
status=1/FAILURE)

  Main PID: 1339 (code=exited, status=1/FAILURE)

Okt 30 14:00:04 openvas.thelounge.net systemd[1]: 
openvas-manager.service: Failed with result 'exit-code'.
Okt 30 14:00:06 openvas.thelounge.net systemd[1]: 
openvas-manager.service: Service hold-off time over, scheduling restart.

Okt 30 14:00:06 openvas.thelounge.net systemd[1]: Stopped OpenVAS Manager.
Okt 30 14:00:06 openvas.thelounge.net systemd[1]: 
openvas-manager.service: Start request repeated too quickly.
Okt 30 14:00:06 openvas.thelounge.net systemd[1]: Failed to start 
OpenVAS Manager.
Okt 30 14:00:06 openvas.thelounge.net systemd[1]: 
openvas-manager.service: Unit entered failed state.
Okt 30 14:00:06 openvas.thelounge.net systemd[1]: 
openvas-manager.service: Failed with result 'exit-code'.

[root@openvas:/etc/sysconfig]$

___
Openvas-discuss mailing list
Openvas-discuss@wald.intevation.org
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss