Skip to content

Update rspamd 1.8.3 (Were missing 10 CritFixes) or maybe even 1.9.3 #197

Description

@sjorge

Currently the newest rspamd is 1.8.0, there are a few minor release in the 1.8.x series that are marked CritFix. We can probably update to the newest 1.8.x release.

There is also a 1.9.x release that has a bunch of new and reworked stuff, not sure if it compliles.

Activity

  1. self-assigned this
    on Jun 21, 2019
  2. jperkin commented on Jun 21, 2019

    @jperkin
    Collaborator

    I updated this to 1.9.4, will be in trunk tonight and will backport to 2018Q4 too.

  3. sjorge commented on Jun 24, 2019

    @sjorge
    Author

    THe new one now segfaults!

    [root@test ~]# rspamadm configwizard
    Segmentation Fault (core dumped)
    

    This is the first command you should run after installing,... https://www.rspamd.com/doc/quickstart.html#caching-setup

  4. jperkin commented on Jun 24, 2019

    @jperkin
    Collaborator

    Is that with a clean setup or an upgrade? I tried to reproduce on a host that hasn't configured it before and it seemed to work ok:

    [root@trunk ~]# pkgin in rspamd
    ...
    [root@trunk ~]# /usr/sbin/svcadm enable -r svc:/pkgsrc/rspamd:default
    svcadm: svc:/milestone/network:default depends on svc:/network/physical, which has multiple instances.
    [root@trunk ~]# svcs -xv
    [root@trunk ~]# rspamadm configwizard
      ____                                     _
     |  _ \  ___  _ __    __ _  _ __ ___    __| |
     | |_) |/ __|| '_ \  / _` || '_ ` _ \  / _` |
     |  _ < \__ \| |_) || (_| || | | | | || (_| |
     |_| \_\|___/| .__/  \__,_||_| |_| |_| \__,_|
                 |_|
    
    Welcome to the configuration tool
    We use /opt/local/etc/rspamd/rspamd.conf configuration file, writing results to /opt/local/etc/rspamd
    Modules enabled: arc, whitelist, force_actions, multimap, trie, mid, settings, dkim_signing, elastic, chartable, ip_score, rbl, forged_recipients, dkim, dmarc, spf, maillist, phishing, mime_types, metadata_exporter, asn, fuzzy_check, once_received, regexp, milter_headers, emails, hfilter, bayes_expiry, surbl
    Modules disabled (explicitly): spamtrap, url_tags, mx_check, neural, url_reputation, dcc, rspamd_update
    Modules disabled (unconfigured): fuzzy_collect, antivirus, clickhouse, maps_stats, dynamic_conf, external_services, metric_exporter, spamassassin, reputation, clustering
    Modules disabled (no Redis): ratelimit, replies, url_redirector, history_redis, greylist
    Modules disabled (experimental): 
    Modules disabled (failed): 
    Do you wish to continue?[Y/n]: 
    Setup WebUI and controller worker:
    Controller password is not set, do you want to set one?[Y/n]: 
    Enter passphrase: 
    ...
    
  5. sjorge commented on Jun 24, 2019

    @sjorge
    Author

    It was a clean setup on 2018Q4 (base-64-lts 18.4.0),

    It seems to happen intermittendly :s I just tried it again and it segfaulted, I wanted to truss and it didn't :/

    [root@test ~]# rspamadm configwizard
    Segmentation Fault (core dumped)
    [root@test ~]# rspamadm configwizard
      ____                                     _
     |  _ \  ___  _ __    __ _  _ __ ___    __| |
     | |_) |/ __|| '_ \  / _` || '_ ` _ \  / _` |
     |  _ < \__ \| |_) || (_| || | | | | || (_| |
     |_| \_\|___/| .__/  \__,_||_| |_| |_| \__,_|
                 |_|
    
    Welcome to the configuration tool
    We use /opt/local/etc/rspamd/rspamd.conf configuration file, writing results to /opt/local/etc/rspamd
    Modules enabled: mid, regexp, ratelimit, dmarc, bayes_expiry, settings, metadata_exporter, maillist, spf, milter_headers, forged_recipients, asn, greylist, emails, phishing, hfilter, dkim, surbl, dkim_signing, rbl, mx_check, ip_score, trie, fuzzy_check, whitelist, arc, mime_types, once_received, history_redis, chartable, replies, multimap, url_redirector, force_actions
    Modules disabled (explicitly): rspamd_update, url_reputation, url_tags, spamtrap, neural, dcc
    Modules disabled (unconfigured): elastic, spamassassin, clickhouse, external_services, fuzzy_collect, reputation, dynamic_conf, metric_exporter, clustering, maps_stats, antivirus
    Modules disabled (no Redis):
    Modules disabled (experimental):
    Modules disabled (failed):
    Do you wish to continue?[Y/n]: n
    

    Other commands also gives error but don't seem to segfault

    [root@test ~]# rspamadm configtest
    lock on file failed: Bad file number
    syntax OK
    

    I double checked that the rspamd service was running and it was

    [root@test ~]# svcs -a | grep rspamd:default
    online         21:56:04 svc:/pkgsrc/rspamd:default
    
  6. jperkin commented on Jun 24, 2019

    @jperkin
    Collaborator

    Ok I'll see if I can tickle it, or if you ever get a core file out of it please send it over.

  7. sjorge commented on Jun 24, 2019

    @sjorge
    Author

    I couldn't find one for now.

    Found a few! I have them for rspam and rspamadm! I included one of each: https://pkg.blackdot.be/cores/rspam_cores.tar.bz2

  8. sjorge commented on Jun 25, 2019

    @sjorge
    Author

    I rebooted the zone, not that it should matter... but it made it worse!

    After a reboot rspamd doens't even start! (default config)

    2019-06-25 12:00:48 #10620(main) rspamd_file_lock: lock on file failed: Bad file number
    2019-06-25 12:00:48 #10620(main) <cb6389>; main; main: cannot write pid file /var/run/
    

    There is indeed no longer a /var/run/rspamd directory!

    pkgin rm rspamd
    pkgin in rspamd
    

    The /var/run/rspamd dir now exists! And rspamd starts again (unless it segfaults, that still happens at random)

  9. jperkin commented on Jun 25, 2019

    @jperkin
    Collaborator

    This is a bug in the package, /var/run is a tmpfs mount and as such needs to be created on startup, not on package install. We handle this correctly in other packages, I'll take a look at fixing this as well.

  10. added a commit that references this issue on Jul 1, 2019
  11. added a commit that references this issue on Oct 6, 2019
  12. added a commit that references this issue on Oct 20, 2019
  13. 99 remaining items

  14. added a commit that references this issue on Jul 17, 2026
  15. added a commit that references this issue on Jul 26, 2026
  16. added a commit that references this issue on Aug 7, 2026
  17. added a commit that references this issue on Aug 25, 2026
  18. added a commit that references this issue on Sep 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions