Well, this fix didn't work. Here it is 45 minutes later and it's hung again.
There is no real network activity now and no server processes going on
taking up it's time. The logs are setup on the server still have the
query.log as zero and the stats.log as 1 byte with no useful information at
all. (I can copy it in if you like)
Switching it to named pipes apparently doesn't help either. What could be
causing this? This never ever happened with the previous mail server which
failed on me (hard drive failure) it was a less powerful machine, could
that be the reason? The new server is more powerful than the machine running
the sql server? This is ridiculous!
On 11/22/02 8:14 PM this was written:
> I may or may not have fixed this, we'll see later if it fails again. I'm not
> getting any ODBC errors in the sys log or any other log for that matter. I
> turned on the debugging in the System DSN and it's strange the query.log
> file never has anything in it, even after several checks. Perhaps it writes
> at intervals? I dunno.
>
> Anyway, I noticed it was accessing the server via tcp/ip rather than named
> pipes. I changed it to named pipes because that way it will force it to use
> the SAN, otherwise it will use the external line and that can get saturated
> real easily.
>
> On 11/22/02 7:51 PM this was written:
>
>> Well, CPU utilization is definitely not peaking. I have records of that.
>> And, not only that, I left for the day at 6pm EST, the machine does nothing
>> but e-mail right now and the pop3d service stopped working at 6:49pm, It's
>> now 7:50 when I came in just to get some e-mail and I noticed it was down, I
>> had to restart it.
>>
>> I would hate to have to babysit this thing all weekend.
>>
>> On 11/22/02 5:45 PM this was written:
>>
>>>> The database is an SQL server system on another computer.
>>>
>>>> I'm finding when I use the server for intensive operations, (well, not VERY
>>>> intensive for this box) like Backup restoration (tape backup system is on
>>>> this) and/or zipping and unzipping of large (700Mb) files.
>>>
>>> If CPU and drive utilization are peaking, the ODBC connection may be
>>> starved out. In addition to looking at your ODBC logs, create a dummy
>>> domain that uses the (much faster) Registry and see if it, too, does
>>> not let you log in.
>>>
>>> Until you know that the POP3 service itself is not responding, avoid
>>> the assumption that POP3D is "hanging."
>>>
>>> -Sandy
>>>
--
Thomas Deliduka
IT Manager
-------------------------
Xenocast
Street Smart Media Solutions
http://www.xenocast.com/
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
