Linter: Enabling Debug for the Linter Database

Overview

This procedure describes the steps to enable debug for the Linter DB. This procedure is helpful when you get DBStatement errors (found under tsunami) and need to find out more about the issue related to the Linter DB, such as an error with a query operation.

Very Important Note

Keep the following in mind when executing the procedure in this article:

Using Linter's debug will may fill up the file system.
It's strongly recommended that you use this feature only in cases where you will be able to monitor the filesystem disk space, or in cases where you can quickly reproduce the issue and then immediately disable debug, to avoid taking up too much space.
This procedure doesn't require a restart of services, or of the DXi.
If you aren't familiar with Linter and its databases, do not attempt any other activity inside Linter besides the one described in this procedure.

Procedure

To enable debug in Linter, follow this procedure.

1. Where Is the Log Stored?

DXi prior to version 2.2:

/snfs/common/data/StorNext/database/config/filelist

Version 2.2 and above:

/opt/DXi/adic/database/config/filelist

Open the file filelist and you'll find lines like the following (the lines marked here in yellow show where the log is stored).

################################################################################

# This section list the log files that will be rolled. Each entry must have # the following syntax or it will be ignored.

# roll_log : <path> : <emasslog> : <save> : <num_keep>

# where

# path - This should be a relative pathname, relative to the top

# level install dir, i.e. /usr/adic.

# emasslog - If this is an emasslog directory put 'y'. Otherwise put

# 'n'. (when 'y' the path must be the top level emasslog dir)

# Valid values are: 'y' or 'n'.

# save - Put 'y' to save the log file to the specified location

# (generally somewhere on the filesystem which will be

# managed). Otherwise, put 'n'. NOTE: This option will only

# be used if the '-s' option is given when the log rolling

# script is called. Valid values are: 'y' or 'n'.

# num_keep - The number of logs to keep. Suggested is 7 which is also

# the default value if you put 'DEF' for this field.

# Valid values are: 'DEF' (for 7-> preferred) or the number

# of logs to keep (i.e. 10 to keep the last 10 logs).

# NOTE: 1. You should list only a single path on each line.

# 2. Wildcards are permited.

# 3. All fields must have a valid value

################################################################################

roll_log : database/db/LINTER.LOG : n : n : DEF <<<<<< THIS IS THE FILE CREATED WHEN YOU ENABLE LOG ON LINTER VIA SQL

roll_log : database/db/linter.out : n : n : DEF <<<<<< THIS IS THE FILE THAT IS BY DEFAULT CREATED AND WILL HAVE ONLY THE INFO ABOUT STARTUP OF THE DB (COMES WITH COLLECT LOGS)

2. How to Enable Debug Logging

2.1. Open a putty session to DXi using root, and log in to the Linter DB SQL cli using the following command:

# inl

2.2. You'll be asked for user/password. Contact your backline team (SES or SUS) to acquire this information, and then enter it.

2.3. By default, Linter's debug is disabled. To confirm that debug is disabled, run the dbinfo command from the SQL prompt. In the last line of the output shown here, you'll see that debug is set to 'off'.

SQL>dbinfo

Database 'tdlmdb' information

   RDBMS Linter SQL version          : 5.9.28

   Linter kernel memory pool size   : 15000

   Channel queue                     : 3750

   Table queue                       : 1100

   Column queue                      : 5200

   File queue                        : 190

   User queue                        : 100

   Transaction control status        : on

   Sorting process memory pool size : 1500

   Number of sort processes          : 1

Log file (LINTER.LOG) status      : off   <<<< logging is disabled

SQL>

2.4. To enable debug logging, enter the following command:

SQL>set log full;

2.5. Run dbinfo again, to confirm that debug was enabled:

SQL>dbinfo

   Database 'tdlmdb' information

   RDBMS Linter SQL version          : 5.9.28

   Linter kernel memory pool size   : 15000

   Channel queue                     : 1750

   Table queue                       : 1100
   Column queue                      : 5200
   File queue                        : 190
   User queue                        : 100
   Transaction control status        : on
   Sorting process memory pool size : 1500
   Number of sort processes          : 1
   Log file (LINTER.LOG) status      : on   <<<< now log is enabled
SQL>

3.   Here an example of the linter log:

[root@SES6520DXi59 db]# head -20 /opt/DXi/adic/database/db/LINTER.LOG

!:E=0:T=23:51:06.825:XPid=26828:XTid=26828:C=64:

?DESC:T=23:51:10.893:XPid=26828:XTid=26828:L=92:

!:E=0:T=23:51:10.893:XPid=26828:XTid=26828:C=64:

?    :T=23:51:16.869:XPid=26828:XTid=26828:C=64:L=16384:P=0:

set log off

;

!:E=0:T=19:42:19.879:XPid=12035:XTid=12035:C=45:

?TRAN:T=19:42:19.882:XPid=18053:XTid=18053:C=6:L=8192:P=0:

select trap_notification_ref, sl_notification_element_ref, ticket_ref, alert_ref, trap_state_ref, created_at, sent_at, destination_ip_list, trap_message, trap_body from sl_notification_trap where sent_at is null;

!:E=0:T=19:42:19.882:XPid=18053:XTid=18053:C=6:L=1128:

?FSPC:T=19:42:19.882:XPid=18053:XTid=18053:C=6:L=2040:S=80:K=80:

730000000100000073000000030000007300000004000000730000000500

000073000000060000007300000007000000730000000800000073000000

09000000730000000A000000730000000B000000

!:E=0:T=19:42:19.882:XPid=18053:XTid=18053:C=6:

?CLOS:T=19:42:19.882:XPid=18053:XTid=18053:C=39:

!:E=0:T=19:42:19.882:XPid=18053:XTid=18053:

?OCUR:T=19:42:19.882:XPid=18053:XTid=18053:C=6:P=256:R=0:

!:E=0:T=19:42:19.882:XPid=18053:XTid=18053:C=39:

?EXEC:T=19:42:19.883:XPid=18053:XTid=18053:C=39:L=8192:S=1128:

[root@SES6520DXi59 db]#