Description of problem: The shutdown process are "sometime" very long. It says something like "A job is running [...] openVAS [...] (XXminXXsec/20min)" Sorry but, 20minutes for shutting down my laptop which doesn't stay to long without be plugged, 20min before leaving the place is a long time ! (In fact, I abord the shutdown process, staying many seconds on the power button :/ ) (Were can I find the log for shutdown process for better informations ?) How reproducible: I don't know, it is random for each shutdown process, I think the probability is 20%.
(In reply to J-B B from comment #0) > Description of problem: > The shutdown process are "sometime" very long. It says something like "A job > is running [...] openVAS [...] (XXminXXsec/20min)" > Sorry but, 20minutes for shutting down my laptop which doesn't stay to long > without be plugged, 20min before leaving the place is a long time ! After it happens again, on next boot, please run, as root: journalctl -ab-1 > log.txt and attach log.txt to this bug report. Also, please give the output of rpm -qa '*openvas*' Assigning to the maintainer of the openvas packages
CC: (none) => marja11Source RPM: (none) => openvas-*Assignee: bugsquad => guillomovitchSummary: very long shutdown process. => very long shutdown process (openVAS 20 minutes stopjob or so)Keywords: (none) => NEEDINFO
Hey ! I got it ! For $rpm -qa '*openvas*' : $ rpm -qa '*openvas*' lib64openvas8-8.0.8-1.mga6 openvas-scanner-5.0.7-2.mga6 For the journalctl : https://framadrop.org/r/dBtCA-sXkG#/s30qpDWXUBAg+dCYYsPebkn8KcMo7uUZMaG0Z8FSCU= from line 30647 (15:27:29) to line 30701 (15:47:22) there is... twenty minutes. I wait only for this. Resume of OpenVAS: déc. 09 12:02:18 Jazptop systemd[1]: Starting OpenVAS Scanner... déc. 09 12:02:18 Jazptop systemd[1]: Started OpenVAS Scanner. déc. 09 12:02:18 Jazptop audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=openvas-scanner comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' déc. 09 12:02:18 Jazptop kernel: audit: type=1130 audit(1512817338.938:80): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=openvas-scanner comm="systemd" exe="/usr /lib/systemd/systemd" hostname=? addr=? terminal=? res=success' déc. 10 06:17:28 Jazptop msec[10994]: Security Warning: these home directory should not be owned by someone else or writable : déc. 10 06:17:28 Jazptop msec[10995]: user=davfs2(983) : home directory is group writable. déc. 10 06:17:28 Jazptop msec[10997]: These are the ports listening on your machine : déc. 10 06:17:28 Jazptop msec[10998]: Connexions Internet actives (seulement serveurs) déc. 10 06:17:28 Jazptop msec[10999]: Proto Recv-Q Send-Q Adresse locale Adresse distante Etat Program name tcp 0 0 0.0.0.0:9391 0.0.0.0:* LISTEN openvassd: Wai déc. 10 15:27:22 Jazptop systemd[1]: Stopping OpenVAS Scanner... déc. 10 15:47:22 Jazptop systemd[1]: openvas-scanner.service: State 'stop-sigterm' timed out. Killing. déc. 10 15:47:22 Jazptop kernel: audit: type=1131 audit(1512917242.488:508): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=openvas-scanner comm="systemd" exe="/usr /lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' déc. 10 15:47:22 Jazptop audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=openvas-scanner comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' déc. 10 15:47:22 Jazptop systemd[1]: openvas-scanner.service: Main process exited, code=killed, status=9/KILL déc. 10 15:47:22 Jazptop systemd[1]: Stopped OpenVAS Scanner. déc. 10 15:47:22 Jazptop systemd[1]: openvas-scanner.service: Unit entered failed state. déc. 10 15:47:22 Jazptop systemd[1]: openvas-scanner.service: Failed with result 'signal'.
Unfortunatly for you, I'm unable to reproduce the issue, and I have no clue about its cause. The only workaround I can suggest you is to lower the timeout value in the systemd service file, whose current value matches your 20 minutes delay: TimeoutSec=1200
Status: NEW => RESOLVEDResolution: (none) => WORKSFORME