Troubleshooting

This appendix describes how to solve common problems using Sun ONE Application Server 7 on Windows and UNIX platforms.

This appendix includes the following topics:

• Forgotten User Name or Password
• Forgotten Administration Server Port Number
• Inaccessible Port
• Could Not Initialize CGI Subsystem
• Leftover Processes, Directories, and Files
• Failed Installation of SNMP Subagent

Forgotten User Name or Password

---

If you do not remember the administrative user name that was supplied during installation, try the user name admin. This is the default user name specified in the server configuration dialog during installation.

If you still cannot determine the user name, look in the following file:

domain_config_dir/domain1/admin-server/config/admpw

This file contains the administrator's user name followed by the encrypted form of the administrative user's password.

If you do not remember the administrator's password, then you will need to uninstall and reinstall the application server.

If you do not remember the administrator's password, then you can delete the administrative domain using the delete-domain subcommand of asadmin and create a new domain with a new administrative password.

Forgotten Administration Server Port Number

---

If you do not remember the HTTP server port number of the administrative server, you can inspect the administrative server's configuration file to determine the HTTP server port number:

1. Navigate to domain_config_dir/domain1/admin-server/config/ and open the server.xml file in your favorite editor.
2. Look for the element http-listener id="http-listener-1" address="0.0.0.0" port="4848"...

In this case, port 4848 is the HTTP port number in use.

Inaccessible Port

---

If the connection was refused when attempting to contact the administrative server's administrative console application, it is likely that the administrative server is not running. Go back to the beginning of this section and check your start-up procedures and the content of the administrative server's log file to determine the reason why the server is not running.

Could Not Initialize CGI Subsystem

---

Sun ONE Application Server may require additional resources if the server won't start and you receive the following error:

[05/Aug/2002:01:12:12] SEVERE (21770): cgi_init reports: HTTP4047: could not initialize CGI subsystem

(Cgistub path /export/home/sun/appserver7/appserv/lib/Cgistub), err fork() failure [Not enough space]

Using the ulimit Command

You can use the ulimit command to determine the number of available file descriptors or set limits on the system's available file descriptors. The ulimit command displays the limits for the current shell and its descendants.

For sh shell, the command ulimit -a lists all of the current resource limits. The command ulimit -n lists the maximum file descriptor plus 1.

Increasing System Resources

On Solaris, increase the system resources by modifying the /etc/system file to include the following entries:

set rlim_fd_max=4086

set rlim_fd_cur=1024

The system will require a reboot for the new kernel parameters to take effect.

After you have set the shell resources, the application server should start.

Leftover Processes, Directories, and Files

---

After uninstalling Sun ONE Application Server 7, you may need to remove any processes, directories, registry entries or files from your system.

• UNIX
• Windows

UNIX

On UNIX, if files or processes remain on your system after uninstalling Sun ONE Application Server, perform the following steps to clean up your installation:

1. Change to your installation directory and manually remove the following:

• Sun ONE Application Server-specific entries from the product registry file, /var/sadm/install/productregistry, if the file exists.
• The following files if they are present:

/tmp/setupSDKNative

/tmp/SolarisNativeToolkit_3.0_1

2. Kill all appservd processes that may be running by typing

ps -ef | grep appservd

at the command line.

3. Remove all remaining files under the Sun ONE Application Server installation directory.

Windows

On Windows, perform the following steps to clean up your installation:

1. From the Windows Task Manager, stop the WindowsNativeToolkit processes, and remove the corresponding files.
2. Remove appserv70-admin, server1, and any other related services using the wincleanup utility.

If your Windows machine does not have the wincleanup utility, you must download it. See the Sun ONE KnowledgeBase for more information.

You can run wincleanup using the following syntax:

wincleanup service_name

The service name is the name of your instance server as it appears in brackets in the Windows Control Panel, on the Services screen. For example, the Services screen might display the following under Name:

Sun ONE Application Server 7 (server1)

In this case, the service name is server1.

For Administration Server, use admin-server as a service name.

If no service name is provided, it will delete all services associated with Sun ONE Application Server 7.

3. Open the Windows registry editor by clicking the Windows Start button, choosing Run, and typing regedit in the text box.
4. Remove the following registry folder and its content:

HKEY_LOCAL_MACHINE\SOFTWARE\Sun Microsystems\Application Server

Exit the registry editor.

5. From Windows Explorer, remove the product registry file (system_drive\WinNT\system32\productregistry), or only remove the appserver entries contained in it.
6. From Windows Explorer, delete the product files from the application server installation directory.
7. Reboot the system.

Failed Installation of SNMP Subagent

---

You must install the Windows SNMP service before you install Sun ONE Application Server 7. If you receive an error message indicating that installation of the SNMP subagent failed, the Windows SNMP service does not exist on your machine and the registration of the associated .dll file failed. You must uninstall the application server, install the Windows SNMP service, and reinstall the application server.

Unless otherwise indicated in the installation log, the rest of the product installation is unaffected by failed installation of the SNMP subagent.