Lance, What does the status say? sudo systemctl -l status openvas-scanner.service
How about for the redis service as well? sudo systemctl -l status redis.service What does the redis config look like? sudo grep -vE '^.*#|^;|^$' /etc/redis.conf From: Openvas-discuss <openvas-discuss-boun...@wald.intevation.org> On Behalf Of Lance M. Caven Sent: Thursday, July 5, 2018 14:35 PM To: openvas-discuss@wald.intevation.org Subject: [Openvas-discuss] When I run sudo systemctl start openvas-scanner - the system times out When I run sudo systemctl start openvas-scanner - the system times out Job for openvas-scanner.service failed because a timeout was exceeded. See "systemctl status openvas-scanner.service" and "journalctl -xe" for details. The system worked on Ubuntu 18.04 on two days ago when I installed it. I rebooted the computer and did run an apt update and upgrade on the instance. Since that time I have not been able to get the Openvas-scanner to start. I found and attempted to follow this advice from Christian Fische - I do not have items 1 or 2 in my configuration. "most likely the known issue where redis is blocking any access by the scanner due to unknown reasons. This should do the trick: 1. Delete dump.rdb (somewhere in /var/run/redis or similar) 2. Comment out/remove all "save xy z" (e.g. save 900 1) from your redis.conf 3. restart redis 4. restart scanner and try again Regards, Christian Fische" I have an openvassd.dump file and it contains (openvassd:99392): lib kb_redis-CRITICAL **: 11:48:42.038: redis_new: cannot access redis at '/var/run/redis/redis.sock' (openvassd:99413): lib kb_redis-CRITICAL **: 11:48:42.038: get_redis_ctx: redis connection error: No such file or directory (openvassd:99403): lib kb_redis-CRITICAL **: 11:48:42.038: get_redis_ctx: redis connection error: No such file or directory (openvassd:99393): lib kb_redis-CRITICAL **: 11:48:42.038: redis_new: cannot access redis at '/var/run/redis/redis.sock' (openvassd:99390): lib kb_redis-CRITICAL **: 11:48:42.038: redis_new: cannot access redis at '/var/run/redis/redis.sock' but in the redis log file it indicates 51575:M 05 Jul 12:53:46.255 # WARNING: The TCP backlog setting of 511 cannot be enforced because /proc/sys/net/core/somaxconn is set to the lower value of 128. 51575:M 05 Jul 12:53:46.255 # Server initialized 51575:M 05 Jul 12:53:46.255 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect. 51575:M 05 Jul 12:53:46.255 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain the setting after a reboot. Redis must be restarted after THP is disabled. 51575:M 05 Jul 12:53:46.661 * DB loaded from disk: 0.406 seconds 51575:M 05 Jul 12:53:46.661 * Ready to accept connections 51575:M 05 Jul 12:53:46.661 * The server is now ready to accept connections at /var/run/redis/redis.sock
_______________________________________________ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
