Hi, just for the record, without ssl not succesfull connection with yahoo server....

Hi all, I have an installation of mercury that I began to fail about a month ago, this very constantly reboots and freezes occasionally. The modules that run on this server is Mercs, MercP, Merced and MercD. This installation already has more than a year working without problems and lately was when I began to restart.

Windows XP 32bits

Mercury v4.62 (I try with 4.72 but doesn't work)

Thanks for your help

If you can't update to Mercury 4.72 there is some serious problem in your system. Run chkdsk to verify disk integrity, make sure you have all recent Windows update patches, and make a full virus scan with an up-to-date anti-malware program.

Clear the queue and scratch directories in Mercury before restarting the program.

/Rolf

Thanks Rolf, 

I think not explain properly, I had version 4.62 installed, updated to version 4.72 but the problem continued. I was testing for a couple of days. Reinstall the version 4.62

OK. Mercury will usually crash only if something interferes with disk or memory access, so you should still run chkdsk. If you have some real-time antivirus software running, make sure it excludes all Mercury directories.

/Rolf 

What's on the screen when Mercury "freezes"? What is going on with processor activity when this happens?

Hi rolf, thanks for your help. 

Do the review with chkdsk  and clean the scratch directory but don't work. On this server I run three instances of mercury for three different services each one run in different ip's,  again commented that was running for a while without any problem.

Hi Peter, mercury "freeze" sometimes when restart and the windows is blank, closing the window (with the "X") and restart again. This is happening very very constantly, sometimes in the next 5 minutes, sometimes 10 minutes, sometimes 30 minutes, aproximately. 

If the setup with 3 instances of Mercury worked as expected before it should of course continue to do so. This leaves us with a few different possibilities:

- some hardware failure, if not disk then perhaps RAM or motherboard

- some other software that is interfering (i.e. an antivirus program)

- some specific message(s) cause Mercury to crash

If you haven't already done so (but I think you have) you should verify that there is sufficient disk space available. It might be a good idea to defragment the disk volumes as well, but I doubt that fragmentation is the cause of your problems.

Is there some other program or service running on the server? Try closing everything else down, and add one at at time to find out what might interfere.

Check Mercury log files to find any common pattern for the crashes.

Finally, if the problem hasn't been solved, get some other hardware for your mail server.

/Rolf 

Thanks Rolf for your help

- I Put the exceptions in the realtime antivirus.

- I already changed the RAM memory

- The disk have 60Gb free space.

I have to review the log files and try in another CPU, because i have more services in this machine.

I just finish a fresh install (not update) and copy all the settings from the defective mercury, for my surprise also restarting!!!!

I try the  test in another machine....

It's quite annoying when one can't pinpoint the reason for a problem like this. If you have any daemons active in Mercury you could try deactivating them as well, but if it worked normally before I don't think that will make any difference. Testing with other hardware will probably prove more fruitful.

/Rolf  

Just for the record. The error was in a module MercuryD account, after closing modules one by one MercuryD was that was causing problems. Check the configuration, and then one by one was removing the accounts until find it which was causing the problems. It is an account that begins "x_" do not know if the programming does not properly handle the escape character (\ x) or something similar ..

Greetings to all and thanks for your help

Good to hear you found the reason for the crashes. I tested adding an account with a name starting with "x_" in Mercury D, but without any surprising effects:

19:19:22 - Connecting to mercury:110 as 'x_12'
Invalid password.  - Network error; delivering anyway.

So it was probably not the account name but some other characteristics of the POP3 server that caused MercuryD to crash. Do you happen to know what server software was used at the other end?

/Rolf

Hi Rolf, the account is in yahoo (pop.mail.yahoo.com) and the local user is the username start with the "x_"

Just had the same problem with MercD in the last few days, also retrieving from a yahoo server. Had several random failures on polling (i.e. sometimes works fine sometimes not)

Note: No mail is being received from this account, it is inactive for general deliveries, but is there as a failover for another account if required.

Eventlog msg:[quote]Faulting application mercury.exe, version 4.7.1.0, faulting module mercuryd.dll, version 4.7.1.0, fault address 0x000089e8.
[/quote]

All I get in a session log is the header [:(] [quote]02:25:47.500: --- Sun Apr 25 02:25:47 2010 ---
08:26:05.593: --- Sun Apr 25 08:26:05 2010 ---
21:26:48.109: --- Sun Apr 25 21:26:48 2010 ---[/quote]

Now using just a plain connection rather than SSL, and no

recurrence of the issue so far.

Hi, looks like we have a winner YAHOO!! 

I'm trying with no SSL to see the results...