3.5 Connecting to a Linux Server
Refer to this checklist for help with problems connecting to the Linux Server.
Also see
Server Problem Check List
|
Check to be Performed
|
Comments / Further Actions
|
|
Process lcolist shows as two active processes when the active processes are displayed (normal operation).
|
You can use ps -ef | grep lco to list all LANSA processes on the Server. Refer to the LANSA Communications Setup Guide.
If you cannot see these processes, the LANSA listener is not running.
|
|
O/S user profile and password coming from the client are valid on the server system and in the correct case (if applicable).
|
|
|
DBMS user profile and password coming from the client are valid on the server system.
|
|
|
Process lcotp shows up as an active process after connection is made. Each connection has its own lcotp running.
You can use ps -ef | grep lcotp to check.
|
If this is not true, you have an initial connection problem or an application start up problem. If there is no entry in the x_err.log file, try turning on tracing of Communications on both the Client and the Server. See the LANSA Communications Setup Guide for details. If you still cannot find any logs, refer to Where can I find logs of messages and errors?
|
|
Process lcotp starts when a connection is made but it quickly fails (or disappears) and the client gets a communications error.
|
You have an initial X_RUN environment problem such as DBMS connection problem or a failure in your own application. Look in the x_err.log file on the server system. Refer to Where can I find logs of messages and errors? for the file location.
|
|
Process lcotp fails (or disappears) while your application is running and the client gets a communications error.
|
Look in the x_err.log file on the server system. Refer to Where can I find logs of messages and errors? for the file location.
|
|
x_err.log shows an SQL error
|
Refer to Database following for help.
|
|