HP File System Extender (FSE) FSE startup and shut-downproblems

FSE startup and shut-down problems

Description	After running the fse --stop command to shut down FSE, you may experience the following
	situation:
	- The fse command does not finish (does not return to the command prompt) in a reasonable
	time.
	- Local HSM file systems are still mounted.
	- Local FSE processes are still running.
Explanation	If a pre-stop script has been configured on this system, the above symptoms may indicate
	problems with commands in the script. Most probably one of the script commands has not
	finished.
Workaround	Identify the problematic command and reconfigure the script, as follows:
	Linux specific
	For each command that is specified in the pre-stop script (the pre_stop.sh file located in the
	local directory /opt/fse/sbin), run the following command on the local system:
	# ps -ef grep CommandName
	This will help you identify which command caused the shut-down problem.
	Windows specific
	If debugging of the FSE processes is enabled, the fse-svcprocess logs the invocation of
	each command specified in the pre-stop script. In this case, identify the problematic command
	by inspecting the fse-svc_ProcessID.logdebug file located in the local
	%InstallPath%\var\log\debug directory. Otherwise, identify the command by
	examining the process list in Windows Task Manager.
	The value of %InstallPath% depends on the choice made in the FSE installation process. It
	defaults to C:\Program Files\Hewlett-Packard\FSE.

240 Troubleshooting