Hi,
  I've been using the OpenVAS 6.0 v1 demo image. Recently, I ran the
virtual disk out of space somehow. It seems that under /usr/local/var
there was almost 3.6 gigs worth of files.

So, I
  #1: shut the machine down,
  #2: made and attached a new disk,
  #3: rebooted to runlevel 1 (shutting down basically everything),
  #4: partitioned the disk and added some more swap space as well
while I was at it,
  #5: formatted the partitions,
  #6: moved /usr/local/var to /usr/local/varold,
  #7: mounted the new disk (40gb) @ /usr/local/var,
  #8: moved all the files back over,
  #9: fixed the group (root:staff rather than root:root),
  #10: added the new space to /etc/fstab, and
  #11: rebooted.

Everything runs, but scans no longer work. There are no remote, or
"slave" scanners. Just the one running off the image. All scans that I
have tried to restart, or start fresh are stuck at 1%. In
/usr/local/var/log/openvassd.messages, I have a constant stream of
"[Tue Nov 26 21:33:18 2013][9650] Communication closed by client".
openvassd.dump is there, but is 0 size due to the original image
running out of disk. In openvasdm.log, I see
"lib  serv:WARNING:2013-11-26 15h45.33 UTC:3169:    Failed to
gnutls_bye: Error in the push function.
base gpgme:MESSAGE:2013-11-26 15h45.35 UTC:3185: Setting GnuPG homedir
to '/usr/local/etc/openvas/gnupg'".

What did I do wrong?

How do I recover?

--
W. Scott Lockwood III
AMST Tech (SPI)
GWB2009033817
http://www.shadowplayinternational.org/
"There are four boxes to be used in defense of liberty:  soap, ballot,
jury, and ammo. Please use in that order." -Ed Howdershelt (Author)
_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to