Toolpack Debug Application:Tbdebug - Revision history

Abrassard: /* How to launch tbdebug tool */

2012-01-30T20:01:00Z

How to launch tbdebug tool

← Older revision		Revision as of 16:01, 30 January 2012
Line 24:		Line 24:
	#Press Enter to launch the ''tbdebug'' application		#Press Enter to launch the ''tbdebug'' application

	If you have selected an acquisition time ~~of 0 or~~ -1, complete the following steps:		If you have selected an acquisition time -1 (manual), complete the following steps:
	#Press the Escape key two times to exit the ''tboamapp'' application		#Press the Escape key two times to exit the ''tboamapp'' application
	#Select the ''tbdebug'' application		#Select the ''tbdebug'' application

Abrassard: /* Using acquisition period of -1 (infinite) */

2012-01-30T20:00:35Z

Using acquisition period of -1 (infinite)

← Older revision		Revision as of 16:00, 30 January 2012
Line 39:		Line 39:
	Use this mode when you can reproduce the problem: Start tbdebug with a long enough period and then reproduce the problem. This ensures that only a short and appropriate portion of the application logs aregathered, simplifying the analysis of the log files by focusing on the period where the actual problem was reproduced.		Use this mode when you can reproduce the problem: Start tbdebug with a long enough period and then reproduce the problem. This ensures that only a short and appropriate portion of the application logs aregathered, simplifying the analysis of the log files by focusing on the period where the actual problem was reproduced.

	== Using acquisition period of -1 (~~infinite~~) ==		== Using acquisition period of -1 (manual) ==
	This mode will also capture logs for a period of acquisition. The ~~duration of the period is infinite, and the~~ user must manually stop the acquisition by pressing the letter ''a'' key in the tbdebug applications' window (through tbx_cli_tools_remote application)		This mode will also capture logs for a period of acquisition, but started and stopped manually. The user must manually start/stop the acquisition by pressing the letter ''a'' key in the tbdebug applications' window (through tbx_cli_tools_remote application)

	== Using acquisition period of 0 (snapshot mode) ==		== Using acquisition period of 0 (snapshot mode) ==

Abrassard at 19:58, 30 January 2012

2012-01-30T19:58:46Z

← Older revision		Revision as of 15:58, 30 January 2012
Line 19:		Line 19:
	#Launch tbx_cli_tools_remote application (/lib/tb/toolpack/pkg/2.''X.X''/bin/release/''[distribution]''/tbx_cli_tools_remote)		#Launch tbx_cli_tools_remote application (/lib/tb/toolpack/pkg/2.''X.X''/bin/release/''[distribution]''/tbx_cli_tools_remote)
	#Select the ''tboamapp'' application		#Select the ''tboamapp'' application
	#Press TAB until the ''Application launch manager'' page is selected		#Press TAB until the ''Application launch manager'' (ALM) page is selected
	#Press key l (lower-case L)		#Press key l (lower-case L)
	#Choose acquisition time for logs (*** see note below about acquisition time and acquisition modes)		#Choose acquisition time for logs (*** see note below about acquisition time and acquisition modes)

Lucas Trottier: /* Using tbdebug to perform Ethernet capture (tcpdump) on the adapter */

2011-11-23T20:19:17Z

Using tbdebug to perform Ethernet capture (tcpdump) on the adapter

← Older revision		Revision as of 16:19, 23 November 2011
Line 55:		Line 55:
	#Press the Escape key two times to exit the ''tboamapp'' application		#Press the Escape key two times to exit the ''tboamapp'' application
	#Select the ''tbdebug'' application		#Select the ''tbdebug'' application
	#Press ''t'' to start ~~or stop the~~ tcpdump capture (on one, or all adapters)		#Press ''t'' to start tcpdump capture (on one, or all adapters; -1 for duration time)
			#Press ''t'' again to stop tcpdump capture

	After stopping the capture, a wireshark-compatible ".cap" file will be available here, for each adapter:		After stopping the capture, a wireshark-compatible ".cap" file will be available here, for each adapter:

Lucas Trottier: /* Using tbdebug to perform Ethernet capture (tcpdump) on the adapter */

2011-11-23T20:15:45Z

Using tbdebug to perform Ethernet capture (tcpdump) on the adapter

← Older revision		Revision as of 16:15, 23 November 2011
Line 53:		Line 53:
	#Choose -1 for execution time		#Choose -1 for execution time
	#Press Enter to launch the ''tbdebug'' application		#Press Enter to launch the ''tbdebug'' application

	#Press the Escape key two times to exit the ''tboamapp'' application		#Press the Escape key two times to exit the ''tboamapp'' application
	#Select the ''tbdebug'' application		#Select the ''tbdebug'' application

