VMware vCloud Director Log files

Working on my home lab the other day, I had forgotten where the log files were kept for VMware vCloud Director. I thought I would document there location and what the purpose of these log files are for.

Path to log files:/opt/vmware/cloud-director/logs

UPDATE: Path to log files as of vCloud Director 1.5 changed to /opt/vmware/vcloud-director/logs

cell.log
The first log file that I always use, is the cell.log. This provides information on what status the cell services and application start up are at. Generally I use tail -f to view the live status when starting a vCD Cell.

Application startup begins: 1/18/11 10:48 PM
Successfully bound network port: 80 on host address: 192.168.10.152
Successfully bound network port: 443 on host address: 192.168.10.152
Application Initialization: 9% complete. Subsystem ‘com.vmware.vcloud.common.core’ started
Successfully connected to database: jdbc:oracle:thin:@192.168.10.150:1521/xe
Successfully bound network port: 443 on host address: 192.168.10.53
Successfully bound network port: 61616 on host address: 192.168.10.152
Successfully bound network port: 61613 on host address: 192.168.10.152
Application Initialization: 18% complete. Subsystem ‘com.vmware.vcloud.common-util’ started
Application Initialization: 27% complete. Subsystem ‘com.vmware.vcloud.consoleproxy’ started
Application Initialization: 36% complete. Subsystem ‘com.vmware.vcloud.vlsi-core’ started
Successfully verified transfer spooling area: /opt/vmware/cloud-director/data/transfer
Application Initialization: 45% complete. Subsystem ‘com.vmware.vcloud.vim-proxy’ started
Application initialization detailed status report: 45% complete
com.vmware.vcloud.backend-core Subsystem Status: [WAITING]
com.vmware.vcloud.ui.configuration Subsystem Status: [WAITING]
com.vmware.vcloud.consoleproxy Subsystem Status: [COMPLETE]
com.vmware.vcloud.vim-proxy Subsystem Status: [COMPLETE]
com.vmware.vcloud.common-util Subsystem Status: [COMPLETE]
com.vmware.vcloud.ui-vcloud-webapp Subsystem Status: [WAITING]
com.vmware.vcloud.rest-api-handlers Subsystem Status: [WAITING]
com.vmware.vcloud.common.core Subsystem Status: [COMPLETE]
com.vmware.vcloud.vlsi-core Subsystem Status: [COMPLETE]
com.vmware.vcloud.jax-rs-servlet Subsystem Status: [WAITING]
com.vmware.vcloud.imagetransfer-server Subsystem Status: [WAITING]

Application Initialization: 54% complete. Subsystem ‘com.vmware.vcloud.backend-core’ started
Application Initialization: 63% complete. Subsystem ‘com.vmware.vcloud.ui.configuration’ started
Application Initialization: 72% complete. Subsystem ‘com.vmware.vcloud.imagetransfer-server’ started
Application Initialization: 81% complete. Subsystem ‘com.vmware.vcloud.rest-api-handlers’ started
Application Initialization: 90% complete. Subsystem ‘com.vmware.vcloud.jax-rs-servlet’ started
Application Initialization: 100% complete. Subsystem ‘com.vmware.vcloud.ui-vcloud-webapp’ started
Application Initialization: Complete. Server is ready in 3:38 (minutes:seconds)
Successfully initialized ConfigurationService session factory
Successfully started scheduler
Successfully started remote JMX connector on port 8999

vmware-vcd-watchdog.log
This log file shows any errors or information (depending on the debug level configured) that the cell may be having.

A healthy watchdog.log looks similar to the below:

2011-01-18 22:47:04 | INFO | vmware-vcd-watchdog started
2011-01-18 22:47:06 | INFO | Started vmware-vcd-cell (pid=12165)

If a failure has occurred you may see something similar to the below:

2011-01-18 22:32:39 | INFO | vmware-vcd-watchdog started
2011-01-18 22:32:41 | INFO | Started vmware-vcd-cell (pid=2933)
2011-01-18 22:39:41 | ALERT | vmware-vcd-cell is dead but /var/run/vmware-vcd-cell.pid exists, attempting to restart it
2011-01-18 22:39:44 | INFO | Started vmware-vcd-cell (pid=3438)

vcloud-container-info.log
This log file shows the status of the installation. If you have any errors or failures during the install, this log file will provide you with the detail required to troubleshoot the installation failure.

VMware Cloud Director 1.0.0.285979 Greenwich Mean Time
2011-01-21 15:04:05,082 | ERROR | main | ConfigAgent | Error: file could not be found: /root/response.properties |
VMware Cloud Director 1.0.0.285979 Greenwich Mean Time

vcloud-container-debug.log
This log file shows the debugging information. The detail in this log file will be dependant upon the level of debugging set.

2011-01-24 14:50:07,364 | DEBUG | VC.TaskManager.NonActiveTaskCompletionsPurger | TaskManager | Marked 0 tasks for purging |
2011-01-24 14:50:07,364 | DEBUG | VC.TaskManager.NonActiveTaskCompletionsPurger | TaskManager | Purged 0 tasks. |
2011-01-24 14:51:07,375 | DEBUG | VC.TaskManager.NonActiveTaskCompletionsPurger | TaskManager | Marked 0 tasks for purging |
2011-01-24 14:51:07,376 | DEBUG | VC.TaskManager.NonActiveTaskCompletionsPurger | TaskManager | Purged 0 tasks. |
2011-01-24 14:52:07,386 | DEBUG | VC.TaskManager.NonActiveTaskCompletionsPurger | TaskManager | Marked 0 tasks for purging |
2011-01-24 14:52:07,386 | DEBUG | VC.TaskManager.NonActiveTaskCompletionsPurger | TaskManager | Purged 0 tasks. |
2011-01-24 14:53:03,549 | DEBUG | Quartz-pool-1-thread-1840 | FailoverServiceManagerImpl | checking for any failed cells from current cell cloud-vcd2.cloud.local (id = 83, uuid = 727cade4-79cd-454f-85f0-ae6f6a959c87) |
2011-01-24 14:53:07,396 | DEBUG | VC.TaskManager.NonActiveTaskCompletionsPurger | TaskManager | Marked 0 tasks for purging |
2011-01-24 14:53:07,397 | DEBUG | VC.TaskManager.NonActiveTaskCompletionsPurger | TaskManager | Purged 0 tasks. |
2011-01-24 14:53:10,293 | DEBUG | Quartz-pool-1-thread-1840 | LeaseManagementJob | Executing lease management job |
2011-01-24 14:54:07,407 | DEBUG | VC.TaskManager.NonActiveTaskCompletionsPurger | TaskManager | Marked 0 tasks for purging |
2011-01-24 14:54:07,407 | DEBUG | VC.TaskManager.NonActiveTaskCompletionsPurger | TaskManager | Purged 0 tasks. |

, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,

2 Responses to VMware vCloud Director Log files

  1. Brian T January 14, 2016 at 12:29 am #

    /opt/vmware/cloud-director/logs should be /opt/vmware/vcloud-director/logs

    • admin January 14, 2016 at 3:09 pm #

      Yes your right. Problem is when this article was written, it was cloud-director! Thanks I will update the article 🙂

Leave a Reply

Copyright David Hill Group Limited

Powered by WordPress. Designed by Woo Themes

%d bloggers like this: