Scan Engine does not start and appears like the /etc/init.d/symcscan script is stuck.
You may see during the install that you do not get prompted for the Java path and the install completes but the Scan Engine service fails to startup.
The case was related to how the symcscan script starts by using su with a dash after it so that the process can be started as a particular user which is given during the installation. With the dash this means not only to run as this user but to also load that user's environment. The user's .profile had lines for environment variables which was fine but they also had a line that said /sbin/ksh that would load another ksh shell. So our script becomes paused and will not complete until this shell is quit so that control goes back to to the calling shell.
There seems to be in issue with using the Java 1.6.0_37 build on a Red Hat Linux install of Scan Engine where the Scan Engine service fails to start up after installing.
Solution 1 - Edit the .profile script for the user so that it does not start additional shells.
Solution 2 - Edit the /etc/init.d/symcscan script so that near the bottom each of the su - lines are just su. For example if you see:
su - $User -c "$Program.sh start"
change it to:
su $User -c "$Program.sh start"
When you run without the dash it still runs as that user but with current environment.
If you see that the Scan Engine service fails to start after an install then verify the version of Java. If you see that the Java build is 1.6.0_37 then remove it and install a higher version or a version below the 1.6.0_37.
Rate this Article
This is machine translated content
Login to Subscribe
Please login to set up your subscription.
Didn't find the article you were looking for? Try these resources.