Skip to content

bug report: Rspamd crash when sending or receiving #3374

@FriderKlugser

Description

@FriderKlugser

Preliminary Checks

  • I checked that all ports are open and not blocked by my ISP / hosting provider.

  • I know that SSL errors are likely the result of a wrong setup on the user side and not caused by DMS itself. I'm confident my setup is correct.

  • I searched the issue tracker but was unable to find my issue.

  • I read

What operating system is the host running?

Linux

Which operating system version?

Debian 11 (Bullseye)

What computer architecture is the host running?

ARM64 (AArch64)

What container orchestration tool are you using?

Docker Compose

DMS version

v12.1.0

What happened and when does this occur?

From time to time Rspamd crashs when sending or receiving an e-mail. And then doesn't check e-mails properly, as seen (missing) in the Web interface history.

I'm running DMS on an Raspberry Pi 4 (8 GB).

What did you expect to happen?

No Rspamd crashs.

Container configuration files

compose.yaml

services:
  Mailserver:
    container_name: Mailserver
    hostname: mx.domain.tld
    image: docker.io/mailserver/docker-mailserver:latest
    pull_policy: always
    healthcheck: {disable: true}
    restart: unless-stopped
    stop_grace_period: 1m30s
    stdin_open: true
    tty: true
    networks: [bridge-mail]
    cap_add: [NET_ADMIN]
    ports:
    - "25:25"
    - "143:143"
    - "465:465"
    - "587:587"
    - "993:993"
    - "4190:4190" # ManageSieve
    - "11334:11334" # Rspamd
    volumes:
    - ./Mailserver/config:/tmp/docker-mailserver:rw
    - ./Mailserver/data:/var/mail:rw
    - ./Mailserver/state:/var/mail-state:rw
    - ./Mailserver/log:/var/log/mail:rw
    - ./Certbot/etc/archive/domain.tld:/etc/letsencrypt/archive/domain.tld:ro
    - ./Certbot/etc/live/domain.tld:/etc/letsencrypt/live/domain.tld:ro
    env_file: ./Mailserver/mailserver.env

networks:
  bridge-mail:
    name: bridge-mail
    driver: bridge

mailserver.env Changes

TZ=Europe/Berlin

SPOOF_PROTECTION=1

ENABLE_OPENDKIM=0
ENABLE_OPENDMARC=0
ENABLE_POLICYD_SPF=0
ENABLE_CLAMAV=1
ENABLE_RSPAMD=1
ENABLE_AMAVIS=0
ENABLE_DNSBL=1
ENABLE_FAIL2BAN=1

SSL_TYPE=letsencrypt

POSTFIX_INET_PROTOCOLS=ipv4
DOVECOT_INET_PROTOCOLS=ipv4

DEFAULT_RELAY_HOST=[host.provider.tld]:465
RELAY_HOST=host.provider.tld
RELAY_PORT=465
RELAY_USER=[email protected]
RELAY_PASSWORD=...

postfix-main.cf

myorigin = $mydomain
smtp_tls_wrappermode = yes

postfix-regexp.cf

/^(abuse|admin|administrator|hostmaster|postmaster|security|webmaster)@(domain\.tld|otherdomain\.othertld)$/ [email protected]

dkim_signing.conf

allow_username_mismatch = true;

selector = "email";
path = "/tmp/docker-mailserver/rspamd/dkim/rsa-2048-$selector-$domain.private.txt";

worker-controller.inc

password = "...";
enable_password = "...";

Relevant log output

/var/log/supervisor/rspamd.log
2023-05-28 21:21:56 #609(rspamd_proxy) rspamd_crash_sig_handler: caught fatal signal 11(Segmentation fault), pid: 609, trace:
2023-05-28 21:21:56 #609(rspamd_proxy) rspamd_print_crash: 0: 0000007FA202F9D4: <unknown>
2023-05-28 21:21:56 #609(rspamd_proxy) rspamd_print_crash: 1: 000000000000003A: <unknown>
2023-05-28 21:21:56 #582(main) <65aa52>; main; rspamd_check_termination_clause: rspamd_proxy process 609 terminated abnormally with exit code 0 by signal: Segmentation fault but NOT created core file (throttled=no); core file limits: -1 current, -1 max
2023-05-28 21:21:56 #582(main) <65aa52>; main; rspamd_cld_handler: respawn process rspamd_proxy in lieu of terminated process with pid 609
2023-05-28 21:21:58 #582(main) <65aa52>; main; rspamd_fork_worker: prepare to fork process rspamd_proxy (1); listen on: 127.0.0.1:11332
2023-05-28 21:21:58 #919093(rspamd_proxy) <65aa52>; main; rspamd_worker_set_limits: use system max file descriptors limit: 1024KiB cur and 1024KiB max
2023-05-28 21:21:58 #919093(rspamd_proxy) <65aa52>; main; rspamd_worker_set_limits: use system max core size limit: -1B cur and -1B max
2023-05-28 21:22:13 #608(rspamd_proxy) <f29daa>; proxy; rspamd_redis_connected: skip obtaining bayes tokens for BAYES_HAM of classifier bayes: not enough learns 0; 200 required
2023-05-28 21:22:13 #608(rspamd_proxy) <f29daa>; proxy; rspamd_redis_connected: skip obtaining bayes tokens for BAYES_SPAM of classifier bayes: not enough learns 0; 200 required

I don't know if it has something to do with the following Output:

/var/log/supervisor/rspamd-redis.log
# WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.

What level of experience do you have with containers, mail servers, and using a terminal?

  • I am inexperienced with containers
  • I am rather experienced with containers
  • I am inexperienced with mail servers
  • I am rather experienced with mail servers
  • I am uncomfortable with using a terminal (CLI)
  • I am rather comfortable with using a terminal (CLI)

Improvements to this form?

No response

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions