[xmail] Re: XMailServer 1.25 Memory Footprint
On Thu, 24 Apr 2008, Vinny Wadding wrote: Absolutely... It seemed to make no difference if the filters were running o= r not. I tried it both ways around. Results were the same when submittin= g mails for that domain - the buffers/cache would immediately start increas= ing where as the memory that xmail was using did not significantly change. A, you meant Buffer+Cache. That is virtually free memory. The OS, instead of leaving memory pages sitting unused, use them for buffers. Once memory pressure start, those pages are automatically reclaimed by the allocator. Don't worry about buffer+cache, it's good to go ;) - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: XMailServer 1.25 Memory Footprint
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On= Behalf Of Davide Libenzi Sent: 21 April 2008 21:54 To: xmail@xmailserver.org Subject: [xmail] Re: XMailServer 1.25 Memory Footprint On Mon, 21 Apr 2008, Vinny Wadding wrote: Hi guys, I have just installed XMail 1.25 and am not seeing some odd behaviour from it. It has taken me a while to try and track down what is happening, but here it is from what I can find. The new server is put live and works extremely well.After several hours, I get alerts saying that the system memory is exhausted.The memory footprint of XMail stays consistent at about 85mb - the rest of the system memory is all allocated to Buffers and Cache. There is virtually no swap space used, but a higher than expected load average on the system. I have taken the server offline so there is no traffic running to it. On a reboot the memory is released, but as soon XMail is restarted the Cache and Buffers climb back up and use all the memory again. That would eliminate an external influence on the server, and suggest something that is already on the XMail queue. I wiped all frozen spool from the server and restarted again. Same as above, the server released the memory but as soon as XMail started it started to grab all free memory for Cache and Buffers. This would suggest something that XMail is still trying to process? I trawled the spool queue and found several mails that appeared to be stuck. It would appear that XMail would repeatedly try and process these, it would not as I could see spool files being created and removed as it goes thorough the motions. I have downloaded the spool queues and had a look through them offline, it would appear that the mails that are causing an issue on this server are coming from badly set up domains. I ran these domains through dnsstuff to see how they were set up= .. One of the domains was set up with no MX record and no A records. Even when manually submitting test mail for this domain, it would be accepted and then causes XMail to overreact. The rest of the domains I saw on the spool queue had minor anomalies, but when submitting manual mails via telnet for these domains it did not seem to cause the same reaction as the domain with no zone information. Obviously wiping the spool queue and rebuilding it from the source example resolves the issue and the behaviour returns to normal. Is this a known behaviour or feature in 1.25? Has anyone else seen this happening? Is there any way of being able to stop this behaviour? I don't think so. The eat all the server's memory feature will not come out till 1.26 :) Which OS is that? Why don't you post one of your telnet transactions that are creating problems? Talking about some domains and some emails is a bit vague, since it does not allow anyone to replicate your box results. This is my XMail BTW: VSZ RSS 18676 5184 - Davide Damn, I was hoping I had missed an option in server.tab. ;-) I only mentioned the memory usage above to clarify that I didn't look like = it I was any leak in XMail itself. Obviously, this is a new server and at = the moment only test traffic is running though it before it goes fully live= .. When that happens the memory usage will, no doubt, go up accordingly. The server it is running on is a Fedora8 X64 Server, with 4gb of memory. I= have two perl filters running. A pre-smtp spf filter and an inbound/outb= ound virus scan. The telnet sessions to the server were just standard ones - no errors were = reported at all. The address I was seeing mails coming from and even when I submitted them d= irectly were: [EMAIL PROTECTED] The mails were being sent to an account that does not exist on my server, s= o would the process of trying to send the NDR have caused a loop given that= their dns seemed to be corrupt at the time? I have checked the domain again and it looks like they have fixed what ever= issues there were having. I have the reports from DNSstuff, I can send them direct to people or send = to the list (not sure if I can mass mail attachments to people) if people a= re interested in the errors from their domain. I didn't mention the emails or domains specifically before, as it seemed ba= d etiquette to just post it onto a forum and saying I was getting bad mails= from them. Registered in England and Wales. Registration Number: 3472519. Registered Office: 1 The Green, Richmond, Surrey, TW9 1PL, United Kingdom This e-mail and any attachment may contain confidential and privileged mate= rial intended for the addressee only. If you are not the addressee, you are= notified that no part of the e-mail or any attachment may be disclosed, co= pied or distributed, and that any other action related to this e-mail or at= tachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immedia= tely by return e
[xmail] Re: XMailServer 1.25 Memory Footprint
On Thu, 24 Apr 2008, Vinny Wadding wrote: Damn, I was hoping I had missed an option in server.tab. ;-) I only mentioned the memory usage above to clarify that I didn't look like = it I was any leak in XMail itself. Obviously, this is a new server and at = the moment only test traffic is running though it before it goes fully live= .. When that happens the memory usage will, no doubt, go up accordingly. The server it is running on is a Fedora8 X64 Server, with 4gb of memory. I= have two perl filters running. A pre-smtp spf filter and an inbound/outb= ound virus scan. I assume you did verify that it was actually XMail using the memory, and not the filters (especially the AV one)? - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: XMailServer 1.25 Memory Footprint
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On= Behalf Of Davide Libenzi Sent: 24 April 2008 16:20 To: xmail@xmailserver.org Subject: [xmail] Re: XMailServer 1.25 Memory Footprint On Thu, 24 Apr 2008, Vinny Wadding wrote: Damn, I was hoping I had missed an option in server.tab. ;-) I only mentioned the memory usage above to clarify that I didn't look lik= e =3D it I was any leak in XMail itself. Obviously, this is a new server and a= t =3D the moment only test traffic is running though it before it goes fully li= ve=3D .. When that happens the memory usage will, no doubt, go up accordingly. The server it is running on is a Fedora8 X64 Server, with 4gb of memory. = I=3D have two perl filters running. A pre-smtp spf filter and an inbound/ou= tb=3D ound virus scan. I assume you did verify that it was actually XMail using the memory, and not the filters (especially the AV one)? - Davide - Absolutely... It seemed to make no difference if the filters were running o= r not. I tried it both ways around. Results were the same when submittin= g mails for that domain - the buffers/cache would immediately start increas= ing where as the memory that xmail was using did not significantly change. It ok when submitting mails for any other domain. Which is why I suspected= it might be something to do with this domains setup at the time. *shrugs* It was the only thing that seemed to make sense. Registered in England and Wales. Registration Number: 3472519. Registered Office: 1 The Green, Richmond, Surrey, TW9 1PL, United Kingdom This e-mail and any attachment may contain confidential and privileged mate= rial intended for the addressee only. If you are not the addressee, you are= notified that no part of the e-mail or any attachment may be disclosed, co= pied or distributed, and that any other action related to this e-mail or at= tachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immedia= tely by return e-mail, and delete this message. QSoft Consulting Ltd., its = subsidiaries and/or its employees shall not be liable for the incorrect or = incomplete transmission of this e-mail or any attachments, or responsible f= or any delay in receipt. Any opinions expressed in this message are those o= f the author only and do not necessarily represent the views of QSoft Consu= lting Ltd. - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: XMailServer 1.25 Memory Footprint
On 24 Apr 2008 at 14:46, Vinny Wadding wrote: Damn, I was hoping I had missed an option in server.tab. ;-) I only mentioned the memory usage above to clarify that I didn't look like = it I was any leak in XMail itself. Obviously, this is a new server and at = the moment only test traffic is running though it before it goes fully live= .. When that happens the memory usage will, no doubt, go up accordingly. The server it is running on is a Fedora8 X64 Server, with 4gb of memory. I= have two perl filters running. A pre-smtp spf filter and an inbound/outb= ound virus scan. The telnet sessions to the server were just standard ones - no errors were = reported at all. Only a home user but several domains and host for a few friends. I've had issues indirectly from XMail and filters eating up memory but in first case it was too many instances of perl and most recently my AV filter causing load by false alarming on a particular message then due to same problem catching each warning email sent. First problem was resolved by limiting number of scripts running at same time to just two (above four caused a rapidly increasing load to 100%cpu when my batch of a dozen test emails hit the server). Second problem back in January wasn't investigated and I disabled AV scan, cleaned out the 30k+ emails in the queue and forgot about it. Later I cloned then reconfigured same setup onto another server but for another domain and had exact same problem when AV enabled. After clearing spool and update of AV the problem hasn't reappeared on either system. It may have been a corrupted AV update in first place. Another possibility is a race when scanning and AV update coincide so I modified both update and filter to minimise this (my perl skill is not good enough to eliminate rather than minimise). David - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: XMailServer 1.25 Memory Footprint
On Mon, 21 Apr 2008, Vinny Wadding wrote: Hi guys, I have just installed XMail 1.25 and am not seeing some odd behaviour from it. It has taken me a while to try and track down what is happening, but here it is from what I can find. The new server is put live and works extremely well.After several hours, I get alerts saying that the system memory is exhausted.The memory footprint of XMail stays consistent at about 85mb - the rest of the system memory is all allocated to Buffers and Cache. There is virtually no swap space used, but a higher than expected load average on the system. I have taken the server offline so there is no traffic running to it. On a reboot the memory is released, but as soon XMail is restarted the Cache and Buffers climb back up and use all the memory again. That would eliminate an external influence on the server, and suggest something that is already on the XMail queue. I wiped all frozen spool from the server and restarted again. Same as above, the server released the memory but as soon as XMail started it started to grab all free memory for Cache and Buffers. This would suggest something that XMail is still trying to process? I trawled the spool queue and found several mails that appeared to be stuck. It would appear that XMail would repeatedly try and process these, it would not as I could see spool files being created and removed as it goes thorough the motions. I have downloaded the spool queues and had a look through them offline, it would appear that the mails that are causing an issue on this server are coming from badly set up domains. I ran these domains through dnsstuff to see how they were set up. One of the domains was set up with no MX record and no A records. Even when manually submitting test mail for this domain, it would be accepted and then causes XMail to overreact. The rest of the domains I saw on the spool queue had minor anomalies, but when submitting manual mails via telnet for these domains it did not seem to cause the same reaction as the domain with no zone information. Obviously wiping the spool queue and rebuilding it from the source example resolves the issue and the behaviour returns to normal. Is this a known behaviour or feature in 1.25? Has anyone else seen this happening? Is there any way of being able to stop this behaviour? I don't think so. The eat all the server's memory feature will not come out till 1.26 :) Which OS is that? Why don't you post one of your telnet transactions that are creating problems? Talking about some domains and some emails is a bit vague, since it does not allow anyone to replicate your box results. This is my XMail BTW: VSZ RSS 18676 5184 - Davide - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
[xmail] Re: XMailServer 1.25 Memory Footprint
xmail using 85MB ram ? Here on a win2000 server, it take up 15MB max (on low traffic it use 7MB average) !?!? Could you give us some information about your server setup ? (os, version, ram, ...) and xmail CMD_LINE parameters ? And some 'bad' destination domains to have some real example (the no mx/no a domain and some of the others) ? Do you use some 'smart-dns' host setting in server.tab file ? And did you implement some 'filters' in xmail ? For the 'no mx nor A' dns zone domain problem, it's strange the mail remaind in the queue for retries as Davide changed the rules for them and xmail should simply not retry at all and immediatly return an NDR. For the 'bad dns zone setup', I don't know xmail exact rules to retry or immediatly return a ndr. Francis -Message d'origine- De: [EMAIL PROTECTED] A: xmail@xmailserver.org Date: 21/04/08 19:51 Objet: [xmail] XMailServer 1.25 Memory Footprint Hi guys, I have just installed XMail 1.25 and am not seeing some odd behaviour from it. It has taken me a while to try and track down what is happening, but here it is from what I can find. The new server is put live and works extremely well.After several hours, I get alerts saying that the system memory is exhausted.The memory footprint of XMail stays consistent at about 85mb - the rest of the system memory is all allocated to Buffers and Cache. There is virtually no swap space used, but a higher than expected load average on the system. I have taken the server offline so there is no traffic running to it. On a reboot the memory is released, but as soon XMail is restarted the Cache and Buffers climb back up and use all the memory again. That would eliminate an external influence on the server, and suggest something that is already on the XMail queue. I wiped all frozen spool from the server and restarted again. Same as above, the server released the memory but as soon as XMail started it started to grab all free memory for Cache and Buffers. This would suggest something that XMail is still trying to process? I trawled the spool queue and found several mails that appeared to be stuck. It would appear that XMail would repeatedly try and process these, it would not as I could see spool files being created and removed as it goes thorough the motions. I have downloaded the spool queues and had a look through them offline, it would appear that the mails that are causing an issue on this server are coming from badly set up domains. I ran these domains through dnsstuff to see how they were set up. One of the domains was set up with no MX record and no A records. Even when manually submitting test mail for this domain, it would be accepted and then causes XMail to overreact. The rest of the domains I saw on the spool queue had minor anomalies, but when submitting manual mails via telnet for these domains it did not seem to cause the same reaction as the domain with no zone information. Obviously wiping the spool queue and rebuilding it from the source example resolves the issue and the behaviour returns to normal. Is this a known behaviour or feature in 1.25? Has anyone else seen this happening? Is there any way of being able to stop this behaviour? Registered in England and Wales. Registration Number: 3472519. Registered Office: 1 The Green, Richmond, Surrey, TW9 1PL, United Kingdom This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. QSoft Consulting Ltd., its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, or responsible for any delay in receipt. Any opinions expressed in this message are those of the author only and do not necessarily represent the views of QSoft Consulting Ltd. - To unsubscribe from this list: send the line unsubscribe xmail in the body of a message to [EMAIL PROTECTED] For general help: send the line help in the body of a message to [EMAIL PROTECTED]
