Right you are, bad habit!
//Henrik

On Thu, Dec 17, 2015 at 2:30 PM, Reindl Harald <[email protected]>
wrote:

>
>
> Am 17.12.2015 um 14:27 schrieb Henrik Cederlöf:
>
>> tried it that way , first killing off the processes, but when I get to
>> starting the gsad service it has already started automatically
>>
>
> don't kill random processes, that leads in failed status for the service
> and may trigger a restart depeding on the systemd unit
>
> the days where the service manager had no clue are gone!
>
> systemctl stop service1 service2 service3
> systemctl start service1 service2 service3
>
> On Thu, Dec 17, 2015 at 1:55 PM, René Behring <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>     Do you only restarted the Manager?
>>     Restart the Scanner and wait until the NVTs are loaded, after that
>>     the Manager and then the gsad.
>>
>>     Am 17.12.2015 13:40 schrieb "Henrik Cederlöf"
>>     <[email protected] <mailto:[email protected]>>:
>>
>>         I have installed:
>>
>>         CentOS Linux release 7.2.1511 (Core)
>>
>>         openvas 8
>>
>>         and it all worked using the instructions below and I could do my
>>         first scans.
>>
>>         Then after some days updates of packages and installed
>>         applications I cannot run openvas anymore.
>>
>>         The management GUI works and I can add hosts etc but when
>>         starting a scan either via gui or similar via command line it
>>         fails with error 503.
>>
>>         openvas-check-setup
>>
>>         gives:
>>
>>         It seems like your OpenVAS-8 installation is OK.
>>
>>         but in openvasmd.log i find:
>>
>>         client: <start_task_response status='503' status_text='Service
>>         temporarily down'/>
>>
>>         Failed to shake hands with peer: The TLS connection was
>>         non-properly terminated.
>>
>>         i have tried:
>>
>>         openvas-mkcert -f -q
>>
>>         openvas-mkcert-client -n -i
>>
>>         then stopped openvasmd
>>
>>         openvasmd --rebuild
>>
>>         and then restarted openvas using:
>>
>>         /openvasmd -p 9390 -a 0.0.0.0/
>>
>>
>>         but with the same result.
>>
>>         Please, any ideas are welcome!
>>
>>         I have read that
>>
>>         "this is a bug in GnuTLS 3.3.8 that is fixed in 3.3.10"
>>
>>         I am using 3.3.8 but I cannot find a version 3.3.10 for Centos.
>>
>>
>>
>>         ----------------------
>>
>>         Installation instruction:
>>
>>         1) Disable SELINUX.
>>         Edit /etc/selinux/config, save and reboot
>>         2) Add required packages
>>         yum install wget bzip2 texlive net-tools alien
>>         3) Add Atomicorp repo
>>         wget -q -O - http://www.atomicorp.com/installers/atomic | sh
>>         4) Install OpenVAS
>>         yum install openvas
>>         5) edit /etc/redis.conf. Add/uncomment the following
>>         unixsocket /tmp/redis.sock
>>         unixsocketperm 700
>>         6) Restart Redis
>>         systemctl enable redis && systemctl restart redis
>>         7) openvas-setup
>>         follow instructions. If rsync throws error, check that your
>>         network allows outgoing TCP 873 to internet
>>         8 ) To access OV-8 from network, either disable firewall or add
>>         exception for tcp 9392
>>         firewall-cmd --permanent --zone=public --add-port=9392/tcp
>>         firewall-cmd --reload
>>
>
>
> _______________________________________________
> Openvas-discuss mailing list
> [email protected]
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
>
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to