Tracing Server-side bugs

Server Bug Trace

1.      Logon server host.

Logon server with specified user account for different line.

Present Innolux QA server is: 172.12.16.110

Array Line: user/ pwd: rary/ 123456

Cell Line: user/ pwd: rcel/ 123456

CF Line: user/ pwd: rcft/ 123456

2.      Enter the log directory

Type “ cd LCDworks/bin/FWLOG_DIR” command to enter the log directory in HOME directory.

 

3.      Find the log files for specified server application.

According to the timing and server application name, we can easy to find the log file. Like the above figure, the xxx.log file is the current log. The xxx.log.x is backup log files, you can find the latest update timing of these log files with “ls –l” command. If you wanna track an event happened on Mar 8 13:25, You can find it in EAPsrv_RCFT_TRACE.log.1.

 

 

 

 

 

4.      Open the log file and search helpful information.

5.      Sometime you need increase log level to get more detailed error or trace information printed by program. You can increase the verbose and diagnose of the log file for specified server application. After that, reproduce the bug, you would get the detailed log for this issue. Please reset the verbose and diagnose level after you complete tracing.

Generally speaking, the server application’s verbose and diagnose are default 1 when it is startup this is the minimum log level. You can increase verbose and diagnose to 5. This will give you detailer information and you can get the MBX message sent by clients/servers.

You need set verbose and diagnose level for all the server instances.

E.G. you need get detail log information of EAPsrv.

Find how many EAPsrv instances live in the host. Like the below figure, you can find 3 EAPsrv instances, EAPsrv.1, EAPsrv.2 and EAPsrv.3.

 

 

 

 

 

Follow the figure to set the verbose and diagnose attribute.

 

 

 

 

 

 

 

 

 

 

Reset the verbose and diagnose for all server instances.

 6.  Using Cell talk.
To start cell talk, using the command:

 CELLtalk -n $FWMBX

where $FWMBX is an environment variable, its value varies according to the logon user.

Once in cell talk, use the du command to print mailboxes, du accepts wildcards like *, to print specific mailboxes. Use help to get help.

To send messages to a server, use the command:

conv servername (e.g. conv EAPdefault )

and then you can type or paste messages directly to the command line.

 6.  Using Cell talk.
To start cell talk, using the command:

 CELLtalk -n $FWMBX

where $FWMBX is an environment variable, its value varies according to the logon user.

Once in cell talk, use the du command to print mailboxes, du accepts wildcards like *, to print specific mailboxes. Use help to get help.

To send messages to a server, use the command:

conv servername (e.g. conv EAPdefault )

and then you can type or paste messages directly to the command line.

  7. Run Cell talk on window platform

There are tow way to run celltalk tools. One is that you can run it in window. Another is to run it in Unix. There are some difference between these two platform.

1. Run Celltalk in Windows

1. Install PTDF window client toolkit by default setting from //172.16.22.20/brooks/Backup/DTPFtraining/5.DTPF/Installer/FwNT3.2.2-Bld1_Dev012103.exe

By default, it will install it in C:/FASTech

2. Add C:/FASTech/DTPFA/ FwNT4.d/bin/Debug to the environment variable, PATH.

3. Open a MS-DOS window, and type in “CELLTALK”

4. Connect to server host and specified mbx.

Conn 172.16.12.110 RCFT_MBX

5. Conv to appropriate mailbox listen by server application. Because there are more than one mailbox in MBX. Simply, you conv to default mailbox, named as [ServerName]default (e.g. the mailbox listened by WIP server is WIPdefault). The message in default mailbox will be executed by server application instance randomly.

conv WIPdefault

6. Type the message and wait the reply message.

There are tow way to run celltalk tools. One is that you can run it in window. Another is to run it in Unix. There are some difference between these two platform.

1. Run Celltalk in Windows

1. Install PTDF window client toolkit by default setting from //172.16.22.20/brooks/Backup/DTPFtraining/5.DTPF/Installer/FwNT3.2.2-Bld1_Dev012103.exe

By default, it will install it in C:/FASTech

2. Add C:/FASTech/DTPFA/ FwNT4.d/bin/Debug to the environment variable, PATH.

3. Open a MS-DOS window, and type in “CELLTALK”

4. Connect to server host and specified mbx.

Conn 172.16.12.110 RCFT_MBX

5. Conv to appropriate mailbox listen by server application. Because there are more than one mailbox in MBX. Simply, you conv to default mailbox, named as [ServerName]default (e.g. the mailbox listened by WIP server is WIPdefault). The message in default mailbox will be executed by server application instance randomly.

conv WIPdefault

6. Type the message and wait the reply message.