We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Installed clamav using helm chart, functionality wise things are working as expected, however unable to get memory details with clamdtop command.
Versions: Clamav : 1.3.1 Kubernetes: 1.29
clamdtop command has below output
ClamdTOP version 1.3.1 Fri Sep 6 10:09:59 2024 NO CONNTIME LIV IDL QUEUE MAXQ MEM ENGINE DBVER DBTIME HOST 1 00:22:38 1 0 0 0 N/A 1.3.1 27389 2024-09-05T08 local Details for Clamd version: ClamAV 1.3.1/27389/Thu Sep 5 08:33:25 2024 Primary threads: live 1 idle 0 max 10 ┌───────────────────────────────────────┐ [|||| ] │Mem: heap N/A mmap N/A unused N/A│ Queue: 0 items 0 max │Libc: used N/A free N/A total N/A│ [ ] │Pool: count 1 used 1382M total 1382M│ │[||||||||||||||||||||||||||||||||||||] │ └───────────────────────────────────────┘ COMMAND QUEUEDSINCE FILE STATS 0.000s
clamconf -n
Checking configuration files in /etc/clamav Config file: clamd.conf ----------------------- LogTime = "yes" PidFile = "/tmp/clamd.pid" TemporaryDirectory = "/tmp" DatabaseDirectory = "/data" LocalSocket = "/tmp/clamd.sock" TCPSocket = "3310" Foreground = "yes" DetectPUA = "yes" ExcludePUA = "NetTool", "PWTool" AlertBrokenExecutables = "yes" MaxScanSize = "157286400" MaxFileSize = "31457280" MaxRecursion = "10" MaxFiles = "15000" MaxEmbeddedPE = "10485760" MaxHTMLNormalize = "10485760" MaxHTMLNoTags = "2097152" MaxScriptNormalize = "5242880" MaxPartitions = "128" MaxIconsPE = "200" PCREMatchLimit = "10000" PCRERecMatchLimit = "10000" DisableCertCheck = "yes" Config file: freshclam.conf --------------------------- LogTime = "yes" PidFile = "/tmp/freshclam.pid" DatabaseDirectory = "/data" UpdateLogFile = "/dev/stdout" DatabaseOwner = "2000" DatabaseMirror = "database.clamav.net" Config file: clamav-milter.conf ------------------------------- LogFile = "/var/log/clamav/milter.log" LogTime = "yes" PidFile = "/tmp/clamav-milter.pid" User = "clamav" ClamdSocket = "unix:/tmp/clamd.sock", "unix:/tmp/clamd.sock", "unix:/tmp/clamd.sock", "unix:/tmp/clamd.sock", "unix:/tmp/clamd.sock", "unix:/tmp/clamd.sock" MilterSocket = "inet:7357" Software settings ----------------- Version: 1.3.1 Optional features supported: MEMPOOL AUTOIT_EA06 BZIP2 LIBXML2 PCRE2 ICONV JSON RAR Database information -------------------- Database directory: /data bytecode.cvd: version 335, sigs: 86, built on Tue Feb 27 15:37:24 2024 main.cvd: version 62, sigs: 6647427, built on Thu Sep 16 12:32:42 2021 daily.cld: version 27389, sigs: 2066461, built on Thu Sep 5 08:33:25 2024 Total number of signatures: 8713974 Platform information -------------------- uname: Linux 6.5.0-1024-aws #24~22.04.1-Ubuntu SMP Thu Jul 18 10:43:12 UTC 2024 x86_64 OS: Linux, ARCH: x86_64, CPU: x86_64 zlib version: 1.2.13 (1.2.13), compile flags: a9 platform id: 0x0a21c9c908000000000c0201 Build information ----------------- GNU C: 12.2.1 20220924 (12.2.1) sizeof(void*) = 8 Engine flevel: 201, dconf: 201
If applicable, add screenshots to help explain your problem.
If the issue is reproducible only when scanning a specific file, attach it to the ticket.
The text was updated successfully, but these errors were encountered:
I believe this is the same issue as #706
Sorry, something went wrong.
No branches or pull requests
Describe the bug
Installed clamav using helm chart, functionality wise things are working as expected, however unable to get memory details with clamdtop command.
Versions:
Clamav : 1.3.1
Kubernetes: 1.29
How to reproduce the problem
clamdtop command has below output
Attachments
If applicable, add screenshots to help explain your problem.
If the issue is reproducible only when scanning a specific file, attach it to the ticket.
The text was updated successfully, but these errors were encountered: