Panic on packet scan about vuls HOT 12 CLOSED

Thanks for reporting.
please update Vuls, then try again.

from vuls.

on it

from vuls.

I want to get more information.
Please paste the output of running with --debug option.

from vuls.

it failed without debug, i run it again with debug mode

from vuls.

time="Jul 12 14:57:16" level=debug msg="Command: set -o pipefail; aptitude changelog docker-engine | grep '\\(urgency\\|CVE\\)'" 
time="Jul 12 14:57:16" level=debug msg="SSH executed. cmd: set -o pipefail; wget --tries=3 --timeout=1 --no-proxy -q -O - http://1.2.3.4/latest/meta-data/instance-id, err: <nil>, status: 4\nstdout: \n\nstderr: \n" 
panic: send on closed channel

goroutine 515 [running]:
panic(0xae3440, 0xc82060b320)
        /usr/local/go/src/runtime/panic.go:481 +0x3e6
github.com/future-architect/vuls/scan.parallelSSHExec.func1(0xe7c660, 0xc820258d20, 0x7f734519b9e8, 0xc820162000)
        /go/src/github.com/future-architect/vuls/scan/sshutil.go:80 +0x37d
created by github.com/future-architect/vuls/scan.parallelSSHExec
        /go/src/github.com/future-architect/vuls/scan/sshutil.go:84 +0x166

here you go

from vuls.

I can not reproduce this problem...

from vuls.

Probably, Snipped log is pasted.

Please send me the entire log by slack message if you like.
Vuls-slack ... https://vuls-github.slack.com/messages

You can join the slack team via this link.
https://docs.google.com/forms/d/e/1FAIpQLSfMyxCKV0C1ukTE0Mc9oyOHDI_2nbz4L75LAMj0D_A2vx_fMA/viewform?c=0&w=1

from vuls.

I understood the reason of this problem.
I am going to fix it.

from vuls.

okay! Thanks a lot! I didnt had time to go into more details on slack even though I cared to join, sorry.

from vuls.

This problem was fixed in #134 .
Please try with latest revision.
Thanks for reporting!

from vuls.

All right, version will be in trial in a few hours

from vuls.

If you are still in trouble, reopen the issue.
Thanks.

from vuls.