I’m installing from source, following my notes last time I successfully installed it (2016). Now when I run the
openvas-check-setup --v9, I get:
Step 1: Checking OpenVAS Scanner …
OK: OpenVAS Scanner is present in version 5.1.3.
OK: redis-server is present in version v=3.2.6.
OK: scanner (kb_location setting) is configured properly using the redis-server socket: /tmp/redis.sock
ERROR: redis-server is not running or not listening on socket: /tmp/redis.sock
FIX: You should start the redis-server or configure it to listen on socket: /tmp/redis.sock
but, when I look at my REDIS-SERVER log, it shows:
1356:M 31 Oct 12:58:28.696 # Server started, Redis version 3.2.6
1356:M 31 Oct 12:58:28.696 * DB loaded from disk: 0.000 seconds
1356:M 31 Oct 12:58:28.696 * The server is now ready to accept connections on port 6379
1356:M 31 Oct 12:58:28.696 * The server is now ready to accept connections at /tmp/redis.sock
when I search for the redis.sock file, I get:
/tmp/systemd-private-9bca8c6759544f0bb634fdd9c0aa7d5f-redis-server.service-jCGzmj/tmp/redis.sock
System = Debian 9.5
Installing from Software.
What’s that causes that odd directory structure in the /tmp folder?