Closed rmarathay-zz closed 5 years ago
Hi @rmarathay are you navigating to it on 443 as https? https://localhost?
Hi @mikesplain, thank you for reaching out. I have tried https and http on port 443 and 9390 with no luck.
@rmarathay Can you post the logs for the container? It can take some time to startup. Also what size droplet are you running?
Log file:
postmap: warning: /etc/postfix/sasl_passwd, line 1: record is in "key: value" format; is this an alias file?
* Stopping Postfix Mail Transport Agent postfix
...done.
* Starting Postfix Mail Transport Agent postfix
...done.
Tailing logs
==> /var/log/openvas/gsad.log <==
gsad main:MESSAGE:2018-07-31 20h30.21 utc:916: Starting GSAD version 7.0.3
gsad main:MESSAGE:2018-07-31 20h30.21 utc:916: main: Locale for gettext extensions set to "C", gettext translations are disabled.
gsad xslt:WARNING:2018-07-31 20h30.21 utc:916: init_language_lists: Failed to open locale directory "/usr/share/openvas/gsa/locale": No such file or directory
gsad main:MESSAGE:2018-08-02 15h23.21 utc:43: Starting GSAD version 7.0.3
gsad main:MESSAGE:2018-08-02 15h23.21 utc:43: main: Locale for gettext extensions set to "C", gettext translations are disabled.
gsad xslt:WARNING:2018-08-02 15h23.21 utc:43: init_language_lists: Failed to open locale directory "/usr/share/openvas/gsa/locale": No such file or directory
==> /var/log/openvas/openvasmd.log <==
md main:MESSAGE:2018-08-02 15h23.21 utc:45: OpenVAS Manager version 7.0.3 (DB revision 184)
md main: INFO:2018-08-02 15h23.21 utc:45: rebuild_nvt_cache_retry: Reloading NVT cache
md main: INFO:2018-08-02 15h23.21 utc:47: update_or_rebuild_nvt_cache: Rebuilding NVT cache
base gpgme:MESSAGE:2018-08-02 15h23.24 utc:35: Setting GnuPG dir to '/var/lib/openvas/openvasmd/gnupg'
base gpgme:MESSAGE:2018-08-02 15h23.28 utc:35: Using OpenPGP engine version '2.1.11'
base gpgme:MESSAGE:2018-08-02 15h23.29 utc:47: Setting GnuPG dir to '/var/lib/openvas/openvasmd/gnupg'
base gpgme:MESSAGE:2018-08-02 15h23.32 utc:47: Using OpenPGP engine version '2.1.11'
md main: INFO:2018-08-02 15h23.34 utc:47: Updating NVT cache.
md main:MESSAGE:2018-08-02 15h26.36 utc:153: OpenVAS Manager version 7.0.3 (DB revision 184)
md manage: INFO:2018-08-02 15h26.36 utc:153: Getting users.
==> /var/log/openvas/openvassd.dump <==
==> /var/log/openvas/openvassd.messages <==
[Tue Jul 31 20:39:46 2018][897] openvassd 5.1.2 started
[Tue Jul 31 20:42:14 2018][1370] Client not present
[Tue Jul 31 20:42:17 2018][897] Received the Terminated signal
[Thu Aug 2 15:23:27 2018][24] openvassd 5.1.2 started
[Thu Aug 2 15:26:35 2018][80] Client not present```
Droplet Size:
@mikesplain Please let me know if that is an acceptable droplet size. Also, based on the log message, what are your thoughts?
When I run the same size Droplet, I have no problems
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 30 days if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had recent activity. Issue creator may reopen if the issue still exists. Thank you for your contributions.
I've followed the instructions in the README. The docker image works correctly on my local machine, however when I try to do the same to my digitalocean droplet, I run into issues. I've run what is on the README as well as run:443, nothing is returned. I feel like I'm missing something rather obvious.
docker run -p 443:443 -p 9390:9390 -e PUBLIC_HOSTNAME=<my ip address> --name openvas mikesplain/openvas
and it seems to start the container but when I navigate to