Great tip, Alan!

I had a delay of only 5 seconds in the auto restart config and changed it to
60 seconds.

Hope this will end with the reboot need.

Thank you!

Guilherme


----- Original Message ----- 
From: "Alan Fiebig" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, March 16, 2004 1:02 AM
Subject: Re: New SMTPRCV


> When smtprcv is running, if you check taskmanager and have the 'Threads'
column
> enabled to display, you will see many copies (threads) of smtprcv running,
one
> for each concurrent connection to the service.
>
> When smtprcv is stopped, either from the service manager, from the netsvc
command,
> the kill command, or any other means, you MUST wait until every thread has
stopped
> and smtprcv is no longer listed in taskmanager before restarting the
service.
>
> Failure to do so will result in exactly what you are describing above... a
service
> that is neither running nor stopped, nor that can be recovered from. The
server
> typically needs to be rebooted to correct it.
>
> I have seen it take as long as 45 seconds for all the threads to expire,
and when
> my monitoring system detected smtprcv had failed and tried immediatly
restarting it,
> I often ended up with this condition. I now have a 60 second delay built
in between
> stopping the service and trying to restart it.
>
> I no longer have the above problem... hope this might help.
>
> -Alan

This is the discussion list for the IMS Free email server software.
  To unsubscribe send mailto:[EMAIL PROTECTED]

            Delivered by Rockliffe MailSite
           http://www.rockliffe.com/mailsite
                Rock Solid Software (tm)

Reply via email to