JMOtto
Contributor
Contributor

vCD Application Initialization Failure Missing: com.vmware.vcloud.backend-core

Hi

Hopefully someone can help me out with this, Just installed vCloud Director 5.5.0.1323688 on a RHEL 6 system, the Application initialization fails at Missing: com.vmware.vcloud.backend-core. I have verified that DNS forward and reverse resolves successfully,

Logs from vcloud-container-info.log

2013-11-28 14:31:20,907 | INFO| g Context: com.vmware.vcloud.service-extensibility | ServiceInitializationTracker   | Application Initialization: 63% complete. Subsystem com.vmware.vcloud.service-extensibility started |
2013-11-28 14:31:21,161 | INFO| Spring Context: com.vmware.vcloud.backend-core | BootstrapXmlApplicationContext | Refreshing BootstrapXmlApplicationContext(bundle=com.vmware.vcloud.backend-core, config=osgibundle:/META-INF/spring/*.xml): startup date [Thu Nov 28 14:31:21 CST 2013]; root of context hierarchy |
2013-11-28 14:31:21,161 | INFO| Spring Context: com.vmware.vcloud.backend-core | BootstrapXmlApplicationContext | Application Context service already unpublished |
2013-11-28 14:31:45,307 | INFO| Spring Context: com.vmware.vcloud.backend-core | BootstrapXmlApplicationContext | Bean '(inner bean)' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) |
2013-11-28 14:31:45,350 | INFO| Spring Context: com.vmware.vcloud.backend-core | BootstrapXmlApplicationContext | Bean 'org.springframework.aop.aspectj.AspectJPointcutAdvisor#0' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) |
2013-11-28 14:31:45,352 | INFO| Spring Context: com.vmware.vcloud.backend-core | BootstrapXmlApplicationContext | Bean '(inner bean)#2' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) |
2013-11-28 14:31:45,354 | INFO| Spring Context: com.vmware.vcloud.backend-core | BootstrapXmlApplicationContext | Bean 'org.springframework.aop.aspectj.AspectJPointcutAdvisor#1' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) |
2013-11-28 14:31:45,389 | INFO| Spring Context: com.vmware.vcloud.backend-core | BootstrapXmlApplicationContext | Bean '(inner bean)#4' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) |
2013-11-28 14:31:45,416 | INFO| Spring Context: com.vmware.vcloud.backend-core | BootstrapXmlApplicationContext | Bean 'org.springframework.aop.aspectj.AspectJPointcutAdvisor#2' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) |
2013-11-28 14:31:45,421 | INFO| Spring Context: com.vmware.vcloud.backend-core | BootstrapXmlApplicationContext | Bean '(inner bean)#6' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) |
2013-11-28 14:31:45,423 | INFO| Spring Context: com.vmware.vcloud.backend-core | BootstrapXmlApplicationContext | Bean 'org.springframework.aop.aspectj.AspectJPointcutAdvisor#3' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) |
2013-11-28 14:31:45,425 | INFO| Spring Context: com.vmware.vcloud.backend-core | BootstrapXmlApplicationContext | Bean '(inner bean)#8' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) |
2013-11-28 14:31:45,426 | INFO| Spring Context: com.vmware.vcloud.backend-core | BootstrapXmlApplicationContext | Bean 'org.springframework.aop.aspectj.AspectJPointcutAdvisor#4' is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) |
2013-11-28 14:34:03,153 | INFO| Spring Context: com.vmware.vcloud.backend-core | ShieldSessionManager      | Starting ... |
2013-11-28 14:34:05,956 | INFO| Spring Context: com.vmware.vcloud.backend-core | ImportServiceImpl         | ImportService initializing... |
2013-11-28 14:34:05,957 | INFO| Spring Context: com.vmware.vcloud.backend-core | ImportServiceImpl         | ImportService initialization completed |
2013-11-28 14:34:12,851 | INFO| Spring Context: com.vmware.vcloud.backend-core | JmsUtils                  | Successfully connected to JMS broker |
2013-11-28 14:34:51,822 | INFO| Spring Context: com.vmware.vcloud.backend-core | BackendInit               | Initializing new handlers for VIM updates |
2013-11-28 14:34:51,927 | INFO| Spring Context: com.vmware.vcloud.backend-core | BackendInit               | Initializing Failover Manager |
2013-11-28 14:34:51,953 | INFO| Spring Context: com.vmware.vcloud.backend-core | FailoverServiceManagerImpl| Invoking Init() |
2013-11-28 14:34:51,953 | INFO| Spring Context: com.vmware.vcloud.backend-core | FailoverServiceManagerImpl| Will use JMS scheduling. |
2013-11-28 14:34:51,954 | INFO| Spring Context: com.vmware.vcloud.backend-core | FailoverMessageServiceImpl| Subscribing listener com.vmware.ssdc.backendbase.failover.impl.FailoverServiceManagerImpl |
2013-11-28 14:34:51,954 | INFO| Spring Context: com.vmware.vcloud.backend-core | FailoverServiceManagerImpl| Scheduling coordinator service as part of startup. |
2013-11-28 14:34:51,978 | INFO| Spring Context: com.vmware.vcloud.backend-core | FailoverServiceManagerImpl| Scheduling service [CoordinatorServiceData: servicetype: Coordinator, jobname: Coordinator, jobgroup: CoordinatorGroup] |
2013-11-28 14:34:52,045 | INFO| Spring Context: com.vmware.vcloud.backend-core | FailoverServiceManagerImpl| Service [CoordinatorServiceData: servicetype: Coordinator, jobname: Coordinator, jobgroup: CoordinatorGroup] scheduled for execution. |
2013-11-28 14:34:52,109 | INFO| Spring Context: com.vmware.vcloud.backend-core | FailoverServiceManagerImpl| Starting ActiveMQ monitor. Will check state every 600,000ms. Message timeout is 5,000ms |
2013-11-28 14:34:52,111 | INFO| Spring Context: com.vmware.vcloud.backend-core | FailoverMessageServiceImpl| Subscribing listener class com.vmware.ssdc.backendbase.failover.impl.ActiveMQMonitorTimerTask |
2013-11-28 14:35:02,835 | INFO| Spring Context: com.vmware.vcloud.backend-core | ThumbnailService          | 2 thumbnail request consumer for creating buckets initialized |
2013-11-28 14:35:02,856 | INFO| Spring Context: com.vmware.vcloud.backend-core | ThumbnailService          | Started 2 thumnail request consumers |
2013-11-28 14:35:08,051 | INFO| Spring Context: com.vmware.vcloud.backend-core | VAppServiceImpl           | VAppService initializing... |
2013-11-28 14:35:08,056 | INFO| Spring Context: com.vmware.vcloud.backend-core | VAppServiceImpl           | VAppService initialized |
2013-11-28 14:35:14,376 | INFO| Spring Context: com.vmware.vcloud.backend-core | BackendService            | Starting back end... |
2013-11-28 14:35:14,376 | INFO| Spring Context: com.vmware.vcloud.backend-core | BackendService            | Back end started successfully. |
2013-11-28 14:35:14,776 | INFO| Spring Context: com.vmware.vcloud.backend-core | BackendService            | Start timer (com.vmware.ssdc.backend.monitoring.KerberosSyncTimer), delay: 600 sec |
2013-11-28 14:35:14,989 | INFO| Spring Context: com.vmware.vcloud.backend-core | BackendService            | Start timer (com.vmware.ssdc.backend.monitoring.TimerUpdateTimer), delay: 60 sec |
2013-11-28 14:36:21,232 | FATAL| Cell Application     | BundleStartupAction       | Application startup event: Error during application startup. Shutting down. (Missing: com.vmware.vcloud.backend-core) |

VMware vCloud Director 5.5.0.1323688, Central Standard Time,

vcloud-container-debug.log

2013-11-28 14:34:52,275 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | ValidationServiceImpl     | Starting service: ValidationService |
2013-11-28 14:34:52,276 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | ValidationServiceImpl     | Service start complete: ValidationService |
2013-11-28 14:34:52,276 | DEBUG| ValidationThread     | ValidationServiceImpl     | validationThread started |
2013-11-28 14:34:52,432 | DEBUG| activemq-monitor-timer| FailoverMessageServiceImpl| Published JMS message ID:(Name removed)-54291-1385670163149-2:8:1:1:1 |
2013-11-28 14:34:52,448 | DEBUG| activemq-monitor-timer| FailoverMessageServiceImpl| Request [id = failoverMessage-cid:60b5e850-ad32-4512-93e3-508512b3965f-ciid:1-mid:1, type = Request, src instance = 1 (id = 60b5e850-ad32-4512-93e3-508512b3965f), target instance = 1, timestamp = Thu Nov 28 14:34:52 CST 2013] published. Waiting for response until timeout=5,000ms |
2013-11-28 14:34:52,450 | DEBUG| ActiveMQ Session Task| FailoverMessageServiceImpl| Received JMS message ID:(Name Removed)-54291-1385670163149-2:8:1:1:1 |
2013-11-28 14:34:52,462 | DEBUG| ActiveMQ Session Task| FailoverMessageServiceImpl| Received message [id = failoverMessage-cid:60b5e850-ad32-4512-93e3-508512b3965f-ciid:1-mid:1, type = Request, src instance = 1 (id = 60b5e850-ad32-4512-93e3-508512b3965f), target instance = 1, timestamp = Thu Nov 28 14:34:52 CST 2013] on cell instance 1 |
2013-11-28 14:34:52,469 | DEBUG| ActiveMQ Session Task| FailoverMessageServiceImpl| Published JMS message ID:(name removed)-54291-1385670163149-2:8:1:1:2 |
2013-11-28 14:34:52,469 | DEBUG| ActiveMQ Session Task| FailoverMessageServiceImpl| Response [id = failoverMessage-cid:60b5e850-ad32-4512-93e3-508512b3965f-ciid:1-mid:2, type = Response, src instance = 1 (id = 60b5e850-ad32-4512-93e3-508512b3965f), target instance = 1, timestamp = Thu Nov 28 14:34:52 CST 2013] published for request [id = failoverMessage-cid:60b5e850-ad32-4512-93e3-508512b3965f-ciid:1-mid:1, type = Request, src instance = 1 (id = 60b5e850-ad32-4512-93e3-508512b3965f), target instance = 1, timestamp = Thu Nov 28 14:34:52 CST 2013] |
2013-11-28 14:34:52,474 | DEBUG| ActiveMQ Session Task| FailoverMessageServiceImpl| Received JMS message ID:(Name removed)-54291-1385670163149-2:8:1:1:2 |
2013-11-28 14:34:52,475 | DEBUG| ActiveMQ Session Task| FailoverMessageServiceImpl| Received message [id = failoverMessage-cid:60b5e850-ad32-4512-93e3-508512b3965f-ciid:1-mid:2, type = Response, src instance = 1 (id = 60b5e850-ad32-4512-93e3-508512b3965f), target instance = 1, timestamp = Thu Nov 28 14:34:52 CST 2013] on cell instance 1 |
2013-11-28 14:34:52,476 | DEBUG| ActiveMQ Session Task| FailoverMessageServiceImpl| WaitHandle released for response [id = failoverMessage-cid:60b5e850-ad32-4512-93e3-508512b3965f-ciid:1-mid:2, type = Response, src instance = 1 (id = 60b5e850-ad32-4512-93e3-508512b3965f), target instance = 1, timestamp = Thu Nov 28 14:34:52 CST 2013] |
2013-11-28 14:35:02,835 | INFO| Spring Context: com.vmware.vcloud.backend-core | ThumbnailService          | 2 thumbnail request consumer for creating buckets initialized |
2013-11-28 14:35:02,856 | INFO| Spring Context: com.vmware.vcloud.backend-core | ThumbnailService          | Started 2 thumnail request consumers |
2013-11-28 14:35:03,319 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | ReplicatedEhCacheFactoryBean   | Using existing EHCache cache region 'com.vmware.vcloud.caches.IDPMetadataCache' |
2013-11-28 14:35:03,511 | DEBUG| VMTransport          | CellAuthenticatedBrokerFactory | Successfully authenticated user |
2013-11-28 14:35:08,051 | INFO| Spring Context: com.vmware.vcloud.backend-core | VAppServiceImpl           | VAppService initializing... |
2013-11-28 14:35:08,052 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Bundle symbolic name for task executor com.vmware.vcloud.vapp.impl.VAppServiceImpl@4ae98c2 is: com.vmware.vcloud.backend-core |
2013-11-28 14:35:08,052 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_UPDATE_VM' |
2013-11-28 14:35:08,052 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'TEMPLATE_UPDATE_VM' |
2013-11-28 14:35:08,053 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_DEPLOY' |
2013-11-28 14:35:08,053 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_UNDEPLOY_POWER_OFF' |
2013-11-28 14:35:08,053 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_UNDEPLOY_SUSPEND' |
2013-11-28 14:35:08,053 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_EJECT_CD_FLOPPY' |
2013-11-28 14:35:08,053 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_INSERT_CD_FLOPPY' |
2013-11-28 14:35:08,053 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_RELOCATE_VM' |
2013-11-28 14:35:08,053 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_CONSOLIDATE_VM' |
2013-11-28 14:35:08,053 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_UPGRADE_HW_VERSION' |
2013-11-28 14:35:08,054 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_ATTACH_DISK' |
2013-11-28 14:35:08,054 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_DETACH_DISK' |
2013-11-28 14:35:08,054 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_CHECK_VM_COMPLIANCE' |
2013-11-28 14:35:08,054 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_MIGRATE_VMS' |
2013-11-28 14:35:08,054 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_CREATE_SNAPSHOT' |
2013-11-28 14:35:08,054 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_REVERT_TO_CURRENT_SNAPSHOT' |
2013-11-28 14:35:08,054 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_REMOVE_ALL_SNAPSHOTS' |
2013-11-28 14:35:08,054 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'EXTENSION_ASSOCIATE_SOI_VM' |
2013-11-28 14:35:08,055 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'EXTENSION_DISASSOCIATE_SOI_VM' |
2013-11-28 14:35:08,055 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Bundle symbolic name for task executor com.vmware.vcloud.vapp.impl.VAppServiceImpl@4ae98c2 is: com.vmware.vcloud.backend-core |
2013-11-28 14:35:08,055 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_DISCARD_SUSPENDED_STATE' |
2013-11-28 14:35:08,055 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_RESUME' |
2013-11-28 14:35:08,055 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_INSTALL_TOOLS' |
2013-11-28 14:35:08,055 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_REBOOT_GUEST' |
2013-11-28 14:35:08,056 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_SUSPEND' |
2013-11-28 14:35:08,056 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_SHUTDOWN_GUEST' |
2013-11-28 14:35:08,056 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_RESET' |
2013-11-28 14:35:08,056 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | TaskServiceImpl           | Registered executor for task name 'VAPP_POWER_OFF' |
2013-11-28 14:35:08,056 | INFO| Spring Context: com.vmware.vcloud.backend-core | VAppServiceImpl           | VAppService initialized |
2013-11-28 14:35:14,376 | INFO| Spring Context: com.vmware.vcloud.backend-core | BackendService            | Starting back end... |
2013-11-28 14:35:14,376 | INFO| Spring Context: com.vmware.vcloud.backend-core | BackendService            | Back end started successfully. |
2013-11-28 14:35:14,776 | INFO| Spring Context: com.vmware.vcloud.backend-core | BackendService            | Start timer (com.vmware.ssdc.backend.monitoring.KerberosSyncTimer), delay: 600 sec |
2013-11-28 14:35:14,989 | INFO| Spring Context: com.vmware.vcloud.backend-core | BackendService            | Start timer (com.vmware.ssdc.backend.monitoring.TimerUpdateTimer), delay: 60 sec |
2013-11-28 14:35:15,090 | DEBUG| Spring Context: com.vmware.vcloud.backend-core | ReactionServiceImpl       | ReactionServiceImpl initialized. |
2013-11-28 14:35:53,753 | DEBUG| VC.TaskManager.NonActiveTaskCompletionsPurger | TaskManager               | Marked 0 tasks for purging |
2013-11-28 14:35:53,845 | DEBUG| VC.TaskManager.NonActiveTaskCompletionsPurger | TaskManager               | Purged 0 tasks. |
2013-11-28 14:36:03,226 | DEBUG| Bound HTTP Request Log Files | SizeBoundedNCSARequestLog | Found log file: 2013_11_28.request.log (Size = 22,090 bytes} |
2013-11-28 14:36:03,227 | DEBUG| Bound HTTP Request Log Files | SizeBoundedNCSARequestLog | Request log processing complete. Total log file size: 22,090 bytes; Deleted 0 request log files |
2013-11-28 14:36:21,225 | DEBUG| Cell Application     | Out                       | Application startup event: Error during application startup. Shutting down. (Missing: com.vmware.vcloud.backend-core) |
2013-11-28 14:36:21,232 | FATAL| Cell Application     | BundleStartupAction       | Application startup event: Error during application startup. Shutting down. (Missing: com.vmware.vcloud.backend-core) |
0 Kudos
0 Replies