Abrassard: /* Using tbdebug to perform Ethernet capture (tcpdump) on the adapter */

2011-11-11T13:01:48Z

Using tbdebug to perform Ethernet capture (tcpdump) on the adapter

← Older revision		Revision as of 09:01, 11 November 2011
Line 60:		Line 60:
	After stopping the capture, a wireshark-compatible ".cap" file will be available here, for each adapter:		After stopping the capture, a wireshark-compatible ".cap" file will be available here, for each adapter:
	/lib/tb/toolpack/setup/12358/2.''X''/apps/tbdebug/tbdebug_logs/tcpdump/		/lib/tb/toolpack/setup/12358/2.''X''/apps/tbdebug/tbdebug_logs/tcpdump/

			== Using shell commands to perform Ethernet capture (tcpdump) on the adapter ==
			Another way to perform a tcpdump capture on the adapter is from it's shell:
			#Start the capture (with circular buffer of 1MB),
			#stop the capture,
			#then upload the capture (there must be a FTP server accepting anonymous connections, here on example IP 10.11.12.13):
			tcpdump start 1000000
			tcpdump stop
			tcpdump upload 10.11.12.13

	== Optional capture options ==		== Optional capture options ==

Abrassard: /* Optional capture options */

2011-11-09T15:20:30Z

Optional capture options

@@ Line 45: / Line 45: @@
 In this mode, the ''tbdebug'' application will not use an acquisition period, but will instantly gather logs of all applications for the current day, as well as other logs that are not related to an acquisition period (there will thus be no IP capture or recording in that mode).
 Use this mode when the bug has already occurred, and cannot be reproduced again.
 == Optional capture options ==

Cboulanger: /* Optional capture options */

2011-06-20T18:52:02Z

Optional capture options

← Older revision		Revision as of 14:52, 20 June 2011
Line 48:		Line 48:
	== Optional capture options ==		== Optional capture options ==
	Additional capture parameters can be configured from the tbdebug configuration file:		Additional capture parameters can be configured from the tbdebug configuration file:
	/lib/tb/toolpack/setup/12358/2.X/apps/tbdebug~~/tbdebug_logs~~/tbdebug.xml		/lib/tb/toolpack/setup/12358/2.X/apps/tbdebug/tbdebug.xml
	We recommend changing only the following parameters:		We recommend changing only the following parameters:
	record_new_calls: Enable/disable recording of new calls established during the acquisition period		record_new_calls: Enable/disable recording of new calls established during the acquisition period

Allyntree: /* Using acquisition period of -1 (infinite) */

2010-11-24T01:43:59Z

Using acquisition period of -1 (infinite)

← Older revision		Revision as of 21:43, 23 November 2010
Line 40:		Line 40:

	== Using acquisition period of -1 (infinite) ==		== Using acquisition period of -1 (infinite) ==
	This mode will also capture logs for a period of acquisition. The duration of the period is infinite, and user ~~has to~~ manually stop the acquisition by pressing ~~key~~ ''a'' in the tbdebug applications' window (through tbx_cli_tools_remote application)		This mode will also capture logs for a period of acquisition. The duration of the period is infinite, and the user must manually stop the acquisition by pressing the letter ''a'' key in the tbdebug applications' window (through tbx_cli_tools_remote application)

	== Using acquisition period of 0 (snapshot mode) ==		== Using acquisition period of 0 (snapshot mode) ==

Allyntree: /* Using acquisition period greater than 0 */

2010-11-24T01:42:30Z

Using acquisition period greater than 0

← Older revision		Revision as of 21:42, 23 November 2010
Line 37:		Line 37:
	== Using acquisition period greater than 0 ==		== Using acquisition period greater than 0 ==
	In this mode, the ''tbdebug'' application will download only the log files of Toolpack applications for that period of acquisition, and will optionally capture IP packets from TMedia, and record calls using tbstreamserver.		In this mode, the ''tbdebug'' application will download only the log files of Toolpack applications for that period of acquisition, and will optionally capture IP packets from TMedia, and record calls using tbstreamserver.
	Use this mode when you can reproduce the problem: Start tbdebug with long enough period, then reproduce the problem. This ensures that only a short and appropriate portion of the application logs ~~is gathered~~, simplifying analysis of the log files by focusing on the period where the actual problem was reproduced.		Use this mode when you can reproduce the problem: Start tbdebug with a long enough period and then reproduce the problem. This ensures that only a short and appropriate portion of the application logs aregathered, simplifying the analysis of the log files by focusing on the period where the actual problem was reproduced.

	== Using acquisition period of -1 (infinite) ==		== Using acquisition period of -1 (infinite) ==