Creating a concert log archive, 6 creating a concert log archive – Clear-Com Concert for Newsroom User Manual

Page 22

Advertising
background image

22

Server Installation Guide


In the preceding example:

The primary Ethernet interface port (eth0) has been assigned an IP address of 192.168.1.100 (the
address will probably be different on your system).

A physical connection to a switch within the network has been detected. The other Ethernet port
(eth1), is currently not active and not physically connected to a switch (as recommended).

Note:

An IP address for eth0 starting with 169.x.x.x, indicates that the server was unable to get a DHCP address
from a DHCP server. To resolve this issue, consider assigning a static IP address to the server.
For more information, see 3.1.2.

4.1.6 Creating a Concert log archive

You can use the collect command to create an archive containing a snapshot of all relevant Concert
information on the Concert Server (such as logs, package versions and configuration files).

This archive can then be emailed to a Clear-Com support representative, for use in diagnosing system issues.

Tip:

It is easier to create an archive in the CMI. For more information, see the Event Log sections in the

Concert Administrator Guide.

To create a Concert log archive, type:

# sudo service concert collect


The following output is returned:

Collect script will remove all previously created archives -- continue? (y/n): y

Collecting Concert logs...
* collecting trace logs...
* collecting config files...
* collecting database logs...
* collecting system logs...
* collecting Package versions...
* archiving files...
* successfully generated archive
'/var/www/html/snapshots/concert_snapshot_2012-01-01_08h53m43s.tar.gz'

Collect operation completed successfully.

Note:

The [file_name] will be uniquely created each time this command is executed. Upon execution, any previously
created archives will be removed from the system.

Advertising
This manual is related to the following products: