Re: Odd semi-crash or hang
- From: "Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 1 Aug 2005 10:54:38 -0400
Then all's well with the server now? I hope that's the case.
For temperature, if you're referring to the server's internal temperature,
40 C is fine - mine is running in the low 30's except for the CPU at 47. If
that's the room temperature, heat could definitely be the cause of your
problem - the generally accepted wisdom, at least in my mind, is that
servers should be in areas that do not exceed 90 F (about 32 C).
"CO-DBA-SC-EL" <dx6490@xxxxxxxxx> wrote in message
news:%23NoolsVlFHA.2860@xxxxxxxxxxxxxxxxxxxxxxx
> "Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote in
> message news:O06zScTlFHA.3256@xxxxxxxxxxxxxxxxxxxxxxx
>> What I do is to click on the Microsoft Exchange System Attendant service
>> and click the restart icon. That'll restart most of the Exchange
>> services - a list will pop up when you click restart. You're right, MTA
>> would normally be disabled on SBS.
>>
>> Have you been able to narrow down the original problem at all? Is it
>> possible that the server was shut down or otherwise hung during the time
>> when no entries were logged? Do you know why computer management is
>> blocked? Can this be a power or heat issue?
>
> No new clue. Restarting Microsoft Exchange System Attendant did not fix
> the email queue problem, but an orderly shutdown and restart resulted in
> the queue being processed after10 minutes later.
> The graph of the UPS monitoring service shows a "gap" of several hours but
> no sag or drop just before the gap. Looks like the monitoring service
> simply stopped. AFAIK the CPU and system temperatures have been way below
> critical level. On this very hot day without AC they are still not
> reaching above 40 degrees C. Good thing this SBS was *behind* another
> firewall/router and VPN server, who the heck knows what else stopped
> working right while enough was still working to fool a LAN user.
> Ironically, it kept responding to pings and to at least *some* file
> sharing requests all along. Of course no notifications were emailed out,
> so it was sheer accident that we noticed something was awry.
>
>> "CO-DBA-SC-EL" <dx6490@xxxxxxxxx> wrote in message
>> news:u4ogR%23KlFHA.2608@xxxxxxxxxxxxxxxxxxxxxxx
>>> Well, thanks to http://support.microsoft.com/?id=885685 and then a
>>> little more guessing
>>> I found the "lost" emails stuck in C:\Program
>>> Files\Exchsrvr\Mailroot\vsi 1\Queue
>>>
>>> How do I get them out of there? Another reboot? Is there a one-command
>>> script to shut down and restart Exchange server without a reboot?
>>> Checking the status, it shows all Exchange services running except the
>>> MTA one which I understand is not used in SBS2003.
>>>
>>> C_O
>>>
>>> "CO-DBA-SC-EL" <dx6490@xxxxxxxxx> wrote in message
>>> news:%23GV%23qxKlFHA.4000@xxxxxxxxxxxxxxxxxxxxxxx
>>>> Help, please.
>>>>
>>>> From bad to worse...
>>>>
>>>> The Pop3 Connector has been pulling messages off the remote mail host
>>>> POP3 servers all day, but not putting those messages into the
>>>> recipients' mailboxes. Looking at the troubleshooting tab on the POP3
>>>> connector it shows 0 pending message. I just tested this -- sent two
>>>> messages from an outside account to two different outside mail hosts,
>>>> watch them disappear from the mail host POP3 server as I was manually
>>>> triggering the POP3 Connector synchronization. The messages seem to
>>>> have disappeared in a bit bucket. Is there *any* place where I might be
>>>> able to find those messages? And how the heck does one fix this?
>>>>
>>>> TIA
>>>>
>>>> C_O
>>>>
>>>> "CO-DBA-SC-EL" <dx6490@xxxxxxxxx> wrote in message
>>>> news:%23xf31KGlFHA.3968@xxxxxxxxxxxxxxxxxxxxxxx
>>>>> SBS 2003 Standard, SP1, TrendMicro suite.
>>>>> The server is at another location. It is on a VPN provided by another
>>>>> device, so I have access to that network. I can ping the SBS box. From
>>>>> a workstation on the domain, I can browse the shared folders. But some
>>>>> time during the night the SBS stopped responding to web remote access
>>>>> (OWA, RWW). Trying to reach it through remote desktop, my local remote
>>>>> desktop window opens but just sits there with a black client area and
>>>>> no error message. This is new--last time I had a remote control
>>>>> session via Remote Desktop was last night, looking at logs.
>>>>> I won't be able to get over there until tonight, and they need their
>>>>> email, so I will have someone at the site just hit reset on the box.
>>>>> The box is running without keyboard or monitor, so I can't ask them to
>>>>> look at the screen to tell me what's going on. Hopefully the system
>>>>> will reboot into a working state.
>>>>> Question: Without the remote desktop, is there any way to figure out
>>>>> what is going on before rebooting? Since the file system seems to be
>>>>> running fine, maybe by logging in as the domain admin at another
>>>>> workstation and looking at the logs files? Has anyone else experienced
>>>>> a similar situation?
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
.
- Follow-Ups:
- Re: Odd semi-crash or hang
- From: CO-DBA-SC-EL
- Re: Odd semi-crash or hang
- References:
- Re: Odd semi-crash or hang
- From: CO-DBA-SC-EL
- Re: Odd semi-crash or hang
- From: CO-DBA-SC-EL
- Re: Odd semi-crash or hang
- From: Dave Nickason [SBS MVP]
- Re: Odd semi-crash or hang
- From: CO-DBA-SC-EL
- Re: Odd semi-crash or hang
- Prev by Date: Re: 4 GB Memory - What Switches I need in Boot.ini
- Next by Date: RE: Does the max mailbox size change?
- Previous by thread: Re: Odd semi-crash or hang
- Next by thread: Re: Odd semi-crash or hang
- Index(es):
Relevant Pages
|
