[nos-bbs] Jnos memory leak with forwarding

Gustavo Ponza g.ponza at tin.it
Thu Oct 19 06:04:01 EDT 2017

On 10/18/2017 07:49 PM, Boudewijn (Bob) Tenty wrote:
> Yes, it is with incoming forwarding but what also plays a role here I think is when the indexing is messed up and this happens sometimes with a large area
> like 'ww' (@ww),  .idn and .new files are formed and jnos doesn't know what to do with it as it seems or the area is too large to fix the indexing.
> Is it running out of resources?
> Bob VE3TOK

I think that analysis is almost correct.
So, to mitigate the failure expire the
areas to drastically reduce bulletins.
Then, if messages as above remain
pending on 'mqueue/rqueue' delete
them together with their information
files. Don't touch the 'sequence.seq'.
As last chance delete all contents of
mail an restart the JNOS :)

I don't know your or other situations
but from my experience many resources
are spent to reply to the many attacks
to our systems... the jnos is rebooting
more frequently at least  from the last
year... other programs seems to remain
hard rock without any collapse.

73 and ciao, gus i0ojj/ir0aab
A proud member of linux team
Quidquid latine dictum sit, altum videtur

More information about the nos-bbs mailing list