No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


Starting the TOS Fails Because of Certain Common Causes

Publication Date:  2012-07-25 Views:  63 Downloads:  0
Issue Description
In the networking mode of the DB, NCP and TOS, the TOS is a platform for sending basic test tasks. During a test, the engineer uses the portable computer to open the TOS on the web page. The web page displays a message indicating that an error occurs. The TOS interface cannot be displayed and thus test tasks cannot be sent. 
Alarm Information
The IE displays a message similar to the following:
Cannot display the page.
The page you are looking for is temporarily unavailable. The Web site might be experiencing technical difficulties, or you may need to adjust your browser settings. 
Handling Process
1. The Oracle database is abnormal.
Run the su � oracle command to check the database.
Run the sqlplus username/password@service name command to log in to the Oracle database.
If you can log in to the database, it indicates that the database is normal. In this case, proceed to the next step.
If you cannot log in to the database, check whether the parameters in the tnsnames.ora file under /opt/oracle/product/9ir2/network/admin are set correctly.
2. The NCP is abnormal.
Run the ncp su � ncp command to enter the NCP user mode.
Run the checkncp command. If the NCP is started, proceed to the next step. If the NCP is not started, run the startncp command to start the NCP. If the operation is successful, proceed to the next step. If the operation fails, it is recommended that you reinstall the NCP.
3. An SMS exists in the Oracle database.
Check whether an SMS exists in the Oracle database. In the case of the Oracle database of certain versions, the SMS and the TOS are both installed in the database. Therefore, certain ports are co-used by these two systems. If the SMS is started, the TOS that uses the same ports cannot be started. In this case, you need to modify the server.xml file of the SMS in server/sms/tomcat/conf, as follows:
Change <Server port="8005" shutdown="SHUTDOWN"> to <Server port="8007" shutdown="SHUTDOWN">.
Change <Connector port="8081" maxHttpHeaderSize="8192" to <Connector port="8083" maxHttpHeaderSize="8192".
Change <Connector port="8009"
enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />
to <Connector port="8011"
enableLookups="false" redirectPort="8443" protocol="AJP/1.3" />.
That is, three port numbers need to be changed.
Then, navigate to the $HOME/script directory and modify the checksms_i file as follows:
Change #connect local server with port 8081
exec 3<>/dev/tcp/ >&2
#connect local server with port 8083
exec 3<>/dev/tcp/ >&2
Note that the port that is used to check whether the SMS is started is modified.
After the modification, the TOS can be started.
4. The configuration file of the TOS is incorrect.
If the TOS still cannot be started after the preceding modification, check the configuration file of the TOS.
Check whether the jdbc.url, jdbc.username, and jdbc.password parameters in the file under /server/tos/ webapp/ROOT/WEB-INF/conf are set correctly. Note that the IP address behind jdbc.url must be the IP address of the server where the TOS is installed.
After all the data is set correctly, the TOS can be started in the normal state. 
Root Cause
1. The Oracle database is abnormal.
2. The NCP is abnormal (the NCP must be started before the TOS is started).
3. An SMS exists in the Oracle database.
4. The configuration file of the TOS is incorrect.