New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MAJOR - All files detected as {CAV}lstat() #59
Comments
Seems to be linked to #58 maldet(9229): {scan} setting nice scheduler priorities for all operations: cpunice 19 , ionice 6 |
I see in the clamd.log
for every file while a maldet -a is going on. I also saw in the shell
The first time this happened I chickened out and killed the process. Then I reviewed conf.maldet and saw that quarantine_hits=0, which is great, so I'm running it again. Same behavior showing a lot of hits and lstat fails... |
What OS version? (cat /etc/redhat-release) |
Issue is because clamdscan cannot scan file because if |
My scan finished with lots of false positives and one command not found (see below)
|
I need the debug output file from my sample command above, debug.maldet: |
I ran it and was inspecting/sanitizing. :-) Where should I send the file? |
ryan at rfxn.com please |
An update has been pushed out to resolve this issue. Please run 'maldet -d' to update to the latest release. Further, if you got bitten by this in any way, you can use the 'maldet -e list' command to review scan result summary, the scan session id with false positive hits can be restored in its entirety with: Thank you for the feedback! |
Are you sure update push ? maldet- d change nothing... Jérémy Le 19/09/2015 11:41, Ryan MacDonald a écrit :
Jérémy Carnus |
verified, I'm not picking up a new drop either. |
got a new drop |
Not getting {CAV}Access hits any longer, thanks! I still get a bunch of WARNING: lstat() failed on: in the clamd log when the scan runs, but everything seems ok. |
Any news on this ? I'm also being affected by this..however my errors are like this:
And the clamscan says:
Also, the number of files is very wrong. The number is actually 5 files. |
All in the title
The text was updated successfully, but these errors were encountered: