post/install-gvm10-psql-beta1/

[utterances-bot]

Install Greenbone Vulnerability Manager 10-beta1 with Postgresql on Ubuntu 18.04 to test is out... · sadsloth.net

https://sadsloth.net/post/install-gvm10-psql-beta1/

[tsanchez88]

Thanks for this write up, I used the beta2 files with this process, a couple issues I ran into and wanted to post about for others...

1. Install Requirements - I believe the coma in the list of packages causes the command to fail, just remove it and it worked for me (postgresql-contrib,)
2. Fix redis for default openvas install - I found the answer to this in one or your other write ups, it should be: openvas/openvassd.conf = db_address = /var/run/redis/redis-server.sock The "kb" option no longer appears to work.

[falkowich]

Hi,

I haven't fixed this for b2 yet. But with I will update the "howto" with your fixes asap.

And thanks for the comments and time to write back the fixes!

-- Regards Falk

[mafli77]

Hi Falk,

your tutorial is great!

I just needed to add the following two lines at the start in order to find all packages:

echo "deb http://archive.ubuntu.com/ubuntu xenial-updates main restricted universe multiverse" >> /etc/apt/sources.list

apt update

Best

Matthias

[mafli77]

I still have a problem getting the system up and running. It seems that the Redis server won't work as expected.

cat /usr/local/etc/openvas/openvassd.conf

openvas/openvassd.conf = db_address = /var/run/redis/redis-server.sock

cat /usr/local/var/log/gvm/openvassd.log:

lib kb:CRITICAL:2019-03-23 20h22.06 utc:979: get_redis_ctx: redis connection error: No such file or directory lib kb:CRITICAL:2019-03-23 20h22.06 utc:979: redis_new: cannot access redis at '/tmp/redis.sock' lib kb:CRITICAL:2019-03-23 20h22.06 utc:979: get_redis_ctx: redis connection error: No such file or directory

cat /etc/redis/redis.conf:

unixsocket /var/run/redis/redis-server.sock unixsocketperm 700

systemctl status redis

● redis-server.service - Advanced key-value store Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled) Active: active (running) since Sat 2019-03-23 21:55:52 UTC; 13min ago Docs: http://redis.io/documentation, man:redis-server(1) Process: 37114 ExecStop=/bin/kill -s TERM $MAINPID (code=exited, status=0/SUCCESS) Process: 37119 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=0/SUCCESS) Main PID: 37120 (redis-server) Tasks: 4 (limit: 2915) CGroup: /system.slice/redis-server.service └─37120 /usr/bin/redis-server 127.0.0.1:0

Mar 23 21:55:52 localhost redis-server[37119]: 37119:C 23 Mar 21:55:52.626 # Configuration loaded Mar 23 21:55:52 localhost redis-server[37119]: oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo Mar 23 21:55:52 localhost redis-server[37119]: Redis version=4.0.9, bits=64, commit=00000000, modified=0, pid=37119, just started Mar 23 21:55:52 localhost redis-server[37119]: Configuration loaded Mar 23 21:55:52 localhost systemd[1]: redis-server.service: Can't open PID file /var/run/redis/redis-server.pid (yet?) after start: No such file or directory Mar 23 21:55:52 localhost redis[37120]:

I really wonder why gvm still tries to access redis at /tmp/redis.sock although the settings in openvassd.conf are different.

Do you have any idea?

Thank you for your help!

Best

Matthias

[falkowich]

I still have a problem getting the system up and running. It seems that the Redis server won't work as expected.

cat /usr/local/etc/openvas/openvassd.conf

openvas/openvassd.conf = db_address = /var/run/redis/redis-server.sock

cat /usr/local/var/log/gvm/openvassd.log:

lib kb:CRITICAL:2019-03-23 20h22.06 utc:979: get_redis_ctx: redis connection error: No such file or directory lib kb:CRITICAL:2019-03-23 20h22.06 utc:979: redis_new: cannot access redis at '/tmp/redis.sock' lib kb:CRITICAL:2019-03-23 20h22.06 utc:979: get_redis_ctx: redis connection error: No such file or directory

cat /etc/redis/redis.conf:

unixsocket /var/run/redis/redis-server.sock unixsocketperm 700

Ouch,

I think that it is a typo by me, really sry m8!

cat << EOF > /usr/local/etc/openvas/openvassd.conf db_address = /var/run/redis/redis-server.sock EOF

It should only be db_address = /var/run/redis/redis-server.sock.

And thanks, I'll fix it asap in the writeup

-- Regards Falk

[mafli77]

Hey Falk,

Thank you for your early reply!

Having the settings fixed the openvassd starts up perfectly! Thanks!

However, I still cannot login on the website - getting the error "GMP Service is down".

cat /usr/local/var/log/gvm/gvmd.log: md main:MESSAGE:2019-03-24 19h07.43 utc:897: Greenbone Vulnerability Manager version 8.0+beta2 (DB revision 200) md manage:WARNING:2019-03-24 19h07.43 utc:898: manage_create_sql_functions: PostgreSQL extension uuid-ossp required md manage:WARNING:2019-03-24 19h07.43 utc:898: init_manage_process: failed to create functions

But PostgreSQL says: "ERROR: extension "uuid-ossp" already exists" ... when I try to re-run the SQLscript.

Do you have any ideas?

Thank you for your help!

Best

Matthias

[mafli77]

Now it works perfectly! Many Thanks!