and what is output that -xe command and output to logs? ma 9. heinäk. 2018 klo 20.18 Lance M. Caven <lance...@gmail.com> kirjoitti:
> I commented these out, the three lines with save are no longer there. > > The same issue continues > sudo service openvas-scanner start > Job for openvas-scanner.service failed because a timeout was exceeded. > See "systemctl status openvas-scanner.service" and "journalctl -xe" for > details. > > On Sat, Jul 7, 2018 at 2:57 AM Christian Fischer < > christian.fisc...@greenbone.net> wrote: > >> Hi, >> >> > What does the redis config look like? >> > sudo grep -vE '^.*#|^;|^$' /etc/redis.conf >> *snip* >> > save 900 1 >> > save 300 10 >> > save 60 10000 >> >> which effectively means that those are not commented out or removed as >> initial assumed: >> >> > 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 >> >> Regards, >> On 06.07.2018 15:58, Lance M. Caven wrote: >> > Lance, >> > >> > What does the status say? >> > sudo systemctl -l status openvas-scanner.service >> > >> > openvas-scanner.service - LSB: remote network security auditor - scanner >> > Loaded: loaded (/etc/init.d/openvas-scanner; generated) >> > Active: failed (Result: timeout) since Fri 2018-07-06 08:28:05 CDT; >> > 19min ago >> > Docs: man:systemd-sysv-generator(8) >> > Process: 2241 ExecStart=/etc/init.d/openvas-scanner start >> > (code=killed, signal=TERM) >> > Tasks: 1 (limit: 19660) >> > CGroup: /system.slice/openvas-scanner.service >> > └─2279 /usr/sbin/openvassd >> > >> > Jul 06 08:23:05 lance-desktop systemd[1]: Starting LSB: remote network >> > security auditor - scanner... >> > Jul 06 08:28:05 lance-desktop systemd[1]: openvas-scanner.service: Start >> > operation timed out. Terminating. >> > Jul 06 08:28:05 lance-desktop systemd[1]: openvas-scanner.service: >> > Failed with result 'timeout'. >> > Jul 06 08:28:05 lance-desktop systemd[1]: Failed to start LSB: remote >> > network security auditor - scanner. >> > >> > How about for the redis service as well? >> > sudo systemctl -l status redis.service >> > >> > ● redis-server.service - Advanced key-value store >> > Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; >> vendor preset: enabled) >> > Active: active (running) since Fri 2018-07-06 08:22:58 CDT; 34min ago >> > Docs: http://redis.io/documentation, >> > man:redis-server(1) >> > Process: 1746 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf >> (code=exited, status=0/SUCCESS) >> > Main PID: 1812 (redis-server) >> > Tasks: 4 (limit: 19660) >> > CGroup: /system.slice/redis-server.service >> > └─1812 /usr/bin/redis-server 127.0.0.1:0 <http://127.0.0.1:0 >> > >> > >> > Jul 06 08:22:58 lance-desktop systemd[1]: Starting Advanced key-value >> store... >> > Jul 06 08:22:58 lance-desktop systemd[1]: redis-server.service: Can't >> open PID file /var/run/redis/redis-serve >> > Jul 06 08:22:58 lance-desktop systemd[1]: Started Advanced key-value >> store. >> > >> > What does the redis config look like? >> > sudo grep -vE '^.*#|^;|^$' /etc/redis.conf >> > >> > sudo grep -vE '^.*#|^;|^$' /etc/redis/redis.conf bind 127.0.0.1 ::1 >> > protected-mode yes port 0 tcp-backlog 511 timeout 0 tcp-keepalive 300 >> > daemonize yes supervised no pidfile /var/run/redis/redis-server.pid >> > loglevel notice logfile /var/log/redis/redis-server.log databases 16 >> > always-show-logo yes save 900 1 save 300 10 save 60 10000 >> > stop-writes-on-bgsave-error yes rdbcompression yes rdbchecksum yes >> > dbfilename dump.rdb dir /var/lib/redis slave-serve-stale-data yes >> > slave-read-only yes repl-diskless-sync no repl-diskless-sync-delay 5 >> > repl-disable-tcp-nodelay no slave-priority 100 lazyfree-lazy-eviction no >> > lazyfree-lazy-expire no lazyfree-lazy-server-del no slave-lazy-flush no >> > appendonly no appendfilename "appendonly.aof" appendfsync everysec >> > no-appendfsync-on-rewrite no auto-aof-rewrite-percentage 100 >> > auto-aof-rewrite-min-size 64mb aof-load-truncated yes >> > aof-use-rdb-preamble no lua-time-limit 5000 slowlog-log-slower-than >> > 10000 slowlog-max-len 128 latency-monitor-threshold 0 >> > notify-keyspace-events "" hash-max-ziplist-entries 512 >> > hash-max-ziplist-value 64 list-max-ziplist-size -2 list-compress-depth 0 >> > set-max-intset-entries 512 zset-max-ziplist-entries 128 >> > zset-max-ziplist-value 64 hll-sparse-max-bytes 3000 activerehashing yes >> > client-output-buffer-limit normal 0 0 0 client-output-buffer-limit slave >> > 256mb 64mb 60 client-output-buffer-limit pubsub 32mb 8mb 60 hz 10 >> > aof-rewrite-incremental-fsync yes unixsocket /var/run/redis/redis.sock >> > unixsocketperm 755 timeout 0 >> > >> > >> > >> > >> > On Thu, Jul 5, 2018 at 1:34 PM Lance M. Caven <lance...@gmail.com >> > <mailto:lance...@gmail.com>> wrote: >> > >> > 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 >> > >> _______________________________________________ >> Openvas-discuss mailing list >> Openvas-discuss@wald.intevation.org >> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss > > _______________________________________________ > Openvas-discuss mailing list > Openvas-discuss@wald.intevation.org > https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
_______________________________________________ Openvas-discuss mailing list Openvas-discuss@wald.intevation.org https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss
