Environment
GWAVA 4, 5, 6 All Scanners Linux
Situation
At the end of the GWAVA installation, there was the following error: java.io.IOException: /etc/init.d/gwavaman: not found Did the installation fail?
Resolution
There is only one part of the installation that failed. During the install, GWAVA will copy the start up script to the /etc/init.d directory. If that fails then fixing it is easy. Just follow these steps:
1) Copy start-up script.
In order to have rcgwavaman work, the gwavaman file needs to exist in /etc/init.d. The file needs to be copied from the GWAVA directory to that directory. Run this command to copy that file over.2) Create automatic start links.
GWAVA 4: cp -prv /opt/beginfinite/gwava/assets/bin/gwava4 /etc/init.d/gwavaman
GWAVA 5: cp -prv /opt/beginfinite/gwava/assets/bin/gwava5 /etc/init.d/gwavaman
GWAVA 6: cp -prv /opt/beginfinite/gwava/assets/bin/gwava6_default /etc/init.d/gwavaman
If the installer failed to copy the file to that directory then it is very likely that the start up links did not get created either. These start up scripts make sure that GWAVA will load and unload correctly when the server starts, stops, or restarted. Run this command to see if the start and stop scripts exist:3) Verify rcgwavaman works.
chkconfig -l gwavamanIf the result is this:
gwavaman 0:off 1:off 2:off 3:off 4:off 5:off 6:offThe start and stop links were not created. Run this command to create the start and stop scripts:
insserv gwavamanRun chkconfig -l gwavaman again to see if the links were created. If it was successful the result should be:
gwavaman 0:off 1:off 2:off 3:on 4:off 5:on 6:offGWAVA should now start and stop when the server is started or stopped.
Another part of the install script is the creation of the rcgwavaman link. This allows GWAVA to be stopped in the terminal from where it is. To verify that this link was created, run this command:4) Remove any old GWAVA startup scripts.
ls -l /sbin/*gwava*If the link was created, it should return the following:
lrwxrwxrwx 1 root root 20 May 19 2009 /sbin/rcgwavaman -> /etc/init.d/gwavamanIf the result was empty or there were no files found that matched, then the shortcut needs to be created. Run this command to create the shortcut:
ln -s /etc/init.d/gwavaman /sbin/rcgwavamanAfter running this command, verify that it works by running the command rcgwavaman status. If it works then the errors that happened during the installer have been resolved.
Enter the following command, to clean up the old startup scripts from previous versions:
rm /etc/init.d/gwavaman.*
Additional Information
This article was originally published in the GWAVA knowledgebase as article ID 1947.