The exact remediation steps depend on which error you are seeing. Many of these solutions require deleting a 0-byte file or adding an XML root element so that the file contains valid XML. In most cases, you can also recover a problematic file from a backup or copy it from a working peer. After making any of the changes recommended in this article, you must restart the peer.
Possible Errors Caused by Disk Space Exhaustion
Error Message
|
Solution
|
01 Jan 2013 01:01:01,001 ERROR GridPeer : Unable to start mandatory component.
com.realops.foundation.component.ComponentStartFailedException: Message[summary=Component failed to start., detail=Component failed to start.]
...Caused by: com.realops.foundation.component.ComponentStartFailedException: Message[summary=Component failed to start., detail=Component failed to start.]
...Caused by: com.realops.foundation.component.ComponentStartFailedException: Message[summary=The Context Component failed to start., detail=The Context Component was unable to start the global context.]
...Caused by: com.realops.foundation.context.ContextStartupFailedException: Message[summary=Unable to start the Global Context., detail=]
...Caused by: com.realops.foundation.context.ContextItemPersistenceException: Message[summary=Unable to load the persisted context items., detail=]
...Caused by: com.realops.common.xml.InvalidXMLFormatException: Message[summary=Unable to parse XML, detail=Unable to parse XML]
...Caused by: org.jdom.input.JDOMParseException: Error on line 388: The element type "suspend" must be terminated by the matching end-tag "</suspend>".
...Caused by: org.xml.sax.SAXParseException: The element type "suspend" must be terminated by the matching end-tag "</suspend>". | A persisted context item file has become corrupted and contains invalid XML. Navigate to [TSO_HOME]/server/grids/[GRID_NAME]/tmp/cache and delete the contents of the directory. |
01 Jan 2013 01:01:01,001 ERROR GridPeer : Unable to start mandatory component from file [peer.xml]
com.realops.foundation.component.ComponentStartFailedException: Message[summary=Component failed to start., detail=Component failed to start.]
...Caused by: com.realops.foundation.component.ComponentStartFailedException: Message[summary=Component failed to start., detail=Component failed to start.]
...Caused by: com.realops.foundation.component.ComponentStartFailedException: Message[summary=Component failed to start., detail=Component failed to start.]
...Caused by: com.realops.common.util.StartupFailedException: Message[summary=, detail=]
...Caused by: com.realops.foundation.gridframework.sharedresource.SharedResourceException: Message[summary=The Context component failed to load the version history for the shared resource "global-context-items"., detail=]
...Caused by: com.realops.common.xml.InvalidXMLFormatException: Message[summary=Unable to parse XML, detail=Unable to parse XML]
...Caused by: org.jdom.input.JDOMParseException: Error on line -1: Premature end of file.
...Caused by: org.xml.sax.SAXParseException: Premature end of file. |
The file [TSO_HOME]/server/grids/[GRID_NAME]/modificationHistory/global-context-items.xml is empty. Add the element <modification-history /> to the file so that TSO has some valid XML to parse.
Or
The folder [TSO_HOME]/server/grids/[GRID_NAME]/tmp/cache is used to persist and cache context items and done of its data has become corrupt. Remove contents of the cache folder and restart
|
01 Jan 2013 01:01:01,001 ERROR BrokerService : Failed to start ActiveMQ JMS Message Broker. Reason: java.io.EOFException
java.io.EOFException | The last ActiveMQ journal file failed during its write and is now left at size 0. Navigate to the folder [TSO_HOME]/server/.jms/activemq-data/ao-grid-framework-embedded-broker/KahaDB/. Copy the files within the directory a safe location and delete the originals. |
01 Jan 2013 01:01:01,001 ERROR ServerManager : Unable to start Grid Peer on grid [DevelopmentGrid]. No shared resource registered under name: staged-adapters
java.lang.IllegalArgumentException: No shared resource registered under name: staged-adapters | The file [TSO_HOME]/server/grids/[GRID_NAME]/modificationHistory/staged-adapters.xml is empty. Add the element <modification-history /> to the file so that TSO has some valid XML to parse. |
| 01 Jan 2013 01:01:01,001 ERROR SeedsMaintainer : Failed to update JXTA's PlatformConfig. | The file [TSO_HOME]/server/.jxta/ro-seeds/rendezvous.xml is empty. Add the element <seeds /> to the file so that TSO has some valid XML to parse. |
|
01 Jan 2013 01:01:01,001 ERROR ERROR CDPLauncher : Fatal error occurred in server manager: Message[summary=Startup failed., detail=]
Summary: Startup failed.
Caused by:
Summary: The attempt to read configuration information failed.
Detail: The attempt to read configuration information from "[PATH]/config/cdps.xml" failed.
Caused by:
Summary: Unable to parse XML
Caused by:
Summary: Error on line -1: Premature end of file.
Caused by:
Summary: Premature end of file.
|
The file [TSO_HOME]/config/cdps.xml is empty. Recreate the file using this format:
<configured-cdps>
<peer id="urn:jxta:uuid-[ID]">
<name>[NAME]</name>
<description></description>
</peer>
</configured-cdps>
Where [NAME] is the name of your Configuration Distribution Peer and [ID] is the Peer ID from the file [TSO_HOME]/config/peer-rankings.xml.
|
If the TSO peer remains in a failed state, please collect the latest logs and send them to BMC Customer Support. It is possible that multiple files were corrupted due to the drive space exhaustion, and the logs will contain more information about the specific problem.
There are a few ways prevent the file system from filling to exhaustion:
- Increase the size of the disk. In the case of small VMs, TrueSight Orchestration may fill the disk with log files or content, and increasing the disk size can give the grid enough room to write its log files, which automatically roll over at a predefined level. BMC recommends free disk space of 10-20 gigabytes, depending on the number of installed components.
- Decrease the amount of logging. If you have added a large amount of logging to the grid, either increasing the number of log files or the size of the log files, you can reset this information to the original levels by editing the peer's log4j.xml file.
- Remove old files from the machine. If TSO is installed on a server with many other programs, these programs may also be consuming unnecessary disk space.
