You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
... I understand that not following the below instructions will result in immediate closure and/or deletion of my issue.
... I have understood that this bug report is dedicated for bugs, and not for support-related inquiries.
... I have understood that answers are voluntary and community-driven, and not commercial support.
... I have verified that my issue has not been already answered in the past. I also checked previous issues.
Description
We have a MailCow instance where all containers are HEALTHY except for the ClamD container keeps restarting with logs below.
Is there a way to RESET this container somehow so it could start fresh?
*** Please forgive me if I am repeating. I searched for the topic in Issues but was not able to see anything.
Logs:
Size: 190 Blocks: 8 IO Block: 4096 regular file
Device: 820h/2080d Inode: 2883594 Links: 1
Access: (0644/-rw-r--r--) Uid: ( 100/ clamav) Gid: ( 101/ clamav)
Access: 2024-12-19 09:10:54.058434276 -0500
Modify: 2024-12-19 09:10:54.058434276 -0500
Change: 2024-12-19 09:10:54.061767626 -0500
Running freshclam...
Thu Dec 19 09:10:54 2024 -> ClamAV update process started at Thu Dec 19 09:10:54 2024
Thu Dec 19 09:10:54 2024 -> daily.cld database is up-to-date (version: 27492, sigs: 2070575, f-level: 90, builder: raynman)
Thu Dec 19 09:10:54 2024 -> main.cvd database is up-to-date (version: 62, sigs: 6647427, f-level: 90, builder: sigmgr)
Thu Dec 19 09:10:54 2024 -> bytecode.cld database is up-to-date (version: 335, sigs: 86, f-level: 90, builder: raynman)
LibClamAV Error: cli_add_content_match_pattern: Problem adding signature (2).
LibClamAV Error: Problem parsing database at line 31220
LibClamAV Error: Can't load /var/lib/clamav/phish.ndb: Malformed database
LibClamAV Error: cli_loaddbdir: error loading database /var/lib/clamav/phish.ndb
ERROR: Thu Dec 19 09:11:11 2024 -> Malformed database
Worker 23 died, stopping container waiting for respawn...
/clamd.sh: line 99: kill: (23) - No such process
Cleaning up tmp files...
Copying non-empty whitelist.ign2 to /var/lib/clamav/whitelist.ign2
File: /var/lib/clamav/whitelist.ign2
Steps to reproduce:
Not sure if there is a procedure to reproduce this, it is just happening in our case.
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Ubuntu 22.04.5 LTS
Server/VM specifications:
16 GB, x6 Core, 512 GB (52 GB consumed)
Is Apparmor, SELinux or similar active?
No
Virtualization technology:
KVM
Docker version:
27.3.1, build ce12230
docker-compose version or docker compose version:
2.29.7
mailcow version:
2023-11
Reverse proxy:
MailCow NginX
Logs of git diff:
diff --git a/.github/ISSUE_TEMPLATE/Bug_report.yml b/.github/ISSUE_TEMPLATE/Bug_report.yml
index afa1a27f..3cfbbe0d 100644
--- a/.github/ISSUE_TEMPLATE/Bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/Bug_report.yml
@@ -62,16 +62,6 @@ body:
- nightly
validations:
required: true
- - type: dropdown
- attributes:
- label: "Which architecture are you using?"
- description: "#### `uname -m`"
- multiple: false
- options:
- - x86
- - ARM64 (aarch64)
- validations:
- required: true
- type: input
attributes:
label: "Operating System:"
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
index 5c422bb4..dcda8f02 100644
--- a/.github/ISSUE_TEMPLATE/config.yml
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -1,11 +1,8 @@
blank_issues_enabled: false
contact_links:
- - name: ❓ Community-driven support (Free)
+ - name: ❓ Community-driven support
url: https://docs.mailcow.email/#get-support
about: Please use the community forum for questions or assistance
- - name: 🔥 Premium Support (Paid)
- url: https://www.servercow.de/mailcow?lang=en#support
- about: Buy a support subscription for any critical issues and get assisted by the mailcow Team. See conditions!
- name: 🚨 Report a security vulnerability
- url: "mailto:info@servercow.de?subject=mailcow: dockerized Security Vulnerability"
+ url: https://www.servercow.de/anfrage?lang=en
about: Please give us appropriate time to verify, respond and fix before disclosure.
diff --git a/.github/workflows/check_if_support_labeled.yml b/.github/workflows/check_if_support_labeled.yml
deleted file mode 100644
Contribution guidelines
I've found a bug and checked that ...
Description
Logs:
Steps to reproduce:
Which branch are you using?
master
Which architecture are you using?
x86
Operating System:
Ubuntu 22.04.5 LTS
Server/VM specifications:
16 GB, x6 Core, 512 GB (52 GB consumed)
Is Apparmor, SELinux or similar active?
No
Virtualization technology:
KVM
Docker version:
27.3.1, build ce12230
docker-compose version or docker compose version:
2.29.7
mailcow version:
2023-11
Reverse proxy:
MailCow NginX
Logs of git diff:
Logs of iptables -L -vn:
Logs of ip6tables -L -vn:
Logs of iptables -L -vn -t nat:
Logs of ip6tables -L -vn -t nat:
DNS check:
The text was updated successfully, but these errors were encountered: