Re: [Openvas-discuss] [openvas-9] "Login failed. Waiting for OMP service to become available."

2016-12-28 Thread Christian Fischer
Hi, On 28.12.2016 13:37, Ralf Hildebrandt wrote: >> root 1673 0.2 0.4 627192 17144 ?Sl 12:52 0:01 >> /usr/sbin/gsad --do-chroot >> --ssl-private-key=/var/lib/openvas/private/CA/serverkey.pem.new >> --ssl-certificate=/var/lib/openvas/CA/servercert.pem.new --no-redirect >>

Re: [Openvas-discuss] [openvas-9] "Login failed. Waiting for OMP service to become available."

2016-12-28 Thread Ralf Hildebrandt
> root 1673 0.2 0.4 627192 17144 ?Sl 12:52 0:01 > /usr/sbin/gsad --do-chroot > --ssl-private-key=/var/lib/openvas/private/CA/serverkey.pem.new > --ssl-certificate=/var/lib/openvas/CA/servercert.pem.new --no-redirect > --port=443 --do-chroot was the culprit here. It *used*

[Openvas-discuss] [openvas-9] "Login failed. Waiting for OMP service to become available."

2016-12-28 Thread Ralf Hildebrandt
After upgrading my openvas-9 installation using the mrazavi packages, I was encountering quite a few issues. I had to use: % openvasmd --migrate Then I updated all the feeds, just to be on the safe side. Then "openvassd" would not start. I traced it down to some issue with the data fetched from