5.0
Table Of Contents
- VMware vCenter Operations Manager Enterprise Administration Guide
- Contents
- VMware vCenter Operations Manager Enterprise Administration Guide
- Configuring and Managing vCenter Operations Manager
- Configuring Adapters
- Configuring Resources
- Configuring Attribute Packages
- Configuring Applications
- Configuring and Managing Users
- Configuring Alert Notifications
- Performing Basic System Administration Tasks
- View vCenter Operations Manager Performance Information
- View vCenter Operations Manager Status Information
- Start or StopvCenter Operations Manager Services
- Viewing and Managing System Log Files
- Delete Old Data in the File System Database
- Run the Audit Report
- Modify Global Settings
- Modify Global Settings for Virtual Environments
- Create a Support Bundle
- Resolving Administrative System Alerts
- Analytics FSDB Overloaded
- Analytics Threshold Checking Overloaded
- Collector Is Down
- Controller Is Unable to Connect to MQ
- DataQueue Is Filling Up
- Describe Failed
- Failed to Repair Corrupted FSDB Files
- File Queue Is Full
- FSDB Files Corrupted for Resources
- FSDB Storage Drive Free Space Is Less Than 10%
- No DT Processors Connected
- One or More Resources Were Not Started
- Outbound Alert Send Failed
- Replication MQ Sender Is Blocked
- Backing Up and Recovering Data
- Using System Tools
- Summary of vCenter Operations Manager System Tools
- Check the FSDB and Repair Problems
- Move the FSDB
- View Resources in the FSDB
- Remove System-Generated Metrics from the FSDB
- Monitor vCenter Operations Manager Services in JConsole
- Verify Server to Collector Communication
- Configuring and Running the Repository Adapter
- Configure Database Connections for the Repository Adapter
- Set the Repository Adapter Schedule
- Configure the Source and Destination Columns for the Repository Adapter
- Set Operation Options for the Repository Adapter
- Configure Data Export Values for the Repository Adapter
- Start the Repository Adapter
- conf.properties File
- Configuring and Running runvcopsServerConfiguration
- Using the FSDB JDBC Driver
- Index
Controller Log File Messages
These messages in the controller.log file might indicate a problem with an SQL Server database.
ERROR [Thread-1] com.integrien.alive.ui.util.MainPortalListener.contextInitialized -
org.hibernate.exception.GenericJDBCException: Cannot open connection
ERROR [Thread-5] com.integrien.alive.common.hibernate.dao.BaseDAO.executeInTransaction - Cannot
open connection
org.hibernate.exception.GenericJDBCException: Cannot open connection
These messages indicate that the ActiveMQ service is not available.
ERROR [http-80-3]
com.integrien.alive.common.rmi.MetricDataDistributorClient.getCurrentHealthsFromMemory -
MetricDataDistributorClient -- Failed to Receive Metric Data. Re-initializing Failed. Null
ERROR [Communicator] com.integrien.alive.controller.collector.CommunicatorThread.connect - Can
not connect to the MQ Broker. The reason is Could not connect to broker URL:
tcp://localhost:61616?wireFormat.maxInactivityDuration=0. Reason: java.net.ConnectException:
Connection refused: connect
These messages indicate that the vcopsWebService service started successfully.
INFORMATION [Thread-1] com.integrien.alive.ui.util.MainPortalListener.contextInitialized -
AliveService has been started 10.1.11.40
INFORMATION [Describe thread] com.integrien.alive.controller.collector.DescribeThread.describe -
Staring describe
INFORMATION [Describe thread]
com.integrien.alive.controller.collector.DescribeUtils.constructAdapterDescribes - Beginning
Describe on Controller
INFORMATION [Describe thread] com.integrien.alive.controller.collector.DescribeThread.describe -
Finished describe in 2281 ms
Collector Log File Messages
These messages in the collector.log file indicate that the ActiveMQ service is down.
2010-04-12 19:04:10,715 ERROR [ActiveMQ Task]
org.apache.activemq.transport.failover.FailoverTransport.doReconnect - Failed to connect to
transport after: 5 attempt(s)
2010-04-12 19:04:10,715 ERROR [Communicator]
com.integrien.alive.collector.CommunicatorThread.connect - Can not connect to the MQ Broker. The
reason is Connection refused: connect
These messages indicate that the CollectorServer service started successfully.
INFORMATION [WrapperListener_start_runner] com.integrien.alive.collector.CollectorMain.start -
CollectorService has been started 10.1.11.40
INFORMATION [Communicator] com.integrien.alive.collector.CommunicatorThread.connect - Collector
by id 1 successfully connected to MQ.
INFORMATION [Thread-5] com.integrien.alive.collector.Collector.describe - Beginning Describe on
Collector
INFORMATION [Thread-5] com.integrien.alive.collector.Collector.describe - Describe succeeded
Chapter 8 Performing Basic System Administration Tasks
VMware, Inc. 95