Community Discussions and Support
Mercury 4.62 Crashing

So, you're running MercuryD and MercuryE. Try to intercept the message via a global policy or filter rule, so you save a copy of each message before they get processed. Then you can later toss them into the queue (hold MercuryE first !!!!) to see if it's the list engine that causes this. I doubt that though. I'd much sooner suspect that something is causing packet/socket problems in your setup, and somehow MercuryE or MercuryD, or the loopback logic is messing things up.

If all else fails, I'd move Mercury to another machine, and use MercuryD and MercuryC, using hMailServer as the "smart host".

Nevertheless I'll see if I can't speed up my web-admin development a bit. Much of the foundation is already in place but I'm noway near a release.

<P>So, you're running MercuryD and MercuryE. Try to intercept the message via a global policy or filter rule, so you save a copy of each message before they get processed. Then you can later toss them into the queue (hold MercuryE first !!!!) to see if it's the list engine that causes this. I doubt that though. I'd much sooner suspect that something is causing packet/socket problems in your setup, and somehow MercuryE or MercuryD, or the loopback logic is messing things up.</P> <P>If all else fails, I'd move Mercury to another machine, and use MercuryD and MercuryC, using hMailServer as the "smart host".</P> <P>Nevertheless I'll see if I can't speed up my web-admin development a bit. Much of the foundation is already in place but I'm noway near a release.</P>

The previous version we were using was very stable, but this new version has crashed on us a couple times already.  The error I get is :

Faulting application mercury.exe, version 4.6.2.0, faulting module mercury.exe, version 4.6.2.0, fault address 0x00055ef9.

And now that I've restarted it, it's taking up 90+ percent of the cpu (I assume processing messages).  We use this as a secondary mail server for a mailing list only so it's not being pounded on or anything.  Any ideas on what may be causing this?

Thanks,

 Doug

<P>The previous version we were using was very stable, but this new version has crashed on us a couple times already.  The error I get is :</P><FONT size=1> <P>Faulting application mercury.exe, version 4.6.2.0, faulting module mercury.exe, version 4.6.2.0, fault address 0x00055ef9.</P> <P>And now that I've restarted it, it's taking up 90+ percent of the cpu (I assume processing messages).  We use this as a secondary mail server for a mailing list only so it's not being pounded on or anything.  Any ideas on what may be causing this?</P> <P>Thanks,</P> <P> Doug</P></FONT>

Do you happen to be using Mercury/32 with Netware bindery mode?  Do you happen to be using a filter that delivers mail using the @<path> as the username?  If so this is a known problem with Mercury/32 v4.62.  The system will crash after delivering the mail to the directory.

 

&lt;p&gt;Do you happen to be using Mercury/32 with Netware bindery mode?&amp;nbsp; Do you happen to be using a filter that delivers mail using the @&amp;lt;path&amp;gt; as the username?&amp;nbsp; If so this is a known problem with Mercury/32 v4.62.&amp;nbsp; The system will crash after delivering the mail to the directory. &lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;

In case it wasn't the Netware bindery problem, here are some more questions to help localizing the problem: How many messages were there in queue when the server crashed? Do you use any real-time anti virus software on the server? Are there any Mercury daemons in use? Did you check the disk for errors?

/Rolf 

&lt;p&gt;In case it wasn&#039;t the Netware bindery problem, here are some more questions to help localizing the problem: How many messages were there in queue when the server crashed? Do you use any real-time anti virus software on the server? Are there any Mercury daemons in use? Did you check the disk for errors? &lt;/p&gt;&lt;p&gt;/Rolf&amp;nbsp;&lt;/p&gt;

This is still happening so thought I'd follow up.  This last time there were about 125 messages in teh queue.  No, I'm not using Netware bindery.  No real time anti-virus software.  No daemons.  No disk errors that I know of, but tough to check with it being a remotely hosted production server. 

We only use this to manage a mailing list, so mail is actually processed through a different mail system.  This one retrieves mail via pop3, the distributes to the list. 

Latest error I recieved:

Faulting application mercury.exe, version 4.6.2.0, faulting module mercury.exe, version 4.6.2.0, fault address 0x00058f0b.

Any additional help would be appreciated.

Doug

 

&lt;P&gt;This is still happening so thought I&#039;d follow up.&amp;nbsp;&amp;nbsp;This last time there were about 125 messages in teh queue.&amp;nbsp; No, I&#039;m not using Netware bindery.&amp;nbsp; No real time anti-virus software.&amp;nbsp; No daemons.&amp;nbsp; No disk errors that I know of, but tough to check with it being a remotely hosted production server.&amp;nbsp; &lt;/P&gt; &lt;P&gt;We only use this to manage a mailing list, so mail is actually processed through a different mail system.&amp;nbsp; This one retrieves mail via pop3, the distributes to the list.&amp;nbsp; &lt;/P&gt; &lt;P&gt;Latest error&amp;nbsp;I recieved:&lt;/P&gt; &lt;P&gt;Faulting application mercury.exe, version 4.6.2.0, faulting module mercury.exe, version 4.6.2.0, fault address 0x00058f0b.&lt;/P&gt; &lt;P&gt;Any additional help would be appreciated. &lt;/P&gt; &lt;P&gt;Doug&lt;/P&gt; &lt;P mce_keep=&quot;true&quot;&gt;&amp;nbsp;&lt;/P&gt;

Since you have two vastly different faulting addresses in a rather short time, I've sent this to David to check upon - he's the only one who can cross-examine the addresses.

We need to know:

OS? (including build number, and service pack level)

 What else do you have running on the system besides Windows that interacts with your NIC?

