Veritas CloudPoint Administrator's Guide
- Getting started with CloudPoint
- Section I. Installing and configuring CloudPoint
- Preparing for installation
- Deploying CloudPoint
- Deploying CloudPoint in the AWS cloud
- Using plug-ins to discover assets
- Configuring off-host plug-ins
- AWS plug-in configuration notes
- Google Cloud Platform plug-in configuration notes
- Microsoft Azure plug-in configuration notes
- HPE RMC plug-in configuration notes
- NetApp plug-in configuration notes
- Hitachi plug-in configuration notes
- InfiniBox plug-in configuration notes
- About CloudPoint plug-ins and assets discovery
- Configuring the on-host agents and plug-ins
- Oracle plug-in configuration notes
- Protecting assets with CloudPoint's agentless feature
- Preparing for installation
- Section II. Configuring users
- Section III. Protecting and managing data
- User interface basics
- Indexing and classifying your assets
- Protecting your assets with policies
- Tag-based asset protection
- Replicating snapshots for added protection
- Managing your assets
- About snapshot restore
- Single file restore requirements and limitations
- Additional steps required after a SQL Server snapshot restore
- Monitoring activities with notifications and the job log
- Protection and disaster recovery
- Section IV. Maintaining CloudPoint
- CloudPoint logging
- Troubleshooting CloudPoint
- Working with your CloudPoint license
- Managing CloudPoint agents and plug-ins
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Section V. Reference
Troubleshooting CloudPoint logging
If the flexsnap-coordinator service is down
If the flexsnap-coordinator
service itself is down, you cannot use the flexsnap-log
utility to obtain the logs. In such a case, you can retrieve the logs of a CloudPoint service from the logs of the flexsnap-fluentd
container itself.
Use the following command:
# sudo docker logs flexsnap-fluentd -f | grep <flexsnap-service name>
If the CloudPoint installation fails with a fluentd logging driver error
If the CloudPoint installation fails with an error that the CloudPoint container services are unable to find the fluentd
logging driver, do the following:
Verify that the
flexsnap-fluentd
service is running.Run the following command on the CloudPoint host:
# sudo docker ps
The command output should display the
fluentd
container as running.If the
fluentd
service has not started on the CloudPoint host, look at the errors in theflexsnap-fluentd
service logs.Use the following command:
# sudo docker logs flexsnap-fluentd
In general, if the flexsnap-log
utility fails to display log messages, you can retrieve the logs from the flexsnap-fluentd
container log using Docker commands.