Changes for page Reporting Issues

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -46,7 +46,7 @@
46	46
47	47	= Support Packages =
48	48
49		-iSymphony now allows administrators to create support packages which contain useful information about the system. Our support that our support staff can use to troubleshoot issues. Creating support packages is easy, and can be done from the Administration Interface or the server command line.
	49	+iSymphony now allows administrators to create support packages which contain useful information about the system. These packages are used by our support team to expedite the troubleshooting process. Creating s support package is easy, and can be done from the Administration Interface or the server command line.
50	50
51	51	{{note}}
52	52	The ability to create support packages is only available in iSymphony 3.3+. If you are using a version of iSymphony prior to 3.3, see the Manual Collection section below.
...	...	@@ -72,6 +72,120 @@
72	72	1. Click **Create**.
73	73	1. Once the package has been created you can use the **Download** button to download the package to your system and attach it to a support ticket.
74	74
	75	+== Creating Support Packages from the Command Line ==
	76	+
	77	+If you are unable to access the Administration Interface, you can create support packages from the server command line by executing the **support.sh** script. You can specify several parameters to tell the script which pieces of information to include in the package.
	78	+
	79	+1. Log into the server via SSH or a terminal.
	80	+1. (((
	81	+Run the following command:
	82	+
	83	+{{code language="bash"}}
	84	+/opt/isymphony3/server/support.sh
	85	+{{/code}}
	86	+
	87	+{{info}}
	88	+The above command will package all information. If you wish to specify the information that is included in the package you can use the flags specified in the Package Options section below.
	89	+{{/info}}
	90	+)))
	91	+1. (((
	92	+Once the script has generated the package it can be found in the following directory on the server:
	93	+
	94	+{{code}}
	95	+/opt/isymphony3/server/support
	96	+{{/code}}
	97	+
	98	+You will need to download the file from the server to your machine. See Transferring Files above.
	99	+)))
	100	+
	101	+== Package Options ==
	102	+
	103	+|=(((
	104	+Admin Option
	105	+)))|=(((
	106	+Script Flag
	107	+)))|=(((
	108	+Includes
	109	+)))
	110	+|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
	111	+(((
	112	+Application Logs
	113	+)))|(% style="text-align: center;" %)(% style="text-align: center;" %)
	114	+(((
	115	+-l
	116	+)))|(((
	117	+* All files in the **/opt/isymphony3/server/log** directory. Excludes any archived (tar.gz) logs.
	118	+)))
	119	+|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
	120	+(((
	121	+Archived Logs
	122	+)))|(% style="text-align: center;" %)(% style="text-align: center;" %)
	123	+(((
	124	+-a
	125	+)))|(((
	126	+* All archived log files (tar.gz) in the **/opt/isymphony3/server/log** directory.
	127	+)))
	128	+|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
	129	+(((
	130	+Thread Dump
	131	+)))|(% style="text-align: center;" %)(% style="text-align: center;" %)
	132	+(((
	133	+-t
	134	+)))|(((
	135	+* Generates a dump of all active threads in the JVM instance and writes it to the **/opt/isymphony3/server/log/iSymphonyServer.out.log** file.
	136	+
	137	+{{note}}
	138	+A thread dump will not be generated if the iSymphony server process is not running.
	139	+{{/note}}
	140	+
	141	+{{note}}
	142	+Application logs must be included in order to include the thread dump in the package.
	143	+{{/note}}
	144	+)))
	145	+|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
	146	+(((
	147	+Environment Information
	148	+)))|(% style="text-align: center;" %)(% style="text-align: center;" %)
	149	+(((
	150	+-e
	151	+)))|(((
	152	+* The process id of the running iSymphony server installation, if the server is running.
	153	+* The contents of** /proc/cpuinfo.**
	154	+* The contents of **/proc/meminfo**.
	155	+* The results of running the command **free -m**.
	156	+* The results of running the ~{~{
	157	+* A snapshot of the **top** command.
	158	+)))
	159	+|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
	160	+(((
	161	+Configuration Files
	162	+)))|(% style="text-align: center;" %)(% style="text-align: center;" %)
	163	+(((
	164	+-c
	165	+)))|(((
	166	+
	167	+)))
	168	+|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
	169	+(((
	170	+PBX Configuration
	171	+)))|(% style="text-align: center;" %)(% style="text-align: center;" %)
	172	+(((
	173	+-p
	174	+)))|(((
	175	+
	176	+)))
	177	+|(% class="highlight-grey" data-highlight-colour="grey" %)(% class="highlight-grey" data-highlight-colour="grey" %)
	178	+(((
	179	+Database Files
	180	+)))|(% style="text-align: center;" %)(% style="text-align: center;" %)
	181	+(((
	182	+-d
	183	+)))|(((
	184	+
	185	+)))
	186	+
	187	+
	188	+
75	75	= Manual Collection =
76	76
77	77	If you are using a version of iSymphony prior to 3.3, you can use the following instructions to collect system information to report to the iSymphony support team.