A very valid and logical point Bill,
Although "I know the directory structure is big" is a little bit of an understatement. :-) There are 3388 spool folders to check, and the problem has occurred 5 times recently = 16940 folders to examine. (thanks to the recycle bin they were all saved) However, in 4 of the 5 cases the only similarity was that there was "redirect" message sitting/stuck in the \cust folder. If this is the problem, or how it is related to high CPU usage, I don't know. How it could possibly related to WAI (other than the fact that WAI does not seem to show custom/redirect domains from the 'Alias Domains' - adom.asp - page) again I don't know. But I've removed or adjusted any 'custom', 'redirect' or 'alias' domains I was using, and will see if the problem occurs again. Regards, Scott At 01:08 PM 29/05/2002 -0700, you wrote: >You realize that when you delete the spool directory you run the risk of >losing some mail. There has to be something in the spool directories >that is causing the problem. Why don't you look through them the next >time it happens and see if you can identify what's in there that's >causing the problem. I know the directory structure is big, but it will >certainly narrow it down. As you go through it move anything suspicious >somewhere else and try xmail again, if it still has the problem keep >looking. Once you've found the offending file then maybe we can identify >what control command would be looking at it and when Davide gets back he >can see if there is some kind of race condition going on in relation to >it. > >Bill > > >---------- > >From: Quost Support[SMTP:[EMAIL PROTECTED]] > >Sent: Wednesday, May 29, 2002 3:30 AM > >To: [EMAIL PROTECTED] > >Subject: [xmail] Re: XMail + WAI = Spool + 100% CPU load > > > > > >Hi again, > > > >Its defiantly a combination of both XMail and WAI that causes the problem. > > > >2 months ago I installed XMail and WAI and had the same problem. > >Then I reinstalled XMail - no WAI - and did not have any problems for 2 > >months. > >(older versions of both XMail and WAI) > > > >Now after reinstalling the WAI, the problem is back again. > > > >However, I did not have the problem on my 'test' server - that is virtually > >identical software setup - but only a single CPU machine. > > > >I'd go with Bill's idea of running it on only one CPU, except I can't work > >out how to set the CPU affinity for a service, or how to call XMail from > >the cmd prompt (to use FireDaemon). > > > >While I guess a batchfile that restarts the service once a day - and > >deletes the spool folder would work - I'd rather find and fix the problem. > > > >Regards, > >Scott > > > > > >At 12:22 PM 29/05/2002 +0200, you wrote: > > > >>Hi, > >> > >>| I stopped running frozcache.vbs and it does not make a difference. > >> > >>therefore I think so WAI is innocent -- all other communication goes > >>trough CTRL protocol (ctrlclnt.exe). > >> > >>BTW: I am using XMail on dual processor server too with no probs... > >> > >>-- [EMAIL PROTECTED] > >> > >>- > >>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] > > > >- > >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] > > > > >- >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] - 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]
