Sun Java System Web Server 7.0 Troubleshooting Guide
Contents
1. Symbol Conventions The following table explains symbols that might be used in this book TABLEP 4 Symbol Conventions Symbol Description Example Meaning Contains optional argumentsand qls l The 1 option is not required command options Contains a set of choices fora d y n The d option requires that you use either the y required command option argument or the n argument Indicates a variable reference com sun javaRoot References the value of the com sun javaRoot variable Joins simultaneous multiple Control A Press the Control key while you press the A keystrokes key Joins consecutive multiple Ctrl A N Press the Control key release it and then press keystrokes the subsequent keys gt Indicates menu item selection ina File New Templates From the File menu choose New From the graphical user interface New submenu choose Templates Accessing Sun Resources Online The http docs sun com docs sun com web site enables you to access Sun technical documentation online You can browse the docs sun com archive or search for a specific book title or subject Books are available as online files in PDF and HTML formats Both formats are readable by assistive technologies for users with disabilities To access the following Sun resources go to http www sun com Training Research Downloads of Sun products Services and solutions Support including patches2. On UNIX systems the installer and uninstaller default to command line mode if the DISPLAY environment variable has not been exported to your local machine and if X Windows is not supported Chapter 2 Installation 21 Uninstallation Problems Uninstallation Problems Asa critical first step examine the uninstallation log file Migration Problems As a critical first step examine the migration log 22 Sun Java System Web Server 7 0 Troubleshooting Guide 2007 CHAPTER 3 Startup and Access My Server Fails to Start on page 23 My Server Fails to Start When your server fails to start consider the following cases l If you have configured Web Server to run on port 80 then you will need to start the server as root user on Unix Linux However in Solaris 10 you don t need to run the Server as root to bind to port 80 or lt 1024 Execute the following commands su usr sbin usermod K defaultpriv basic net_privaddr webservd When you encounter server startup issue Server s error log or console output on UNIX Linux platforms should most likely contain the reason for the startup failure If the Web Server is configured to run in 64 bit and any of the plug ins mentioned in the magnus conf is of 32 bit then Web Server 7 0 would fail to startup throwing out error message like wrong ELF class ELFCLASS32 Similarly if you see an error message like wrong ELF class ELFCLASS64 it means
3. Top PESETA E cutus scu alc LIS 15 See if the Problem has been Solved Before eene tentent 16 Search the Product Documentation Search the Knowledge Base Y To search the Knowledge Base siciscesssscsssrssssssdveasssvsnsavacsstvatsenssvcsoeastsarcesedianvateesssscseciatsstletey Search or Participate in the Online Forum eese tentent tenentis 17 Contact SUPPOR ete deii e I erri e EEr A E Eonia Sias eds UFU Deve pete ee SERRE TTC eani 17 DCItil et EE Installation Problems Failed Installation iei diete atten cene a e da e TE ARE I REN ING 19 Existing Installation Detected ondaa anneta dd a eai eed RR da cedere 20 Defaults to Command Line Mode idea iaai direi 21 Uninstallation Problems iet dete re ORTI RR YR ARR ERE AA 22 Misration Probletis foe itat tocaba tesa etude tuned tides 22 Contents Startup and Access 5 ose oce temo pide teni e o taaeoestaaa E a e TASEA EPE ELIAN 23 My Server Pails to Start ciscssceccsciscessontsies 23 Pile Descriptor sues saie odd ertt aO DNI A PRO a dee 24 Performance 550685 nt eine cnni ei tO we Re A e UR UR PR AERE ERR DURAN 24 Administration Server And Nodes 0 ccccccessessssssssesssesssseesesssesessscssesssesesseesesseeseessessesnensesneees 25 Running Administration Server As Non Root sse tette tenente 25 Pulling Configuration Changes to the Administration Server
4. Troubleshooting Guide 2007 CHAPTER 8 Gathering Debug Data Gathering Debug Data for Sun Java System Web Server on page 37 Gathering Debug Data for Sun Java System Web Server You can use Sun Gathering Debug Data Sun GDD tool that the Sun Support Center requires to debug problems with Sun Java System Web Server See Sun Gathering Debug Data for Sun Java System Web Server at http docs sun com app docs doc 820 0429 37 38 Index A Administration interface more information about 6 D diagnosis ofa problem 12 documentation 16 error messages 14 F forum 17 investigation of a problem 13 K Knowledge Base 16 log files 15 log levels 15 o online forum 17 P pkginfo 12 rpm 12 S server log 16 showrev 12 SunSolve 17 W Windows loglevels 16 39 40
5. from Sun ONE Web Server 6 0 or 6 1 to Sun Java System Web Server 7 0 Sun Java System Web Server 7 0 Administrators Guide Performing the following administration tasks Using the Administration and command line interfaces m Configuring server preferences Using server instances Monitoring and logging server activity Using certificates and public key cryptography to secure the server m Configuring access control to secure the server Using JavaPlatform Enterprise Edition Java EE security features Deploying applications Managing virtual servers Defining server workload and sizing the system to meet performance needs Searching the contents and attributes of server documents and creating a text search interface m Configuring the server for content compression m Configuring the server for web publishing and content authoring using WebDAV Sun Java System Web Server 7 0 Developers Guide Using programming technologies and APIs to do the following m Extend and modify Sun Java System Web Server Dynamically generate content in response to client requests and modify the content of the server Sun Java System Web Server 7 0 NSAPI Developers Guide Creating custom Netscape Server Application Programmers Interface NSAPT plug ins Sun Java System Web Server 7 0 Developers Guide to Java Web Applications Implementing Java Servlets and JavaServer Pages JSP technology in Sun Java Syst
6. logs its messages into Fastcgistub log file under the Web Server s temporary directory In case of any error analyzing this file can help in debugging the problem FastCGI Requests Are Not Getting Served FastCGI request not getting served is one of the common problems l While starting the Web Server did you see the following message FCGI1000 Sun Java System Web Server 7 0 FastCGI NSAPI Plugin lt build information gt Yes FastCGI Plug in has been loaded successfully No Check the path to the plug in library within magnus conf file Check if the request mapping is correctly specified within obj conf file For more information see Administrator s Configuration File Reference Guide Check the Server Log for any error message Check the permissions for the stub binary and FastCGI applications Without sufficient permissions the plug in will fail to start the stub application Check the Fastcgistub log file for any possible error on the stub side Try executing the FastCGI application in a standalone mode and check if the application runs normally 35 Dependency Issues Dependency Issues If library dependency errors are thrown then whichever path is required to be added to LD_LIBRARY_PATH for resolving the library dependency errors in the standalone mode the same library path should be specified within obj conf file as app env parameter with LD_LIBRARY_PATH value 36 Sun Java System Web Server 7 0
7. that 32 bit Web Server is trying to load a 64 bit NSAPI plugin or vice versa While starting up the Web Server if you do not see the message info CORE3274 successful server startup on UNIX Linux platforms then it is most likely that the server has startup issues If you see the error message catastrophe 908 Server crash detected signal SIGSEGV in the server s error log file this means that Web Server s daemon has detected a crash Web Server crash during startup can happen because of various reasons including Any of the configured 3rd party NSAPI plug ins is either not following NSAPI specification Improper Server Configuration 23 File Descriptor Issues 6 Web Server requires at least 512 MB of memory to operate optimally If your system is running low on swap space then you might get error shown below warning CORE3283 stderr Error occurred during initialization of VM warning CORE3283 stderr Could not reserve enough space for object heap catastrophe CORE4005 Internal error unable to create JVM failure server initialization failed You will have to increase the swap space on your system If you are running Web Server 7 under Solaris 10 zones then you will need to increase the swap space within the global zone Note Refer to your operating system document on how to add increase swap space File Descriptor Issues Under heavy load condition Web Server may run out of file descriptors In such cases
8. the following areas Installing software Using web browsers Performing basic system administration tasks Issuing commands in a terminal window Before You Read This Book Web Server can be installed as a standalone product or as a component of Sun Java Enterprise System Java ES a software infrastructure that supports enterprise applications distributed across a network or Internet environment If you are installing Web Server as a component of Java ES you should be familiar with the system documentation at http docs sun com coll 1286 1 Web Server Documentation Set The Web Server documentation set describes how to install and administer the Web Server The URL for Web Server documentation is http docs sun com coll 1308 3 For an introduction to Web Server refer to the books in the order in which they are listed in the following table Preface TABLEP 1 Books inthe Web Server Documentation Set Documentation Title Sun Java System Web Server 7 0 Documentation Center Contents Web Server documentation topics organized by tasks and subject Sun Java System Web Server 7 0 Release Notes Late breaking information about the software and documentation Supported platforms and patch requirements for installing Web Server Sun Java System Web Server 7 0 Installation and Migration Guide Performing installation and migration tasks Installing Web Server and its various components Migrating data
9. ws7 lt location gt lt compinstance gt lt compversion gt lt compid gt lt compid gt java lt compversion gt 1 0 lt uniquename gt java lt uniquename gt lt compinstance gt 1 lt compt ype gt COMPONENT Sun Java System Web Server 7 0 Troubleshooting Guide 2007 Installation Problems EXAMPLE 2 1 Example Product Registry File Continued lt comptype gt lt location gt sun gj ws7 lt location gt lt compinstance gt lt compversion gt lt compid gt lt compid gt snmp lt compversion gt 1 0 lt uniquename gt snmp lt uniquename gt lt compinstance gt 1 comptype COMPONENT lt comptype gt lt location gt sun gj ws7 lt location gt lt compinstance gt lt compversion gt lt compid gt lt components gt lt productregistry gt Product Registry on Linux On Linux the product registry is in var opt sun install productregistry Product Registry on Windows On Windows the product registry is in C WINNT system32 The installation will fail if the Windows registry contains the HKEY_LOCAL_MACHINE SOFTWARE Sun Microsystems WebServer 7 0 entry Remove this entry using Registry Editor and you should then be able to install to the desired location Note If you get an error related to the https admserv70 service remove the following entry from the registry and try installing again HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services https admserv70 Defaults to Command Line Mode
10. you will get an error like the following 18 Dec 2005 20 01 03 failure 3014 HTTP3069 Error accepting connection PR PROC DESC TABLE FULL ERROR file descriptor table full Increase the file descriptor limit either per process or per system and restart the system Linux limits the number of file descriptors that any one process may open the default limits are 1024 per process These limits can prevent optimum performance of Web Server The open file limit is one of the limits that can be tuned with the ulimit command The command ulimit aS displays the current limit and ulimit aH displays the hard limit above which the limit cannot be increased without tuning kernel parameters For setting the limit to hard limit execute the following command ulimit n unlimited Performance Issues 24 See Sun Java System Web Server 7 0 Performance Tuning Sizing and Scaling Guide Sun Java System Web Server 7 0 Troubleshooting Guide 2007 gt CHAPTER 4 Administration Server And Nodes Running Administration Server As Non Root on page 25 Pulling Configuration Changes to the Administration Server on page 26 Making Changes to server policy File on page 26 Running Administration Server As Non Root Problem Unable to bind at port lt port_number gt The administration server and the administration nodes should be run by the same user id in Unix This is because of the following reason 1 Ifthe instan
11. 8 0x0003a0 CertificateChain chainlength 925 0x039d Certificate size 485 0x01e5 Chapter 6 Security 33 Analyzing SSL Requests 34 data saved in file cert 001 Certificate size 434 0x01b2 data saved in file cert 002 type 14 server hello done length 0 0x000000 The server picked TLS RSA AES256 CBC SHA as the cipher suite to use A session ID was sent which this client will include in subsequent requests The server also sent its certificate chain for the browser to verify ssltap saved these certificates in the files noted cert 001 and cert 002 You can examine these certificates with any tool that can parse X 509 certificates For example execute the following command openssl x509 in cert 001 text inform DER Note ssltap is a single threaded proxy server So if you issue multiple requests through it the requests will get serialized If you need to analyze a specific problem with your application that only occurs on concurrent requests through SSL try running multiple ssltap instances Sun Java System Web Server 7 0 Troubleshooting Guide 2007 CHAPTER 7 FastCGl Getting More Information on page 35 FastCGI Requests Are Not Getting Served on page 35 Dependency Issues on page 36 Getting More Information Fastcgistub is a process manager that manages the life cycle of the FastCGI application processes Fastcgistub
12. After identifying the problem you are ready to do some investigation The following topics are addressed in this section Verify System Configuration on page 14 Evaluate Messages on page 14 Examine Log Files on page 15 See if the Problem has been Solved Before on page 16 Search the Product Documentation on page 16 Search the Knowledge Base on page 16 Search or Participate in the Online Forum on page 17 Contact Support on page 17 Chapter 1 Overview 13 Seeking a Solution 14 Verify System Configuration Sometimes the most obvious solutions are overlooked and so the first step is to verify the system configuration Refer to the Sun Java System Web Server 7 0 Release Notes for the most up to date system requirements and dependencies Evaluate Messages Messages generally include information about the attempted action the outcome of the action and if applicable the cause of jeopardy or failure Types of Messages The log files contain the following general types of message entries Error These messages mark critical failures that cause status to be reported as Failed Error messages generally provide detailed information about the nature and the cause of the problem that occurred Warning These messages mark non critical failures Warning messages generally contain information about the cause and the nature of the failure and also provide possible rem
13. Guide 2007 Analyzing SSL Requests 0x00000a SSL3 RSA 3DES192EDE CBC SHA 0x000015 SSL3 DHE RSA DES56 CBC SHA 0x000012 SSL3 DHE DSS DES56 CBC SHA 0x00fefe SSL3 RSA FIPS DES CBC SHA 0x000009 SSL3 RSA DES56 CBC SHA 0x000064 TLS RSA EXPORT1024 RC4 56 SHA 0x000062 TLS RSA EXPORT1024 DES56 CBC SHA 0x000003 SSL3 RSA RC4 40 MD5 0x000006 SSL3 RSA RC2CBC40 MD5 session id challenge Oxdfb5 0x1d22 0x6562 0x34f6 0x95b9 0x668a 0x234e 0x38ea This is the SSL client hello being sent from the browser to the server Note the list of cipher suites the browser has sent This is the set of cipher suites the browser is configured to handle note that they are sorted in order of preference The server will pick one of those for the handshake if the server is not set up to handle any of these the connection will then immediately fail In the above snippet the session id is empty which tells you the browser does not have any cached SSL session with this particular server For the above request the Web Server s response is shown below lt I 1015 bytes of 1010 SSLRecord Mon Apr 10 15 49 49 2006 type 22 handshake version 3 1 length 1010 0x3f2 handshake type 2 server_hello length 70 0x000046 ServerHello server_version 3 1 random session ID Length 32 contents cipher suite 0x0035 TLS RSA AES256 CBC SHA type 11 certificate length 92
14. NER FINE and CONFIG provide information related to debugging and must be specifically enabled Instructions for doing this are contained in the Sun Java System Web Server Administrator s Guide In addition to the standard JDK log levels the Web Server has added log levels designed to map more intuitively to the Web Server log file server Log and to tightly integrate with Solaris The log levels ALERT and FATAL are specific to the Web Server and are not implemented in the JDK1 4 logging API Chapter 1 Overview 15 Seeking a Solution 16 Note For information on the event log mechanism used in the Microsoft Windows operating environment refer to the Windows help system index using the keywords Event Logging If you choose to send logs to the Windows server log file only messages with a log level of INFO WARNING SEVERE ALERT or FATAL are logged to the Windows Event Log Log Options The Administration GUI provides the following two logging options Option 1 Log stdout System out print content to the event log Option 2 Log stderr System err print content to the event log When these options are set stdout and stderr messages are written to the server Log file The event log is a syslog daemon on Solaris and Event Log on Microsoft Windows If the above options are not set Anything written to stdout or stderr that is using System out or System err will not appear in the logs Messages logge
15. Sun Java System Web Server 7 0 Troubleshooting Guide S o SUN microsystems Sun Microsystems Inc 4150 Network Circle Santa Clara CA 95054 U S A Part No 819 4293 2007 Copyright 2006 Sun Microsystems Inc 4150 Network Circle Santa Clara CA 95054 U S A All rights reserved This product or document is protected by copyright and distributed under licenses restricting its use copying distribution and decompilation No part of this product or document may be reproduced in any form by any means without prior written authorization of Sun and its licensors if any Third party software including font technology is copyrighted and licensed from Sun suppliers Parts of the product may be derived from Berkeley BSD systems licensed from the University of California UNIX is a registered trademark in the U S and other countries exclusively licensed through X Open Company Ltd Sun Sun Microsystems the Sun logo docs sun com AnswerBook AnswerBook2 Java and Solaris are trademarks or registered trademarks of Sun Microsystems Inc in the U S and other countries All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International Inc in the U S and other countries Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems Inc The OPEN LOOK and Sun Graphical User Interface was developed by Sun Microsystems Inc for its users and licensees Sun
16. acknowledges the pioneering efforts of Xerox in researching and developing the concept of visual or graphical user interfaces for the computer industry Sun holds a non exclusive license from Xerox to the Xerox Graphical User Interface which license also covers Sun s licensees who implement OPEN LOOK GUIs and otherwise comply with Sun s written license agreements U S Government Rights Commercial software Government users are subject to the Sun Microsystems Inc standard license agreement and applicable provisions ofthe FAR and its supplements DOCUMENTATION IS PROVIDED ASIS AND ALL EXPRESS OR IMPLIED CONDITIONS REPRESENTATIONS AND WARRANTIES INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE OR NON INFRINGEMENT ARE DISCLAIMED EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID 070112015821 Contents Preface m M 5 Du 11 Planning Ahead p V To back up your virtual server Identifying the Problem T Y Verifying Server Platform mieu drip rt e n da ii a e HE ERR ETE bosons 12 Seeking a SOLON ated Du EU RII EDU OUR RI RU EDI UIDERI UI G 13 Verify System Configuration zi ores dp PRU UST HOME DR CH DERI IRER UHR Urdu 14 Eyal at Messages cc umet teni dune o Ute nodum en dead e ios e th 14 Examine
17. and updates Communities for example Sun Developer Network Preface Searching Sun Product Documentation Besides searching Sun product documentation from the docs sun com web site you can use a search engine by typing the following syntax in the search field search term site docs sun com For example to search for Web Server type the following Web Server site docs sun com To include other Sun web sites in your search for example java sun com www sun com and developers sun com use sun com in place of docs sun com in the search field Third Party Web Site References Third party URLs are referenced in this document and provide additional related information Note Sun is not responsible for the availability of third party web sites mentioned in this document Sun does not endorse and is not responsible or liable for any content advertising products or other materials that are available on or through such sites or resources Sun will not be responsible or liable for any actual or alleged damage or loss caused or alleged to be caused by or in connection with use of or reliance on any such content goods or services that are available on or through such sites or resources Sun Welcomes Your Comments Sun is interested in improving its documentation and welcomes your comments and suggestions To share your comments go to http docs sun com and click Send Comments In the online form provide t
18. anual changes to the configuration files make the changes within the configuration store These changes will be reflected in the CLI and GUI and can be deployed using the deploy config command or by clicking on Deploy button in the GUI But if you make changes directly in the instance the Administration Console will show up a warning stating that there are manual modifications to the configuration files and you need to either overwrite these changes with the configuration in the configuration store or else get these changes back into the configuration store overwriting the existing configuration changes Note Always use the Administration Console or the wadm CLI to edit the settings deploy config Command Fails Question Sometimes the deploy config fails saying that a server restart is needed Why Answer When deploy config is invoked the configuration changes in the configuration store are propagated to the instances and the running servers are re configured so that the configuration changes are picked up But certain changes cannot be applied dynamically and need a server restart You will hence need to run a restart instance command in order to restart the server instances Where Can I Find wadm CLI Question Where can I find the CLI for Sun Java System Web Server 7 0 administration Answer The administration CLI is located at install root bin wadm To use the CLI you need to know Administration server hostname default i
19. ation log Installation Problems 20 Existing Installation Detected The installer maintains an entry in the product registry If installation files are removed incorrectly for example if the files are manually deleted instead of being removed by running the uninstaller the files may be gone but the Web Server entries remain in the product registry If you then try to re install to that location a message displays indicating that an existing installation has been detected even though it appears that the installation does not exist To remedy the situation go to the product registry and delete the entries manually The location ofthe product registry differs for each platform Note Again the information in this section applies only iffiles were removed in some way other than by using the Web Server uninstaller Product Registry on Solaris On Solaris the product registry is in var sadm install productregistry In the productregistry file remove the content between components and lt components gt and you should then be able to install to the location The following example shows a product registry file on Solaris EXAMPLE2 1 Example Product Registry File productregistry lt version gt 7 0 lt version gt lt components gt lt compid gt webcore lt compversion gt 1 0 lt uniquename gt webcore lt uniquename gt lt compinstance gt 1 lt compt ype gt COMPONENT lt comptype gt lt location gt sun gj
20. ces are running as part of the root process the Administration Server will not have sufficient permissions to modify the instance s configuration files ifit is not running as part ofthe root process So for the administration server to perform its job of maintaining the server instances it either needs to be part of the root process or at least the same user as that of the server instance However in Solaris 10 you don t need to run the Administration Server as root to bind to port 80 or 1024 Execute the following commands su usr sbin usermod K defaultpriv basic net privaddr webservd 25 Pulling Configuration Changes to the Administration Server Pulling Configuration Changes to the Administration Server Whenever you make manual changes to the configuration you should replicate the changes back into the Administration server repository as follows 1 Manually edit server instance s configuration files as you would do with the earlier version of Web Server 2 Start the Web Server 7 0 Administration Server See the Administrator s Guide 3 For pulling the changes back to the Administration Server repository execute the following command wadm gt pull config user admin config CONFIG NAME Note The operation may take some time depending on the configuration Note Always use the Administration Console or the wadm CLI to edit the settings Making Changes to server policy File If you are deploying yo
21. com jive index jsp cat 7 Contact Support When necessary gather together the information you have acquired and contact technical support at http www sun com service contacting Chapter 1 Overview 17 18 CHAPTER 2 Installation This chapter describes how to troubleshoot the most common installation uninstallation and migration issues This chapter contains the following sections Installation Problems on page 19 Uninstallation Problems on page 22 Migration Problems on page 22 Installation Problems As a critical first step examine the installation log files The install log file is the Sun Java System Web Server install log file located in install_dir setup directory Install log file entries contain information about the attempted action the outcome of the action and the cause of failure if applicable Entries fall into three categories INFO WARNING and ERROR For more information on the installation log see Viewing Installation Log Files in Sun Java System Web Server 7 0 Installation and Migration Guide Note Check if the DISPLAY environment variable is set properly on the machine used for installation The DISPLAY variable needs to be set to the IP address of that machine followed by a screen address which can always be assumed to be 0 0 On Linux Unix execute echo DISPLAY to find the value Failed Installation If your installation fails investigate the install
22. d with the JDK logger will appear in the logs Messages written to stdout or stderr appear with the INFO level but do not have a message ID See if the Problem has been Solved Before A good initial step is to scan this Troubleshooting Guide to see if the problem is addressed here If so select the appropriate solution Many of the solutions contain references to other documents in the Web Server document collection for additional details explanations or examples Search the Product Documentation Start by reading the Release Notes for the version of the product you are troubleshooting The documentation for this Web Server product release is available at Sun Java System Web Server 7 0 Documentation Center Search the Knowledge Base The Knowledge Base is a collection of articles on product issues that provide information helpful for troubleshooting To access the Knowledge Base Sun Java System Web Server 7 0 Troubleshooting Guide 2007 Seeking a Solution To search the Knowledge Base Goto SunSolve http sunsolve sun com pub cgi show pl target home Under SunSolve Collections click the Search Collections link Select the checkbox for the collection s to search Click Next Enter the search criteria Click Go Search or Participate in the Online Forum Browse directly in any ofthe online forums or log in and register to start posting messages The Web Server online forum is available at http swforum sun
23. ed c How is the Web Server connected to the directory server d Are web servers in a cluster or not e Wasany upgrade done If so what were source and target versions f Wasamigration done If so what were source and target versions Have any new web applications been deployed Is SSL enabled or not What database is being used Sun Java System Web Server 7 0 Troubleshooting Guide 2007 Seeking a Solution 7 What JDBC driver is being used to access the database 8 What JDK version is being used 9 Whatare the JVM heap stack and garbage collection related parameters set to 10 Whatare the JVM options 11 Whatthird party technologies are being used in the installation 12 Aretheinteroperating component versions in compliance with the compatibility matrix specified in the release notes After gathering this information Collect web server error and access log data web server instance specific Collect any Web Server stack traces Note that a fresh set of logs associated with the specific problem should be run This avoids scanning gigabytes of irrelevant log information Determine the sequence of events that occurred when the problem first appeared including any steps that may already have been taken to resolve the problem Note When you encounter a problem do not panic It is better to approach the problem more systematically by collecting the necessary system specific details Seeking a Solution
24. edies Information These messages mark normal completion of particular tasks Error Messages A problem is often accompanied by an error message that prevents the application from proceeding Insomecases the message is very clear about what is wrong and what needs to be done if anything to fix it For example the Deployment Pending link that appears on the administration console whenever an instance configuration is modified In this case the message gives clear guidance and the problem can be disregarded Sometimes an error message gives only general information about the problem or solution or suggests multiple possibilities In this case the problem is not obvious or there might be multiple things wrong You might have to consider various possibilities and perhaps a number of solutions If the proposed fix is time consuming or costly take steps to ensure that the fix is likely to be correct before actually doing anything Some error messages are either not helpful or provide little guidance In this case there is very little information to go on It is especially important to identify the exact situation that caused the error and what the symptoms are before proceeding For descriptions of all the Web Server error messages refer to the later sections in this guide Sun Java System Web Server 7 0 Troubleshooting Guide 2007 Seeking a Solution Examine Log Files A number of the Web Server subsystems c
25. em Web Server 6 Sun Java System Web Server 7 0 Troubleshooting Guide 2007 Preface TABLEP 1 Books in the Web Server Documentation Set Continued Documentation Title Contents Sun Java System Web Server 7 0 Administrator s Editing configuration files Configuration File Reference Sun Java System Web Server 7 0 Performance Tuning Tuning Sun Java System Web Server to optimize performance Sizing and Scaling Guide Sun Java System Web Server 7 0 Troubleshooting Guide Troubleshooting Web Server Related Books The URL for all documentation about Sun Java Enterprise System Java ES and its components is http docs sun com app docs prod entsys 06q4 Default Paths and File Names The following table describes the default paths and file names that are used in this book TABLEP 2 Default Paths and File Names Placeholder Description Default Value install_dir Represents the base installation directory for Web Sun Java Enterprise System Java ES installations on the Server Solaris platform opt SUNWwbserver7 Java ES installations on the Linux and HP UX platform opt sun webserver Java ES installations on the Windows platform System Drive Program Files Sun JavaES5 WebServer7 Other Solaris Linux and HP UX installations non root user user s home directory sun webserver7 Other Solaris Linux and HP UX installations root user sun webserver7 Windows all installations Sy
26. he full document title and part number The part number is a 7 digit or 9 digit number that can be found on the book s title page or in the document s URL For example the part number ofthis book is 819 4738 10 Sun Java System Web Server 7 0 Troubleshooting Guide 2007 CHAPTER 1 Overview This chapter provides a description of the tools methods and information sources available for troubleshooting the Sun Java System Web Server Server 7 0 Guidelines for evaluating and investigating a problem are included Planning Ahead on page 11 Identifying the Problem on page 12 Seeking a Solution on page 13 Planning Ahead As applications get deployed un deployed and redeployed and as you experiment with different server configuration settings there may be times when your server gets into an unstable state In such cases it is useful to have a previously saved working configuration on which to fall back This is not problem solving but rather a way to avoid problems in the first place Refer to the Web Server Administrator s Guide for complete instructions on using the CLI and GUI options Briefly however for the purposes of this Troubleshooting Guide use the following procedure to backup the virtual servers in your configuration v To back up your virtual server 1 Goto Common Tasks page The Common Tasks page is the home page when you access the administration console Fore information on acces
27. l is ssltap ssltap takes the proxy approach it serves as a simple proxy between the client and the Web Server and displays information about the connections it forwards you can also use ssltap for observing plain HTTP requests or even requests based on other protocols Assume that Web Server is running with an SSL enabled listener on port 8088 on a machine Now issue the following command ssltap l s localhost 8088 Looking up localhost Proxy socket ready and listening Note Use the l option so ssltap doesn t exit after a single request By default ssltap listens on port 1924 Now connect to https localhost 1924 with your browser You will get an output like the following snippet Connection 1 Mon Dec 10 15 49 49 2006 Connected to localhost 8088 smi alloclen 87 bytes 87 bytes of 87 Mon Apr 10 15 49 49 2006 ssl2 ClientHelloV2 version 0x03 0x01 cipher specs length 60 0x3c sid length 0 0x00 challenge length 16 0x10 cipher suites 0x000039 TLS DHE RSA AES256 CBC SHA 0x000038 TLS DHE DSS AES256 CBC SHA 0x000035 TLS RSA AES256 CBC SHA 0x000033 TLS DHE RSA AES128 CBC SHA 0x000032 TLS DHE DSS AES128 CBC SHA 0x000004 SSL3 RSA RC4 128 MD5 0x000005 SSL3 RSA RC4 128 SHA 0x00002f TLS RSA AES128 CBC SHA 0x000016 SSL3 DHE RSA 3DES192EDE CBC SHA 0x000013 SSL3 DHE DSS DES192EDE3CBC SHA 0x00feff SSL3 RSA FIPS 3DESEDE CBC SHA Sun Java System Web Server 7 0 Troubleshooting
28. reate log files and log their events to these files The primary purpose of these log files is to provide troubleshooting information Note Web Server Error Logs are the first place you should look for information when you need to troubleshoot a runtime issue For issues related to installation see the installation log files In addition to the message text a logged message provides the following information Date and time of the event Log level for the event Web Server specified log level ID or name Process identifier PID PID of the Web Server process optional Virtual server identifier VSID VSID that generated the message Message identifier MID subsystem and a four digit integer Message data The specific logs associated with each Web Server problem area are discussed in the associated chapters of this manual Log Levels The Web Server has many log levels that can be set in the Administration GUI FINEST FINER FINE CONFIG INFO WARNING SEVERE ALERT and FATAL All messages are logged when the log level is set to FINEST and only serious error messages appear if the log level is set to FATAL Note that the more detailed log levels FINEST FINER FINE can generate high volumes of log information for certain events which may make it appear at first glance that there is an error condition when in fact there is not All messages with a log level less than the default level of INFO FINEST FI
29. s localhost SSL port for the administration server default is 8989 Administration server user name default is admin Chapter 4 Administration Server And Nodes 27 Where Can Find wadm CLI 28 Administration server password Note Administration server needs to be running in order to use the CLI You can start the server by running install root admin server bin startserv Note If you are using wadm CLI on the same machine where the Administration Server is installed then you do not need to know the Administration Server s port number You are required to know the port number only if you have configured Administration Node and need to use wadm CLI to connect to a remote Administration Server Sun Java System Web Server 7 0 Troubleshooting Guide 2007 CHAPTER 5 WebDAV HTTP 403 Forbidden Error Message on page 29 HTTP 403 Forbidden Error Message After enabling WebDAV in Sun Java System Web Server 7 0 when you send a WebDAV request that needs write permissions you get 403 Forbidden error This error message means you need to set appropriate ACLs in the ACL file for that virtual server See the Administrator s Guide Note If after enabling WebDAV in Sun Java System Web Server 7 0 make sure that the directory in which WebDAV is enabled has Read and Write permissions for the user that owns webservd process like webservd or root 29 30 CHAPTER 6 Securi
30. sing the administration console refer to the Administrator s Guide 2 Select the Configuration From the Configuration Tasks page select the configuration from the drop down box Identifying the Problem Copy Virtual Servers Select the virtual server from the list and click Copy button A window will pop up Provide the new virtual server name and click OK The web applications also gets copied Identifying the Problem 12 Sun Java System Web Servers are typically deployed in complex and highly sophisticated operating environments The Sun Java System Web Server covers a broad range of technologies including Java Java Servlets XML JSP JDBC data sources and more Understanding and diagnosing complex issues involving so many disparate components requires thorough knowledge and a careful diagnostic process Gathering any or all of the following information will make it easier to classify a problem and search for solutions Note that operating system utilities such as pkginfo and showrev on Solaris and rpm on Linux are helpful in gathering system information Verifying Server Platform What are the exact version numbers of the operating system and products installed Have any patches been applied If so specify product and operating system patch numbers How is the system configured a What system resources does the system have memory disk swap space and so on b How many web servers and directory servers are install
31. sse 26 Making Changes to server policy File cc cssssccssecnseiscessossseesoseeoesicaseseascasosssdueenisossessneniedessseoseies Deployment Pending Message in Administration Console DOT Need to Save Or Deploy 52 555 onere tete ett o esed nde ct asc nns 27 Manually Editing Configuration Files eseeeeete tentent tenentes 27 deploysconfig Command Falls oec rite RE RE a 27 Where Can I Find wadin CLI 2 5 teneret a n pte i ie rie 27 WebDAW ooo ate cioe dean deed v div dida diet ev iata e dido 29 ETEEP 405 Forbidden Error Message nureen aeiae t acedae nta Od ud Hie eiie 29 Security Issuing Fest Request toan SSL Server iiia inet ho ni Ia d t b n n reden 31 Analyzing SSL SIC 32 Ij 35 Getting More Information a aee ede iet di eiie et ce De ne ieu eta i De eeu 35 FastCGI Requests Are Not Getting Served asorin ia N E ARRENE NGN 35 MVE PEN emcy BES MU T E 36 Gathering Debug Data Gathering Debug Data for Sun Java System Web Server seen 37 Sun Java System Web Server 7 0 Troubleshooting Guide 2007 Preface This guide describes the ways to troubleshoot some common issues related to Sun Java System Web Server 7 0 See Also Sun Java System Web Server 7 0 Administrator s Guide Who Should Use This Book This book is intended for Sun Java System Web Server administrators to troubleshoot the server in production environments The guide assumes familiarity with
32. stemDrive Program Files Sun WebServer7 Preface TABLEP 2 Default Paths and File Names Continued Placeholder Description Default Value instance_root Directory that contains the instance specific subdirectories The default location for instances on Solaris is var opt SUNWwbsvr7 The default location for instances on Linux and HP UX is var opt sun webserver7 The default location for instance on Windows is System Drive Program Files sun WebServer7 For Java ES installations the default location for instance on Windows is System Drive Program Files Sun JavaES5 WebServer7 Typographic Conventions The following table describes the typographic changes that are used in this book TABLEP 3 Typographic Conventions Typeface Meaning Example AaBbCc123 The names of commands files and directories and Edit your login file onscreen computer output Fieve sade eval nies machine names you have mail AaBbCc123 What you type contrasted with onscreen computer output machine names su Password AaBbCc123 A placeholder to be replaced with a real name or value The command to remove a file is rm filename AaBbCc123 Book titles new terms and terms to be emphasized note Read Chapter 6 in the User s Guide that some emphasized items appear bold online A cacheisa copy thatisstorediocaliy Do not save the file 8 Sun Java System Web Server 7 0 Troubleshooting Guide 2007 Preface
33. ty Issuing Test Request to an SSL Server on page 31 Analyzing SSL Requests on page 32 Issuing Test Request to an SSL Server While diagnosing problems between Web Server 7 0 and web browsers it is useful to analyze the requests and responses When SSL TLS is not used for capturing requests and responses between web browser and the server you can use any network capture tool such as ethereal But when SSL TLS is used for communication you can use the OpensSSL s s_client application for tapping the communication Execute the following command after successful SSL connection and enter the test HTTP request as desired openssl s client host localhost port 8080 quiet By using the same command without the quiet flag you can see information about the connection such as the server DN Certificate name and negotiated cipher suite For testing particular cipher suites check the cipher option For example openssl s client host localhost port 8080 cipher DES CBC SHA For more information see thes client man page at http www openssl org docs apps s client html 31 Analyzing SSL Requests Analyzing SSL Requests 32 Earlier method of issuing test request works well as long as you can recreate the request content manually But sometimes you need to diagnose a connection that is being used by a web browser There are a number of tools available to observe such request and response data One such too
34. ur website containing Java web applications and would like to enable security manager within the web container then you will need to edit the server instance s server policy file In this scenario Administration Server does not provide a direct command line interface or GUI to edit this server policy file But you can still perform the steps as mentioned in the previous section to make any manual edit to the server policy file Deployment Pending Message in Administration Console Question When I make changes to a configuration from the GUI I see a deployment pending message What does it mean Answer The deployment pending message indicates that there are changes to the configuration that are saved into the administration server s configuration store You need to click the Deploy button to save these changes to the instances 26 Sun Java System Web Server 7 0 Troubleshooting Guide 2007 Where Can Find wadm CLI Do Need to Save or Deploy Question What is the difference between the Save and Deploy buttons that shows up on every page in the Administration Console within a configuration Answer If you click on Save then the changes are saved only in the configuration store When you click the Deploy button the changes will be saved to the instances Manually Editing Configuration Files Question Can I make manual edits to my configuration files Will these be reflected in the CLI and GUI Answer If you need to make m
Download Pdf Manuals
Related Search