Closed austinginder closed 4 years ago
Actually I haven't been able to pinpoint the cause of this issue. It seems to periodically happen on both single
and file
commands. Sometimes I can crunch through hundreds of screenshots. Other times it gives an error after only a few screenshots.
Ah... it appears DB related. If I delete the gowitness.db
file it generates images just fine. If there is an existing gowitness.db
file it results in the above errors sporadically.
In case others run into it, I also got similar panic errors but the result was using the -D flag without providing an actual DB name. I was just pointing to a directory.
Hey, thanks for the report! I think this may be as a result of a race condition when using the buntdb storage which admittedly makes little sense in single
mode. As the db is only used when generating reports, I think I should add a flag to just disable writing the db entirely in cases where it may not be needed.
I'm attempting to batch collect images from hundreds of websites. Using
gowitness file
with threads seems to work fine. However for more control I'd like to usegowitness single
as it's part of a larger bash script. However running multiplegowitness single
commands or even manygowitness single
command consecutively and I'm get panic errors as shown below.If helpful here is the format of the
single
command I'm using.gowitness single --url="$url" --resolution="1200,750" --log-format=json --log-level=warn --timeout=60 --destination="/Users/austinginder/Desktop/Screenshots/"