SDI-104 Operator's Manual
Version 2008
[Search Manual] [Table of Contents] [FAQ] [Go to Previous] [Go to Next]
Like image segment files, log files are also located in the /mnt/HDD/data/ directory. The maximum size that the log file is allowed to grow to before being rolled and the number of log files to retain are defined by the LOG_SIZE= and LOG_COUNT= settings in the /data/opt/etc/rc.MTSAT-HRIT file. The following is a sample listing of files rolled at 1 MB and ten files retained.
root@0[data]# cd /mnt/HDD/data root@0[data]# ls -lt mtsat* -rw-r--r-- 1 root root 767437 Feb 20 19:35 mtsat-hrit.log -rw-r--r-- 1 root root 1048599 Feb 20 12:01 mtsat-hrit.log.1 -rw-r--r-- 1 root root 1048641 Feb 20 01:03 mtsat-hrit.log.2 -rw-r--r-- 1 root root 1048631 Feb 18 19:01 mtsat-hrit.log.3 -rw-r--r-- 1 root root 1048626 Feb 18 08:03 mtsat-hrit.log.4 -rw-r--r-- 1 root root 1048600 Feb 17 21:03 mtsat-hrit.log.5 -rw-r--r-- 1 root root 1048674 Feb 17 10:19 mtsat-hrit.log.6 -rw-r--r-- 1 root root 1048607 Feb 16 23:35 mtsat-hrit.log.7 -rw-r--r-- 1 root root 1048610 Feb 16 11:02 mtsat-hrit.log.8 -rw-r--r-- 1 root root 1048587 Feb 15 23:02 mtsat-hrit.log.9 -rw-r--r-- 1 root root 1048603 Feb 15 11:02 mtsat-hrit.log.10 |
You can monitor ingest by tailing the log.
Type: tail -f mtsat-hrit.log
The sections below contain information about what the log files report during various scenarios.
For normal processing of an image segment, you'll see something like the output below.
INFO | jvm 1 | 2007/02/20 12:01:19 | Found start of a new file! Filename: IMG_DK01VIS_200702201130_004 INFO | jvm 1 | 2007/02/20 12:01:26 | before JPG read... INFO | jvm 1 | 2007/02/20 12:01:27 | BufferedImage width: 11000 INFO | jvm 1 | 2007/02/20 12:01:27 | BufferedImage height: 1100 INFO | jvm 1 | 2007/02/20 12:01:29 | This file is complete... |
If the jvm number increases, an error caused the ingestor to restart. This should be reported in the log file, as shown in the example below.
INFO | jvm 1 | 2007/02/20 17:35:31 | Found start of a new file! Filename: IMG_DK02VIS_200702201713_005 INFO | jvm 1 | 2007/02/20 17:35:48 | before JPG read... INFO | jvm 1 | 2007/02/20 17:35:48 | # INFO | jvm 1 | 2007/02/20 17:35:48 | # An unexpected error has been detected by HotSpot Virtual Machine: INFO | jvm 1 | 2007/02/20 17:35:48 | # INFO | jvm 1 | 2007/02/20 17:35:48 | # SIGSEGV (0xb) at pc=0x6afce646, pid=21359, tid=311316 INFO | jvm 1 | 2007/02/20 17:35:48 | # INFO | jvm 1 | 2007/02/20 17:35:48 | # Java VM: Java HotSpot(TM) Server VM (1.5.0_07-b03 mixed mode) INFO | jvm 1 | 2007/02/20 17:35:48 | # Problematic frame: INFO | jvm 1 | 2007/02/20 17:35:48 | # C [libclib_jiio.so+0xab646] INFO | jvm 1 | 2007/02/20 17:35:48 | # INFO | jvm 1 | 2007/02/20 17:35:48 | # An error report file with more information is saved as hs_err_pid21359.log INFO | jvm 1 | 2007/02/20 17:35:48 | # INFO | jvm 1 | 2007/02/20 17:35:48 | # If you would like to submit a bug report, please visit: INFO | jvm 1 | 2007/02/20 17:35:48 | # http://java.sun.com/webapps/bugreport/crash.jsp INFO | jvm 1 | 2007/02/20 17:35:48 | # ERROR | wrapper | 2007/02/20 17:35:48 | JVM exited unexpectedly. STATUS | wrapper | 2007/02/20 17:35:53 | Launching a JVM... INFO | jvm 2 | 2007/02/20 17:35:53 | Wrapper (Version 3.2.0) http://wrapper.tanukisoftware.org INFO | jvm 2 | 2007/02/20 17:35:53 | INFO | jvm 2 | 2007/02/20 17:35:54 | RT-STPS SSEC extension, version 1.1. Created Monday, February 12, 2007 INFO | jvm 2 | 2007/02/20 17:35:54 | 2/20/07 5:35 PM Auto-loading configuration. INFO | jvm 2 | 2007/02/20 17:35:54 | 2/20/07 5:35 PM Load HRIT.xml INFO | jvm 2 | 2007/02/20 17:35:54 | 2/20/07 5:35 PM Go INFO | jvm 2 | 2007/02/20 17:35:54 | 2/20/07 5:35 PM Ready to serve. |
Ingested data is purged when the period defined by the DAYS= setting in the /data/opt/etc/rc.MTSAT-HRIT file has elapsed. A purge check is done after each image is ingested. When image data is purged, you'll see log file output similar to that below.
INFO | jvm 1 | 2007/02/20 12:01:34 | Purging file: IMG_DK01IR2_200702171130_004 INFO | jvm 1 | 2007/02/20 12:01:34 | Purging file: IMG_DK01IR3_200702171130_004 |
Every hour frame and packet level statistics are dumped. When this happens, the output is similar to that below.
INFO | jvm 1 | 2007/02/20 12:11:44 | Processing statistics: (counts reset each time logged) INFO | jvm 1 | 2007/02/20 12:11:44 | packet.apid0 INFO | jvm 1 | 2007/02/20 12:11:44 | Packets Output=9559 INFO | jvm 1 | 2007/02/20 12:11:44 | Discarded Packets=0 INFO | jvm 1 | 2007/02/20 12:11:44 | Bad Lengths=0 INFO | jvm 1 | 2007/02/20 12:11:44 | Bad Length Sample=0 INFO | jvm 1 | 2007/02/20 12:11:44 | Missing Packets=0 INFO | jvm 1 | 2007/02/20 12:11:44 | Packets With Fill=0 INFO | jvm 1 | 2007/02/20 12:11:44 | Sequence Errors=0 INFO | jvm 1 | 2007/02/20 12:11:44 | cadu_service INFO | jvm 1 | 2007/02/20 12:11:44 | Unrouteables=0 INFO | jvm 1 | 2007/02/20 12:11:44 | Fill CADUs=310902 INFO | jvm 1 | 2007/02/20 12:11:44 | Output CADUs=88177 INFO | jvm 1 | 2007/02/20 12:11:44 | frame_status INFO | jvm 1 | 2007/02/20 12:11:44 | Lock Frames=399084 INFO | jvm 1 | 2007/02/20 12:11:44 | Flywheels=0 INFO | jvm 1 | 2007/02/20 12:11:44 | Slipped Frames=0 INFO | jvm 1 | 2007/02/20 12:11:44 | True Frames=0 INFO | jvm 1 | 2007/02/20 12:11:44 | Inverted Frames=399084 INFO | jvm 1 | 2007/02/20 12:11:44 | CRC Error Frames=0 INFO | jvm 1 | 2007/02/20 12:11:44 | RS-Corrected Frames=34851 INFO | jvm 1 | 2007/02/20 12:11:44 | RS-Uncorrectable Frames=5 INFO | jvm 1 | 2007/02/20 12:11:44 | Deleted Frames=5 INFO | jvm 1 | 2007/02/20 12:11:44 | Passed Frames=399079 INFO | jvm 1 | 2007/02/20 12:11:44 | frame_sync INFO | jvm 1 | 2007/02/20 12:11:44 | Mode=search INFO | jvm 1 | 2007/02/20 12:11:44 | Search Buffers=142431 INFO | jvm 1 | 2007/02/20 12:11:44 | Lost Sync Count=3 INFO | jvm 1 | 2007/02/20 12:11:44 | Flywheels=0 INFO | jvm 1 | 2007/02/20 12:11:44 | Total Frames=399084 INFO | jvm 1 | 2007/02/20 12:11:44 | hrit.hritfile INFO | jvm 1 | 2007/02/20 12:11:44 | Packets Written=9559 INFO | jvm 1 | 2007/02/20 12:11:44 | path.vc0 INFO | jvm 1 | 2007/02/20 12:11:44 | CADUs=88177 INFO | jvm 1 | 2007/02/20 12:11:44 | CADU Seq Errors=0 INFO | jvm 1 | 2007/02/20 12:11:44 | Missing CADUs=0 INFO | jvm 1 | 2007/02/20 12:11:44 | Idle VCDUs=0 INFO | jvm 1 | 2007/02/20 12:11:44 | Bad FHPs=0 INFO | jvm 1 | 2007/02/20 12:11:44 | Troublesome Frames=0 INFO | jvm 1 | 2007/02/20 12:11:44 | Created Packets=9603 INFO | jvm 1 | 2007/02/20 12:11:44 | Irrational Packet Lengths=0 INFO | jvm 1 | 2007/02/20 12:11:44 | Discarded Fragments=0 |
High numbers in the RS-Uncorrectable Frames= or Lost Sync Count= entries above usually indicate data reception or transmission problems. To do a time-order check for a high number of RS-Uncorrectable Frames= errors, run a command similar to that below from the /data directory.
Type: ls -1art | grep mtsat-hrit.log | xargs grep Uncorrect | grep -v Frames=1 | grep -v Frames=0
Values of 10 or more often result in dropped segments. If you see values of 10 or more occurring continuously or for spurts, you should check your antenna for optimum signal strength. It may need peaking or there may be data path hardware issues causing interference in the signal.
[Search Manual] [Table of Contents] [FAQ] [Go to Previous] [Go to Next]