• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

clamd crashing affecting proxy

Scheduled Pinned Locked Moved Cache/Proxy
1 Posts 1 Posters 410 Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A
    adamw
    last edited by Jan 8, 2019, 1:12 PM

    Hello,

    My environment:
    2.4.4-RELEASE-p1
    squid-0.4.44_7
    Netgate SG-3100 with 32GB SSD

    Settings (pretty much default):
    Enable Squid antivirus check using ClamAV
    Enable Google Safe Browsing support
    Exclude Audio/Video Streams
    ClamAV Database Update: every 1 hour
    Regional ClamAV Database Update Mirror: United Kingdom

    PROBLEM:
    Every 2-3 days (on average) clamd crashes producing only a single line in logs:

    Jan 3 08:33:07	kernel		pid 90580 (clamd), uid 106: exited on signal 10
    

    No additional info in /var/log/clamav/clamd.log

    (...)
    SelfCheck: Database status OK.
    Reading databases from /var/db/clamav/
    Database correctly reloaded (9623988 signatures)
    SelfCheck: Database status OK.
    SelfCheck: Database status OK.
    SelfCheck: Database status OK.
    SelfCheck: Database status OK.      ---> CRASH
    +++ Started at Thu Jan  3 09:13:45 2019
    Received 0 file descriptor(s) from systemd.
    clamd daemon 0.100.2 (OS: freebsd11.2, ARCH: arm, CPU: armv6)
    Running as user clamav (UID 106, GID 106)
    Log file size limited to 1048576 bytes.
    Reading databases from /var/db/clamav/
    Not loading PUA signatures.
    Bytecode: Security mode set to "TrustSigned".
    Loaded 9623988 signatures.
    LOCAL: Removing stale socket file /var/run/clamav/clamd.sock
    LOCAL: Unix socket file /var/run/clamav/clamd.sock
    LOCAL: Setting connection queue length to 200
    (...)
    

    As a result browsing either stops working or starts flickering (web pages come and go).
    At the same time squid itself doesn't report any problems.
    Starting clamd in Status -> Services solves the issue, but only until next crash.

    Any ideas?

    Thanks,
    Adam

    1 Reply Last reply Reply Quote 0
    1 out of 1
    • First post
      1/1
      Last post
    Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
      This community forum collects and processes your personal information.
      consent.not_received