Entering content frame

Procedure documentationTroubleshooting When Status Is Red Locate the document in its SAP Library structure

Use

This section described how to handle the following errors, which can lead to status Red:

·        <server_type> check : server not responding

·        ping reports general error

·        ping timeout

·        index could not be created RC: <errorcode>

·        search ended with RC: <errorcode>

·        could not get queue 2982

·        WebServer could not be reached

Error: <server_type> check : server not responding

This error can occur for the index server, queue server, preprocessor, or name server.

Troubleshooting

...

       1.      Log on to the TREX host.

       2.      Check whether the TREX server is active.

If it is not running, start it using the TREX daemon.

       3.      Check the host name and port of the TREX server in the file installed.xml:

                            a.      Use the Python script kill.py to define the TREX server port. You can find this script in the directory <TREX_DIR>/exe/python_support.

Note

Execute the script without arguments. This displays information on the TREX server without stopping them.

                            b.      Check that the host name and port of the TREX server are entered correctly in the file installed.xml. You can find this file in the directory <TREX_DIR>/exe/python_support/grmg.

Server Type

Section of installed.xml

Index server

<component name="IS_01" installed="X">

     <property name="HOST" value=" host"/>

     <property name="PORT" value=" 30003"/>

</component>

Queue server

<component name="QS_01" installed="X">

     <property name="HOST" value=" host"/>

     <property name="PORT" value=" 30004"/>

</component>

Preprocessor

<component name="PP_01" installed="X">

     <property name="HOST" value=" host"/>

     <property name="PORT" value=" 30002"/>

</component>

Name server

<component name="NS_01" installed="X">

     <property name="HOST" value=" host"/>

     <property name="PORT" value=" 30001"/>

</component>

       4.      If you have to change the file installed.xml, proceed as follows:

                            a.      Stop the TREX GRMG server by stopping the TREX daemon.

                            b.      Change the file.

                            c.      Start the TREX GRMG server by starting the TREX daemon.

Error: ping reports general error

This error can occur for the index server, queue server, preprocessor, or name server.

Troubleshooting

...

       1.      Log on to the TREX host.

       2.      Execute all steps listed under Error: <server_type> check: server not responding above.

       3.      If this does not correct the error, stop the TREX daemon and restart it.

Error: ping timeout

This error can occur for the index server, queue server, preprocessor, or name server.

Troubleshooting on the Index Server

...

       1.      Log on to the TREX host.

       2.      Execute all steps listed under Error: <server_type> check: server not responding above.

       3.      If this does not remove the error, use the TREX admin tool to check the status of the index server in the Landscape Services window.

Check whether there are requests that have waited more than 5 minutes to be processed. If such requests exist, restart the index server at Landscape Services.

Troubleshooting on the Queue Server, Preprocessor, and Name Server

...

       1.      Log on to the TREX host.

       2.      Execute all steps listed under Error: <server_type> check: server not responding above.

       3.      If this does not remove the error, use the TREX admin tool to restart the queue server.

Error: index could not be created RC: <error code>

This error can occur for the index server.

Troubleshooting

...

       1.      Refer to SAP Note 879305 for the meaning of the error code. Try to correct the error.

       2.      If you cannot correct the error, create a customer message.

Error: search ended with RC: <error code>

...

This error can occur for the index server.

Troubleshooting

       1.      Refer to SAP Note 879305 for the meaning of the error code. Try to correct the error.

       2.      If you cannot correct the error, create a customer message.

Error: could not get queue 2982

This error can occur on the queue server.

Troubleshooting

Use the TREX admin tool to restart the queue server.

Error: WebServer could not be reached

This error can occur on the TREX Web servers.

Troubleshooting

...

       1.      Log on to the TREX host.

       2.      Check whether the TREX Web server is running.

¡        Windows: Open the service management console and check whether the WWW Publishing Service is running.

¡        UNIX: Use ps to check whether the HTTP daemon httpd is running.

If the TREX Web server is not running, restart it.

       3.      Check whether the URL of the TREX Web server is entered correctly in the file installed.xml. This URL varies according to the operating system that TREX is running on. You can find the file installed.xml in the directory <TREX_DIR>/exe/python_support/grmg.

Operating System of TREX Host

Section of installed.xml

Windows

<component name="WS_01" installed="X">

     <property name="URL" value=" http://<trex_hostname>:30005/trexhttpserver/trexhttpserver.dll"/>

</component>

UNIX

<component name="WS_01" installed="X">

     <property name="URL" value=" http://<trex_host_name>:30005/TREX"/>

</component>

Note

You might need to specify the domain of the TREX Web server in the URL: http://<hostname>.<domain>:30005.

       4.      If you have to change the file installed.xml, proceed as follows:

                            a.      Stop the TREX GRMG server by stopping the TREX daemon.

                            b.      Change the file.

                            c.      Start the TREX GRMG server by starting the TREX daemon.

       5.      If this does not correct the error, restart the TREX Web server.

 

Error: Enterprise Portal unavailable

If the entire Enterprise Portal becomes unavailable, the system displays appropriate error messages in the subtree MoniInfra_...  ®  RunStatus/Error Messages.

Troubleshooting

On UNIX

·        If the TREX GRMG server does not behave correctly, check whether the port is blocked. To do this, use netstat –a | grep <GRMG_server_port_number>. This will generate a list of ports.

·        Check the ports and modify the port if it is already in use.

 

 

Leaving content frame