&lt;P&gt;Since you have two vastly different faulting addresses in a rather short time, I&#039;ve sent this to David to check upon - he&#039;s the only one who can cross-examine the addresses.&lt;/P&gt; &lt;P&gt;We need to know:&lt;/P&gt; &lt;P&gt;OS? (including build number, and service pack level)&lt;/P&gt; &lt;P&gt;&amp;nbsp;What else do you have running on the system besides Windows that interacts with your NIC?&lt;/P&gt;

OS is Windows 2003 Server Standard, SP 2.

Also running on the server is IIS, Apache, MySQL, HMailServer, ASSP, STunnel, Serv-U FTP Server.  I think that's it. 

Thanks much,

Doug

&lt;P&gt;OS is Windows 2003 Server Standard, SP 2.&lt;/P&gt;&lt;P&gt;Also running on the server is IIS, Apache, MySQL, HMailServer, ASSP, STunnel, Serv-U FTP Server. &nbsp;I think that&#039;s it.&nbsp;&lt;/P&gt;&lt;P&gt;Thanks much,&lt;/P&gt;&lt;P&gt;Doug&lt;/P&gt;

Hmm, - a famous movie-quote yells in the back of my head:

"I wouldn't trust that overgrown pile of microchips any further than I can throw it"

IIS, hMailServer and Mercury rarely works well together in the same machine. Try to localize via f.ex. wireshark if your apps are fighting for network control. You need to be very certain that installed modules do not fight f.ex. over port 25 usage. If you install smtpsvc for IIS, it utilizes all ports unless you hack the metabase config.

&lt;P&gt;Hmm,&amp;nbsp;- a famous movie-quote yells in the back of my head:&lt;/P&gt; &lt;P&gt;&quot;I wouldn&#039;t trust that overgrown pile of microchips any further than I can throw it&quot;&lt;/P&gt; &lt;P&gt;IIS, hMailServer and Mercury rarely works well together in the same machine. Try to localize via f.ex. wireshark if your apps are fighting for network control. You need to be very certain that installed modules do not fight f.ex. over port 25 usage. If you install smtpsvc for IIS, it utilizes all ports unless you hack the metabase config.&lt;/P&gt;

I have it set up so that hMailServer is listening on Port 125, ASSP is listening on Port 25, IIS SMTP is disabled and Mercury only has the SMTP client enabled.  So I guess it could be possible that when Mercury goes to send that it could be conflicting with ASSP listening on port 25.  Seems like that would be an all or nothing sort of thing but maybe it's only a problem if mecury and ASSP both try to actively (sending/receiving vs just listening) use the port at the same time.  It just seems odd that this only started happening after upgrading to the latest version.  Did Mercury change the way the smtp client (end to end) works?  Or is it just a coincidence in timing and has nothing to do with the upgrade?  

If you can think of anything else to check out, let me know. 

Thanks,

Doug

&lt;P&gt;I have it set up so that hMailServer is listening on Port 125, ASSP is listening on Port 25, IIS SMTP is disabled and Mercury only has the SMTP client enabled. &nbsp;So I guess it could be possible that when Mercury goes to send that it could be conflicting with ASSP listening on port 25. &nbsp;Seems like that would be an all or nothing sort of thing but maybe it&#039;s only a problem if mecury and ASSP both try to actively (sending/receiving vs just listening) use the port at the same time. &nbsp;It just seems odd that this only started happening after upgrading to the latest version. &nbsp;Did Mercury change the way the smtp client (end to end) works? &nbsp;Or is it just a coincidence in timing and has nothing to do with the upgrade? &nbsp;&lt;/P&gt;&lt;P&gt;If you can think of anything else to check out, let me know.&nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Doug&lt;/P&gt;

Mercury and ASSP work well together and Mercury won't be using port 25 of your machine if it's only sending with MercuryE.

Why do you need two MTAs anyway? 

&lt;p&gt;Mercury and ASSP work well together and Mercury won&#039;t be using port 25 of your machine if it&#039;s only sending with MercuryE.&lt;/p&gt;&lt;p&gt;Why do you need two MTAs anyway?&amp;nbsp;&lt;/p&gt;

hMailServer handles normal mail and Mercury is just used to manage a mailing list.  I used to just use Mercury but at some point switched.  Now that I think about it I'm not entirely sure why, I think in part due to its ability to allow users to manage their domains and accounts via a web based system and to run as a real windows service.  It would be nice, and probably preferred to consolidate on to one system but they both offer features we use that the other doesn't.    

hMailServer handles normal mail and Mercury is just used to manage a mailing list. &nbsp;I used to just use Mercury but at some point switched. &nbsp;Now that I think about it I&#039;m not entirely sure why, I think in part due to its ability to allow users to manage their domains and accounts via a web based system and to run as a real windows service. &nbsp;It would be nice, and probably preferred to consolidate on to one system but they both offer features we use that the other doesn&#039;t. &nbsp; &nbsp;

How do you submit mail to the list engine if you're not using MercuryS?

How do you submit mail to the list engine if you&#039;re not using MercuryS?

As a side note, I agree that managing accounts externally (via web or webservice) and having Mercury run as a native service is a key future issue.

As a side note, I agree that managing accounts externally (via web or webservice) and having Mercury run as a native service is a key future issue.

The mail goes to a box in hMail, then Mercury pops it from there.  

The mail goes to a box in hMail, then Mercury pops it from there. &nbsp;

That's good to hear that some of these features may be coming to Mercury.  I'd certainly consolidate into one system if I could get everything.  

That&#039;s good to hear that some of these features may be coming to Mercury. &nbsp;I&#039;d certainly consolidate into one system if I could get everything. &nbsp;
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Cancel
Delete
Pending draft ... Click to resume editing
Discard draft