watchdog report zip file structure

Top  Previous  Next
Standard > Troubleshooting Data: References > Netrix > Debug Information

This describes the contents of some of the files gathered by the watchdog when a problem is detected.

 

backtracefile.txtAvailable when turret Application crashes.  Contains a stack trace of calls leading up to the failure for each thread that crashed.  See Section on analysing the backtracefile.
df.txtthe result of a df command at the time of failure
dhcpc/dhcpcd-ethx.infocontains variables set by DHCP for the interface, x = 0 or 1
dmesg.txtcontains the output from the Linux 'dmesg' command.
download.inf.xxxxlast and previous download information file, xxxx = "curr" or "prev"
eth_logx_wd.txtethernet driver specific internal data. x = 0 or 1
i2cStatus.txtcreated by watchdog by interrogating the I2C driver three times. Indicates that the I2C is still operating.
ifconfig.txtcontains the output from the linux 'ifconfig' command.
lsdhcp.txtcontains the output from the lunix 'ls -l /etc/dhcpc /var/db' command. These are useful to see the last time leases were renewed.
lsopt_data.txtcontains the output from the lunix 'ls -l /opt/data'.  Useful to see the size and existence of certain files at time of failure without wasting space in the report.
lsvar_log.txtcontains the output from the Lunix 'ls -l /var/log'.  Useful to see the size and existence of certain files.

netrixPlatform.log

ps.txtcontains the output from the Lunix 'ps ax'.  Useful to see what other processes were running at the time of the failure.
reason.txtgives the reason the watchdog gave for the gathering of the files in this report.  Also shows the 'uptime' and version of turret software.
route.txtContains the output from the Lunix 'route'.  Shows the currently defined network routing details.
signalcaught.txtAvailable when turret application crashes. Contains an indication of which threads crashed and the Linux signal that caused the crash.
Threads.logContains the thread numbers of the main threads created during start up.
top.txtFinal 'top -bcn 1' run by watchdog at the time the failure was detected.
UTAApplications.logContains the last 600 records of output from the Turret Application before a crash.  Watchdog restricts the size to keep the overall report small.
UTAPlatform.logContains the Platform log which is usually a record of what was written to the unseen turret platform screen.
currentIPTNetworkConfig.jsonThe Current Network Configuration file

 

/tmp/*

./capturex.pcapTCP Dump capture files containing upto 1000 packets of trace in each file, x = 1 or 2
./device-profile.json                
./dhcplog.tmpSome debug specific to NIC teaming feature and DHCP
./ethx.hook.env.xxxFrom dhcp contains dhcp parameters such as lease time, ip address etc. x = 0 or 1, xxx=current or prev
./hardwareDevices.jsonHardware information such as turret type, serial number.
./interfaceStatus.jsonStatus of both interfaces.

./ipt.1018.mod

./ipt.BTNetrix1402394759.cfgthe turret specific configuration downloaded from TSS.

./ipt.versions.cfg

./ipt.zones.cfgthe zones downloaded from TSS.
./logOnData.jsonlog on data

./patches.json

./postRotate_UTAApplications.log
A file indicating the occurrence of the UTAApplications log file being rotated to conserve disk space.
./postRotate_UTAPlatform.log
A file indicating the occurrence of the UTAPlatform log file being rotated to conserve disk space.
./shortcutData.jsonShortcut data.
./syncClientStatus.jsonsync client status data.
./topx.txtWatchdog runs the Linux 'top -bcn 1' command every 60 seconds and stores the output in these files. The file is reused, x = 0, 1, . . 9.
./tssStatus.jsonContains the status of the connection with the TSS indicating which TSS is being used, primary or secondary, and their URL's.
./user-profile.jsoncontains user profile data.
./userSettings.jsoncontains user settings information.  Useful for spotting trends in resource usage, i.e. memory and/or cpu usage, etc.

 

/www-log/*

./access.logcontains details of the web interface activity.

./lighttpd.error.log