Community Discussions and Support
Mercury does not start: Abnormal terminations continued after attempted recovery - exiting.

Good evening

Thank you very much for your fast answer & your description of steps I can do! I'll go an test it…

Kind regards,
Thomas

<P>Good evening</P> <P>Thank you <STRONG>very</STRONG> much for your fast answer & your description of steps I can do! I'll go an test it…</P> <P>Kind regards, Thomas</P>

Good afternoon

We used Mercury/32 for some years and never had problems, but suddenly Mercury
crashes at startup and in loader.log we have:

07-06-28.0813: Mercury/32 Loader Started
07-06-28.0813: Restarted Mercury after apparent abnormal termination
07-06-28.0813: …
07-06-28.0813: Restarted Mercury after apparent abnormal termination
07-06-28.0813: Too many abnormal terminations in time period - attempting recovery.
07-06-28.0813: No queue files to quarantine - no recovery performed.
07-06-28.0813: Recovery complete - attempting to restart Mercury.
07-06-28.0813: Restarted Mercury after apparent abnormal termination
07-06-28.0813: …
07-06-28.0814: Abnormal terminations continued after attempted recovery - exiting.
07-06-28.0814: Mercury/32 Loader shutting down.  

And Mercury/32 does not start - without any information about a problem

Then I re-installed Mercury/32 and upgraded to the new releade 4.51. Everything
worked fine for 2 days and then we got the same problem & errors again:
Mercury does not start and does not say why.

» Is there a way to get more informations about start-problems?

Thanks a lot in advance!,

kind regards,
Thomas

<P>Good afternoon</P> <P>We used Mercury/32 for some years and never had problems, but suddenly Mercury crashes at startup and in loader.log we have:</P> <P><EM>07-06-28.0813: Mercury/32 Loader Started 07-06-28.0813: Restarted Mercury after apparent abnormal termination 07-06-28.0813: … 07-06-28.0813: Restarted Mercury after apparent abnormal termination 07-06-28.0813: Too many abnormal terminations in time period - attempting recovery. 07-06-28.0813: No queue files to quarantine - no recovery performed. 07-06-28.0813: Recovery complete - attempting to restart Mercury. 07-06-28.0813: Restarted Mercury after apparent abnormal termination 07-06-28.0813: … 07-06-28.0814: Abnormal terminations continued after attempted recovery - exiting. 07-06-28.0814: Mercury/32 Loader shutting down.  </EM></P> <P>And Mercury/32 does not start - <STRONG>without any information about a problem</STRONG>…</P> <P>Then I re-installed Mercury/32 and upgraded to the new releade 4.51. Everything worked fine for 2 days and then we got the same problem & errors again: Mercury does not start and does not say why.</P> <P><STRONG>» Is there a way to get more informations about start-problems?</STRONG></P> <P>Thanks a lot in advance!,</P> <P>kind regards, Thomas</P>

[quote user="schittli"]

Good afternoon

We used Mercury/32 for some years and never had problems, but suddenly Mercury
crashes at startup and in loader.log we have:

07-06-28.0813: Mercury/32 Loader Started
07-06-28.0813: Restarted Mercury after apparent abnormal termination
07-06-28.0813: …
07-06-28.0813: Restarted Mercury after apparent abnormal termination
07-06-28.0813: Too many abnormal terminations in time period - attempting recovery.
07-06-28.0813: No queue files to quarantine - no recovery performed.
07-06-28.0813: Recovery complete - attempting to restart Mercury.
07-06-28.0813: Restarted Mercury after apparent abnormal termination
07-06-28.0813: …
07-06-28.0814: Abnormal terminations continued after attempted recovery - exiting.
07-06-28.0814: Mercury/32 Loader shutting down.  

And Mercury/32 does not start - without any information about a problem

Then I re-installed Mercury/32 and upgraded to the new releade 4.51. Everything
worked fine for 2 days and then we got the same problem & errors again:
Mercury does not start and does not say why.

» Is there a way to get more informations about start-problems?

Thanks a lot in advance!,

kind regards,
Thomas

[/quote]

 

The multiple restarts are usually caused when the mercury.ini file  has been zeroed out for some reason.  The most common reason is that Mercury/32 can't open it either because it lost the connection to the drive or your anti-virus software is fighting Mercury/32 for the files.  Some things to you might want to do:

1.  Replace mercury.ini with the mercury.bak or mercury.bk1 and try again.

2.  Clear the queue of mail to be processed.  Do not think this is your problem since the program says the queue is empty.

3.  Exclude all the Mercury/32 directories from scanning.

4.  Make sure that Mercury/32 in installed to the local hard drive, especially the queue, temp and scratch directories.  You can use supplementary queues on the lan if running with Pegasus Mail.  Mailbox directories may be on a lan without causing a problem.  

 



 

 

[quote user="schittli"]<p>Good afternoon</p> <p>We used Mercury/32 for some years and never had problems, but suddenly Mercury crashes at startup and in loader.log we have:</p> <p><i>07-06-28.0813: Mercury/32 Loader Started 07-06-28.0813: Restarted Mercury after apparent abnormal termination 07-06-28.0813: … 07-06-28.0813: Restarted Mercury after apparent abnormal termination 07-06-28.0813: Too many abnormal terminations in time period - attempting recovery. 07-06-28.0813: No queue files to quarantine - no recovery performed. 07-06-28.0813: Recovery complete - attempting to restart Mercury. 07-06-28.0813: Restarted Mercury after apparent abnormal termination 07-06-28.0813: … 07-06-28.0814: Abnormal terminations continued after attempted recovery - exiting. 07-06-28.0814: Mercury/32 Loader shutting down.  </i></p> <p>And Mercury/32 does not start - <b>without any information about a problem</b>…</p> <p>Then I re-installed Mercury/32 and upgraded to the new releade 4.51. Everything worked fine for 2 days and then we got the same problem & errors again: Mercury does not start and does not say why.</p> <p><b>» Is there a way to get more informations about start-problems?</b></p> <p>Thanks a lot in advance!,</p> <p>kind regards, Thomas</p><p>[/quote]</p><p> </p><p>The multiple restarts are usually caused when the mercury.ini file  has been zeroed out for some reason.  The most common reason is that Mercury/32 can't open it either because it lost the connection to the drive or your anti-virus software is fighting Mercury/32 for the files.  Some things to you might want to do: </p><p>1.  Replace mercury.ini with the mercury.bak or mercury.bk1 and try again.</p><p>2.  Clear the queue of mail to be processed.  Do not think this is your problem since the program says the queue is empty.</p><p>3.  Exclude all the Mercury/32 directories from scanning.</p><p>4.  Make sure that Mercury/32 in installed to the local hard drive, especially the queue, temp and scratch directories.  You can use supplementary queues on the lan if running with Pegasus Mail.  Mailbox directories may be on a lan without causing a problem.  </p><p> </p><p>  </p><p> </p>
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 ?
Pending draft ... Click to resume editing
Discard draft