[THIN] Re: Server hangs
- From: "Rick Mack" <Rick.Mack@xxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Tue, 19 Oct 2004 06:58:00 +1000
Thanks Pieter,
Last time we had to do this HP had nothing to offer, ended up with a
laptop connected to a blade running the kernel debugger. It worked but
you approach is much neater.
If this is Windows Server 2003, possible reasons for hangs include
back-end systems not performing, corrupted user profiles, and handle
leaks due to the timezone hooks in Metaframe and the Appsense server
toolkit getting in each others way.
Backend server tuning comprises tuning the SMB request stack, setting
virus checking for inbound only, and if it includes a SAN, making sure
appropriate hotfixes are in place and things like the SAN request block
size are optimized. Gigabit NICs and a misconfigurd switch port (NIC on
half duplex and switch port on full, or vice versa).
Another subtle cause of performance problems on file/print servers is
file system corruption. Running a readonly chkdsk (no /f switch) over
your data volumes is a real good idea to detect any problems. In
particular, screwed up security descriptors can severely affect
read/write performance on just some parts of the file system.
Test the speed of your back end systems by doing some agressive file
copies in both directions. The speed in both directions ought to be
about the same. If it isn't, you'll have to do some work.
I've appended part of a standard policy template that we apply to ALL
backend end servers in a terminal services environment. If you're
running Great Plains, disabling oplocks is kind of essential so that's
included.
If you've had some server crashes/reboots, there is a possibility that
some of the user profiles have been corrupted. This can hang a server on
login, even with a very low number of users. It's painful, but blowing
away user profiles for server stability is a cost you may have to wear.
If you installed the Appsense server toolkit, an extra DLL hook is
installed for timezone support. HKLM\Software\Microsoft\Windows
NT\Current Version\Windows\AppInit_DLLs may have both mfaphook.dll and
tportal.dll remove mfaphook.dll or tportal.dll. They both handle client
timezones and get in each other's way causing a massive handle leak that
will result in a server hang.
Hope this helps.
And of course good luck, it might be something new ;-).
------- backend_server.adm -------------
CLASS MACHINE
CATEGORY "Back-end Server Tuning"
CATEGORY "Redirector Settings"
POLICY "SMB Redirector Parameters"
KEYNAME "SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters"
PART "Set MaxWorkitems" DROPDOWNLIST REQUIRED
VALUENAME "MaxWorkitems"
ITEMLIST
NAME "Default - 50" VALUE NUMERIC 50
NAME "Enhanced - 1024" VALUE NUMERIC 1024 DEFAULT
END ITEMLIST
END PART
PART "Set MaxMpxCt" DROPDOWNLIST REQUIRED
VALUENAME "MaxMpxCt"
ITEMLIST
NAME "Default - 210" VALUE NUMERIC 210
NAME "Enhanced - 4096" VALUE NUMERIC 4146 DEFAULT
END ITEMLIST
END PART
PART "Set MaxRawWorkItems" DROPDOWNLIST REQUIRED
VALUENAME "MaxRawWorkItems"
ITEMLIST
NAME "Default - 64" VALUE NUMERIC 64
NAME "Enhanced - 512" VALUE NUMERIC 512 DEFAULT
END ITEMLIST
END PART
PART "Set MaxFreeConnections" DROPDOWNLIST REQUIRED
VALUENAME "MaxFreeConnections"
ITEMLIST
NAME "Default - 16" VALUE NUMERIC 16
NAME "Enhanced - 100" VALUE NUMERIC 100 DEFAULT
END ITEMLIST
END PART
PART "Set MinFreeConnections" DROPDOWNLIST REQUIRED
VALUENAME "MinFreeConnections"
ITEMLIST
NAME "Default - 8" VALUE NUMERIC 8
NAME "Enhanced - 32" VALUE NUMERIC 32 DEFAULT
END ITEMLIST
END PART
END POLICY ; smb
POLICY "Opportunistic Locking"
KEYNAME "SYSTEM\CurrentControlSet\Services\Lanmanserver\Parameters"
PART "Disable OpLocks" CHECKBOX
VALUENAME "EnableOplocks"
VALUEON NUMERIC 0
VALUEOFF NUMERIC 1
END PART
END POLICY ; oplocks
END CATEGORY ; redirector settings
END CATEGORY ; Server Tuning
---------------------
regards,
Rick
Ulrich Mack
Volante Systems Ltd
18 Heussler Terrace, Milton 4064
Queensland Australia.
Ph: +61 7 3246 7704
email: rmack@xxxxxxxxxxxxxx
web: www.volante.com.au
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx
[mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf Of Pieter Mussche
Sent: Monday, 18 October 2004 11:22 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Server hangs
Dear All,
I am experiencing the same problems on my blades. Also HP Blades
bl20p g2 with win 2003, citrix and appsense.
I opened a case at Microsoft and indeed they are very eager for
memory dump file.
Like allready said this is not easy to do on a blade. But!!! I
think I found something.
It worked with a server that was having no problems at that
time, but i am quit sure it will work on a non responding server also.
These are rhe steps to create the memory dump
1. Go to the ILO for the concerning server
2. Under virtual devices , choose virtual serial port
3. Press enter once to receive the "SAC" prompt
4. type crashdump en press enter.
5. This generates a blue screen and therefore a memory.dmp file
if windows is configured to do that.
I am now waiting for the first blade to hang and then I am
hoping that microsoft finds something in the dumpfile
Regards
Pieter Mussche
#####################################################################################
This e-mail, including all attachments, may be confidential or privileged.
Confidentiality or privilege is not waived or lost because this e-mail has been
sent to you in error. If you are not the intended recipient any use,
disclosure or copying of this e-mail is prohibited. If you have received it in
error please notify the sender immediately by reply e-mail and destroy all
copies of this e-mail and any attachments. All liability for direct and
indirect loss arising from this e-mail and any attachments is hereby disclaimed
to the extent permitted by law.
#####################################################################################
Other related posts:
