[Rspamd-Users] Worker Fuzzy "process fuzzy error"

[Emanuel Gonzalez]

Here the log:

2019-11-06 12:05:03 #8975(fuzzy) <4574f1>; main;
rspamd_worker_term_handler: terminating after receiving signal Terminated
2019-11-06 12:05:03 #8970(main) <4574f1>; main;
rspamd_check_termination_clause: fuzzy process 8975 terminated normally
2019-11-06 12:05:03 #8970(main) <4574f1>; main; rspamd_cld_handler: do not
respawn process fuzzy after found terminated process with pid 8975
2019-11-06 12:05:04 #9046(main) <r895s5>; cfg; fuzzy_parse_rule: added
fuzzy rule R_FUZZY_HASH, key: ef43ae80cc8d, shingles_key: ef43ae80cc8d,
algorithm: sip
2019-11-06 12:05:04 #9046(main) <r895s5>; cfg; fuzzy_check_module_config:
init internal fuzzy_check module, 1 rules loaded
2019-11-06 12:05:04 #9046(main) <r895s5>; cfg;
rspamd_config_is_module_enabled: lua module fuzzy_collect is enabled but
has not been configured
2019-11-06 12:05:04 #9046(main) <r895s5>; cfg;
rspamd_config_is_module_enabled: fuzzy_collect disabling unconfigured lua
module
2019-11-06 12:05:04 #9046(main) <ed76a3>; main; spawn_workers: worker of
type fuzzy(localhost) is disabled in the config, skip spawning
2019-11-06 12:05:04 #9046(main) <ed76a3>; main; rspamd_fork_worker: prepare
to fork process fuzzy (0); listen on: *
2019-11-06 12:05:04 #9050(fuzzy) <ed76a3>; main; rspamd_worker_set_limits:
use system max file descriptors limit: 1024KiB cur and 1024KiB max
2019-11-06 12:05:04 #9050(fuzzy) <ed76a3>; main; rspamd_worker_set_limits:
use system max core size limit: 0B cur and -1B max
2019-11-06 12:05:04 #9050(fuzzy) <ed76a3>; main; rspamd_fork_worker:
starting fuzzy process 9050 (0); listen on: *:11335
2019-11-06 12:05:04 #9050(fuzzy) <r895s5>; cfg;
rspamd_dns_resolv_conf_on_server: parsed nameserver 200.58.117.74 from
resolv.conf
2019-11-06 12:05:04 #9050(fuzzy) <r895s5>; cfg;
rspamd_dns_resolv_conf_on_server: parsed nameserver 200.58.122.8 from
resolv.conf
2019-11-06 12:05:04 #9050(fuzzy) <r895s5>; cfg;
rspamd_dns_resolv_conf_on_server: parsed nameserver 200.58.117.74 from
resolv.conf
2019-11-06 12:05:04 #9050(fuzzy) <r895s5>; cfg;
rspamd_dns_resolv_conf_on_server: parsed nameserver 200.58.122.8 from
resolv.conf
2019-11-06 12:05:04 #9050(fuzzy) fuzzy_peer_rep: got peer fd reply from the
main process
2019-11-06 12:05:04 #9050(fuzzy) fuzzy_peer_rep: start listening on
[::]:11335
2019-11-06 12:05:04 #9050(fuzzy) fuzzy_peer_rep: start listening on
0.0.0.0:11335
2019-11-06 12:05:18 #9048(controller) <20c9e2>; task;
fuzzy_controller_io_callback: fuzzy hash (bin) for message cannot be added<
0.0.0.18.1D59342E335E720.678E85 at mail.expertsimplyinterested.com>,
4a5e05f1961268df79ecefa345bcdaaae6766a72d392643e28c5ec570b65c72b5b5814e33e545a1b64a9eb9a38bdca4b713d90c59113cd6829e9395d9d390e7e,
list FUZZY_DENIED:1, error: 403

El mar., 5 de nov. de 2019 a la(s) 12:16, Emanuel Gonzalez (
emawata at gmail.com) escribió:

> Hello,
>
> I configured the worker fuzzy, but i received this error "HTTP error: 403,
> process fuzzy error"
>
> [root at vpsx ~] # rspamc -w 20 -f 1 fuzzy_add Are\ you\ prepared\ for\
> Medicare\ Annual\ Election\ Period_.eml
> Results for file: Are you prepared for Medicare Annual Election
> Period_.eml (0.000 seconds)
> HTTP error: 403, process fuzzy error
>
> [root at vpsx ~] # rspamadm configdump fuzzy_check
> no actions defined
> *** Section fuzzy_check ***
> retransmits = 1;
> rule {
>    read_only = false;
>    max_score = 20;
>    fuzzy_map {
>        FUZZY_DENIED {
>            flag = 1;
>            weight = 20;
>        }
>        FUZZY_WHITE {
>            flag = 3;
>            weight = 0;
>        }
>    }
>    mime_types = "application/*";
>    servers = "*:11335";
>    skip_unknown = true;
> }
> timeout = 2;
> min_bytes = 1000;
>
> *** End of section fuzzy_check ***
>
> [root at vpsx ~] # rspamadm configdump worker
>
> fuzzy {
>    backend = "redis";
>    expire = 7776000;
>    allow_update = "::1 127.0.0.1";
>    type = "fuzzy";
>    count = -1;
>    bind_socket = "*:11335";
>    hashfile = "/var/lib/rspamd/fuzzy.db";
> }
>
> I see the db file not exits in /var/lib/rspamd, maybe the error 403 is for
> this?
>
> Regards,
>