Error converting from old BAYES_SPAM/HAM Redis Scheme

67 views
Skip to first unread message

Robert McGovern

unread,
Mar 12, 2018, 8:26:02 PM3/12/18
to rspamd
Hi,

I upgraded to 1.70 today, and ran "rspamadm configwizard". I let it migrate from the old BAYES_SPAM/HAM redis scheme, and while the BAYES_SPAM conversion succeeded, the BAYES_HAM failed.

You are using an old schema for BAYES_HAM/BAYES_SPAM
Do you wish to convert data to the new schema?[Y/n]: y
Expire time for new tokens  [default: 100d]:
converted 3160722 elements from symbol BAYES_SPAM
error converting symbol BAYES_HAM: ERR Error running script (call to f_6b10841ba3e1dc0b4d91f9d7e1f1e8efb4039625): @user_script:15: @user_script: 15: -OOM command not allowed when used memory > 'maxmemory'.
Conversion failed

What can I change to let the conversion succeed? Should I be concerned that the conversion failed?

Rob

Robert McGovern

unread,
Mar 12, 2018, 8:43:09 PM3/12/18
to rspamd
Consulting the logs there are now other OOM errors while running

ar 13 01:28:53 dedi rspamd[8593]: (rspamd_proxy) <a112a1>; lua; ip_score.lua:117: got error while IP score changing: OOM command not allowed when used memory > 'maxmemory'.
Mar 13 01:28:53 dedi rspamd[8593]: (rspamd_proxy) <a112a1>; lua; greylist.lua:353: greylisted until "Tue, 13 Mar 2018 00:33:53 GMT", new record
Mar 13 01:28:53 dedi rspamd[8593]: (rspamd_proxy) <a112a1>; proxy; lua_task_set_pre_result: <spammer email addresss>: set pre-result to soft reject: 'Try again later'
Mar 13 01:28:53 dedi rspamd[8593]: (rspamd_proxy) <a112a1>; lua; greylist.lua:312: got error OOM command not allowed when used memory > 'maxmemory'. when setting greylisting record on server 127.0.0.1(00000000400A4800)
Mar 13 01:28:53 dedi rspamd[8593]: (rspamd_proxy) <a112a1>; lua; history_redis.lua:92: got error OOM command not allowed when used memory > 'maxmemory'. when writing history row: no value

maxmemory was set to 500mb in the redis.conf, although according to htop redis is using 1475M (Virt), 1307M (Res), 1352 (Shr).
Reply all
Reply to author
Forward
0 new messages