Troubleshooting Toolpack

From TBwiki
Revision as of 14:28, 10 May 2011 by Luc Morissette (Talk | contribs)
Jump to: navigation, search

This page contains pointers to help troubleshoot Toolpack-based systems.


Contents

Installation

Problem: Toolpack fails during installation

Problem: The Toolpack system does not start


Problem: I want to change the Ip Address of the TMG800/TMG3200 from static to DHCP or from DHCP to static.


Problem: I want to change the hostname of the server running Toolpack


Problem: E1 trunks are not up


Problem: Can't download a new software package

You see this error while trying to download a software package with wget:

Resolving download.telcobridges.com... failed: Temporary failure in name resolution.
wget: unable to resolve host address `download.telcobridges.com'

Web portal

Problem: The Toolpack web portal does not start or is not accessible.


Problem: I cannot perform addition or modification of configuration in the web portal. Usually this occurs in a new Toolpack Platform, for example, when new Toolpack software has been just installed on a host or a new TMG3200 is started up.


Problem: Do not have permission to add features.

  • See 'How to modify system configuration'


Problem: The system does not work properly with a copied configuration.


Problem: There are no web browser on the linux host server

ssh tunnel can be use to re-direct the connection on a remote host port to a local port:

System configuration backup

Problem: How do I make sure I keep my system configuration?

All the configuration is stored in a MySQL database. See Database Backup.

For releases before 2.4 or older or if you do not have access to the web portal, see Manual Database Backup.


Calls

Problem: The Tmedia device does not accept or generate calls

A new page is created here: How to troubleshoot call routing

How to gather all logs

Problem: Which application logs should I gathered?


How to get a dump for a crashed Toolpack application

When one of the Toolpack application crashes, log files are most likely useless, since most of the time the crash is unrelated to the few traces found in the log files.
In order to debug a crash, TelcoBridges needs other debugging information (the "call stack" of the crashed application thread).
Procedure to get that information can be found here:
For release 2.5 and up, see 'Support:How To Get Toolpack Crash Dump'
For release 2.4 and up, see 'Support:How To Run Toolpack Application In gdb'

How to submit a problem

Problem: I don't know what else to do

Personal tools