Replicator: Panic: data stack: Out of memory

[hi at zakaria.website]

On 2022-06-04 12:20, Paul Kudla (SCOM.CA Internet Services Inc.) wrote:
> just an fyi domain is registered and appears to be active so there 
> should not be any issues with the domain
> 
> .website is an actual domain (like .com, .ca etc)
> 
> however i did note
> 
> ZAKARIA.WEBSITE.        14400   IN      MX      10 ZAKARIA.WEBSITE.
> 
> usually the mx record points to an actual sub domain like mail. or 
> whatever
> 
> if you are running everything on one server then this is ok
> 
> its just usually better to seperate the mx record incase you want to 
> goto a different server down the road.
> 
> 
> 
> Domain Name: ZAKARIA.WEBSITE
> Registry Domain ID: D198561373-CNIC
> Registrar WHOIS Server: whois.ionos.com
> Registrar URL: https://ionos.com
> Updated Date: 2021-11-02T01:42:25.0Z
> Creation Date: 2020-08-29T09:28:59.0Z
> Registry Expiry Date: 2022-08-29T23:59:59.0Z
> Registrar: IONOS SE
> Registrar IANA ID: 83
> Domain Status: clientTransferProhibited 
> https://icann.org/epp#clientTransferProhibited
> Registrant Organization: 1&1 Internet Limited
> Registrant State/Province: GLS
> Registrant Country: GB
> Registrant Email: Please query the RDDS service of the Registrar of 
> Record identified in this output for information on how to contact the 
> Registrant, Admin, or Tech contact of the queried domain name.
> Admin Email: Please query the RDDS service of the Registrar of Record 
> identified in this output for information on how to contact the 
> Registrant, Admin, or Tech contact of the queried domain name.
> Tech Email: Please query the RDDS service of the Registrar of Record 
> identified in this output for information on how to contact the 
> Registrant, Admin, or Tech contact of the queried domain name.
> Name Server: NS1.ZAKARIA.WEBSITE
> Name Server: NS2.ZAKARIA.WEBSITE
> 
> ## nslookup ZAKARIA.WEBSITE
> Server:         10.220.0.2
> Address:        10.220.0.2#53
> 
> Non-authoritative answer:
> Name:   ZAKARIA.WEBSITE
> Address: 213.171.210.111
> Name:   ZAKARIA.WEBSITE
> Address: 2a00:da00:1800:834c::1
> 
> ## dig mx ZAKARIA.WEBSITE
> 
> ; <<>> DiG 9.14.3 <<>> mx ZAKARIA.WEBSITE
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32110
> ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 3
> 
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 4096
> ; COOKIE: ba2f2ec47dfcc90f4581111d629b4d2855567ad8dfa57bf8 (good)
> ;; QUESTION SECTION:
> ;ZAKARIA.WEBSITE.               IN      MX
> 
> ;; ANSWER SECTION:
> ZAKARIA.WEBSITE.        14400   IN      MX      10 ZAKARIA.WEBSITE.
> 
> ;; ADDITIONAL SECTION:
> zakaria.website.        14372   IN      A       213.171.210.111
> zakaria.website.        14372   IN      AAAA    2a00:da00:1800:834c::1
> 
> ;; Query time: 87 msec
> ;; SERVER: 10.220.0.2#53(10.220.0.2)
> ;; WHEN: Sat Jun 04 08:16:40 EDT 2022
> ;; MSG SIZE  rcvd: 147
> 
> 
> 
> 
> Happy Saturday !!!
> Thanks - paul
> 
> Paul Kudla
> 
> 
> Scom.ca Internet Services <http://www.scom.ca>
> 004-1009 Byron Street South
> Whitby, Ontario - Canada
> L1N 4S3
> 
> Toronto 416.642.7266
> Main 1.866.411.7266
> Fax 1.888.892.7266
> Email paul at scom.ca
> 
> On 6/4/2022 6:07 AM, Marc wrote:
>> 
>> I think it is because of the domain, obviously you should only be 
>> running a website.
>> 
>>> -----Original Message-----
>>> From: dovecot <dovecot-bounces at dovecot.org> On Behalf Of
>>> hi at zakaria.website
>>> Sent: Saturday, 4 June 2022 11:15
>>> To: Dovecot <dovecot at dovecot.org>
>>> Subject: Re: Replicator: Panic: data stack: Out of memory
>>> 
>>> On 2022-06-04 02:46, Ivan Jurišić wrote:
>>>>> Ok a little more help :
>>>>> vsz_limit = 0 --> means unlimited ram for allocation, change
>>>>> this/try 2g etc pending avaliable ram.
>>>> 
>>>> I try with 524M, 1G, 2G, 4G and 8G but in any case repclicator 
>>>> proces
>>>> got crash.
>>> 
>>> Maybe there is another service process causing OOM? e.g. check clamd,
>>> antivirus DBs tend to be quite big and in updating for sometime 
>>> becomes
>>> double the size due to reloading.
>>> 
>>> Also, somtimes httpd service when using event worker, and its not 
>>> tuned
>>> properly, it will cause the OOM crash to other service along itself.
>> 

Hi Paul,

I couldnt get the context, and not sure if you've addressed me with 
confusion, since I didnt post the OOM issue, but its Ivan, anyhow thanks 
for the heads up.

I think the MX record its ok. I ran validation on internet.nl, as well 
as staging.hardenize.net and many other mail server validating services 
and none of them in terms of meeting standards, has picked anything 
wrong on the MX records, therefore I kept it as I thought was right. If 
I by any chance had the mail services running on another server, then 
indeed as you stated, invitably, I will have to point the MX record to 
it's domain and using unique domain or subdomain will turn as a 
requirement.

Also, another thought for Ivan about OOM, it seems that the memory leak 
sometimes can happen legitimately, if you have low resoucess, make sure 
your server didnt run out of resources including CPU cores, storage as 
well as RAM.

To check storage you can run: df -h.

Zakaria.