During a normal start-up of the middle-tier services, you might find that the SAS Web Server stops responding.

Symptoms for this problem include some, or all, of the following:

• The sas.servers (or sas.servers.mid) start-up scripts stop responding on the web server.
• If you attempt to start the web server directly (using the httpdctl start command), that command execution stops responding as well.
• Even thought the command ps -ef | grep httpd indicates that the httpd process has started, the process does not respond.
• This error message might appear in the vf.ws.log file: 

The root cause of this problem is that the httpd process can stop responding when it is waiting for a Write lock. You can confirm a Write lock by submitting the following command:

If you are not sure about how to interpret the strace -p [httpd PID] output, contact SAS Technical Support.

To resolve this problem:

1. Kill the process by submitting the kill -9 command.
2. Remove all files in the SAS-configuration-directory/Lev1/Web/WebServer/logs directory.

After you perform these steps, the web server should start.

Operating System and Release Information