Hi All
during installation of the VCloud Director we got this error, we did some troubleshooting with this results, someone has an idea about why?
Thanks for your help
Demetrio
[root@vCloudC402 logs]# service vmware-vcd status
vmware-vcd-watchdog is running
vmware-vcd-cell is dead, but pidfile exists
[root@vCloudC402 logs]#
[root@vCloudC402 logs]# service vmware-vcd restart
Stopping vmware-vcd-watchdog: [ OK ]
Stopping vmware-vcd-cell: [ OK ]
Starting vmware-vcd-watchdog: [ OK ]
Starting vmware-vcd-cell [ OK ]
[root@Centos7-Test ~]# sqlplus "teiaxeio1/summerio@147.214.6.51:1521/AXECLOUD"
SQL*Plus: Release 12.1.0.2.0 Production on Tue Jun 13 15:20:03 2017
Copyright (c) 1982, 2014, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Release 11.2.0.4.0 - 64bit Production
##vcloud-container-debug.log
2017-06-13 15:13:49,067 | INFO | Spring Context: com.vmware.vcloud.ui.h5cellapp | BundleWarScanner | WAR Bundle found: h5-webapp - vCloud UI HTML5 Web Application (com.vmware.vcloud.h5-webapp) |
2017-06-13 15:13:49,078 | INFO | Spring Context: com.vmware.vcloud.ui.h5cellapp | WarBundleManager | WAR Bundle: h5-webapp - vCloud UI HTML5 Web Application (com.vmware.vcloud.h5-webapp) has Context Path: /tenant |
2017-06-13 15:13:49,100 | DEBUG | WebApp: com.vmware.vcloud.h5-webapp on: /tenant | DefaultJettyWarDeployer | Unpacking bundle h5-webapp - vCloud UI HTML5 Web Application (com.vmware.vcloud.h5-webapp) to folder [/opt/vmware/vcloud-director/tmp/jetty-tenant3165691230836904232.osgi] |
2017-06-13 15:13:49,188 | INFO | WebApp: com.vmware.vcloud.h5-webapp on: /tenant | DefaultJettyWarDeployer | Base resource for web application h5-webapp - vCloud UI HTML5 Web Application (com.vmware.vcloud.h5-webapp) is file:/opt/vmware/vcloud-director/tmp/jetty-tenant3165691230836904232.osgi/ |
2017-06-13 15:13:49,362 | INFO | CellApplicationManagerImpl CellApplication starter | Html5CellApplication | Starting bundle: com.vmware.vcloud.h5-webapp |
2017-06-13 15:13:49,364 | DEBUG | OSGI Delegator - listener dispatcher | EventHelper | Dispatcher service is unavailable. Queuing event: Event [id=43128724-90bc-4c76-808b-134a3400f6b5, timestamp=1497359629364, type=com/vmware/vcloud/event/cell/modify, serviceNamespace=com.vmware.vcloud, properties={
cellApplication.intermediateState=STARTING_FROM_STOPPED,
cellApplication.name=com.vmware.vcloud.ui.h5cellapp.Html5CellApplication,
cellApplication.originState=STOPPED,
cellApplication.simpleName=Html5CellApplication,
cellApplication.simpleState=started,
cellApplication.targetState=STARTED,
cellApplication.transitionState=SUCCESS,
currentContext.cell.uuid=,
currentContext.org.id=System(com.vmware.vcloud.entity.org:a93c9db9-7471-3192-8d09-a8f7eeda85f9),
currentContext.success=true,
currentContext.user.id=system(com.vmware.vcloud.entity.user:808cc07b-7092-3666-bcc5-89910188d5e7),
currentContext.user.name=system,
currentContext.user.proxyAddress=,
entity.id=com.vmware.vcloud.common.cell.event.CommonCellEventBuilder$$Lambda$20/406620132@28a0b22a,
entity.type=com.vmware.vcloud.entity.cell,
}] |
2017-06-13 15:13:49,455 | INFO | WebApp: com.vmware.vcloud.h5-webapp on: /tenant | JasperLocator | Found JSP Support for: h5-webapp - vCloud UI HTML5 Web Application (com.vmware.vcloud.h5-webapp) |
##Cell.log
All required system properties are present
An unspecified error occurred during application start
All required local configuration properties are present
Successfully bound network port: 80 on host address: 10.33.32.4
Successfully bound network port: 443 on host address: 10.33.32.4
Successfully bound network port: 8999 on host address: 10.33.32.4
All required local configuration properties are present
Successfully initialized system cryptography
Successfully configured HTTP SSL Connector from certificate store: /opt/vmware/vcloud-director/etc/certificates
Current locale "en" verified successfully.
Bootstrap application: complete
Application startup event: Waiting for subsystem 'com.vmware.vcloud.common.core'
Application startup event: Waiting for subsystem 'com.vmware.vcloud.computeservice.broker'
Application startup event: Waiting for subsystem 'com.vmware.vcloud.consoleproxy'
Application startup event: Waiting for subsystem 'com.vmware.vcloud.networking-server'
Application startup event: Waiting for subsystem 'com.vmware.vcloud.cloud-proxy-server'
Application startup event: Subsystem 'com.vmware.vcloud.cloud-proxy-server' startup initiated.
Application startup event: Subsystem 'com.vmware.vcloud.networking-server' startup initiated.
Application startup begins: Subsystem 'com.vmware.vcloud.cloud-proxy-server' at 6/13/17 3:14 PM
Application startup begins: Subsystem 'com.vmware.vcloud.networking-server' at 6/13/17 3:14 PM
Application startup event: Subsystem 'com.vmware.vcloud.common.core' startup initiated.
Application startup begins: Subsystem 'com.vmware.vcloud.common.core' at 6/13/17 3:14 PM
Error starting application: Database schema version is not compatible with this release. Requires version
[ "2.1.9", "6.0.116", "7.0.0", [ "1.0.44", "45.2.0", [ "19.9.0", "11.0.0", "8.0.0" ], [ "6.0.0", "6.0.0" ], [ "14.0.0", "4.0.0", "6.0.0", "9.0.0", "5.0.0" ], [ "7.0.0", "3.0.0", "4.0.0", "12.0.0", "2.0.0", "2.0.0", "7.0.0", "3.0.0", "6.0.0", "5.0.0", "15.0.0", "5.0.0", "20.0.0" ] ], "71.0.0" ]
but found version
[ "2.1.9", "6.0.116", "7.0.0", [ "1.0.44", "45.2.0", [ "19.9.0", "11.0.0", "8.0.0" ], [ "6.0.0", "6.0.0" ], [ "3.0.0.transition", "4.0.0", "6.0.0", "9.0.0", "5.0.0" ], [ "7.0.0", "3.0.0", "4.0.0", "12.0.0", "2.0.0", "2.0.0", "7.0.0", "3.0.0", "6.0.0", "5.0.0", "15.0.0", "5.0.0", "20.0.0" ] ], "0.0.0.transition" ]
##vmware-vcd-watchdog.log
2017-06-13 15:06:43 | WARN | Server status returned HTTP/1.1 404
2017-06-13 15:07:43 | ALERT | vmware-vcd-cell is dead but /var/run/vmware-vcd-cell.pid exists, attempting to restart it
2017-06-13 15:07:50 | INFO | Started vmware-vcd-cell (pid=20164)
2017-06-13 15:07:53 | WARN | Server status returned HTTP/1.1 404
2017-06-13 15:08:53 | ALERT | vmware-vcd-cell is dead but /var/run/vmware-vcd-cell.pid exists, attempting to restart it
2017-06-13 15:09:00 | INFO | Started vmware-vcd-cell (pid=20643)
2017-06-13 15:09:04 | WARN | Server status returned HTTP/1.1 404
2017-06-13 15:10:04 | ALERT | vmware-vcd-cell is dead but /var/run/vmware-vcd-cell.pid exists, attempting to restart it
2017-06-13 15:10:11 | INFO | Started vmware-vcd-cell (pid=21085)
2017-06-13 15:10:14 | WARN | Server status returned HTTP/1.1 404
2017-06-13 15:11:14 | ALERT | vmware-vcd-cell is dead but /var/run/vmware-vcd-cell.pid exists, attempting to restart it
2017-06-13 15:11:21 | INFO | Started vmware-vcd-cell (pid=21513)
2017-06-13 15:11:25 | WARN | Server status returned HTTP/1.1 404
2017-06-13 15:12:25 | ALERT | vmware-vcd-cell is dead but /var/run/vmware-vcd-cell.pid exists, attempting to restart it
2017-06-13 15:12:32 | INFO | Started vmware-vcd-cell (pid=22115)
2017-06-13 15:12:36 | WARN | Server status returned HTTP/1.1 404
2017-06-13 15:13:36 | ALERT | vmware-vcd-cell is dead but /var/run/vmware-vcd-cell.pid exists, attempting to restart it
2017-06-13 15:13:43 | INFO | Started vmware-vcd-cell (pid=22550)
2017-06-13 15:13:47 | WARN | Server status returned HTTP/1.1 404
2017-06-13 15:14:47 | ALERT | vmware-vcd-cell is dead but /var/run/vmware-vcd-cell.pid exists, attempting to restart it
2017-06-13 15:14:54 | INFO | Started vmware-vcd-cell (pid=23064)
2017-06-13 15:14:57 | WARN | Server status returned HTTP/1.1 404
2017-06-13 15:15:57 | ALERT | vmware-vcd-cell is dead but /var/run/vmware-vcd-cell.pid exists, attempting to restart it
2017-06-13 15:16:04 | INFO | Started vmware-vcd-cell (pid=23498)
2017-06-13 15:16:07 | WARN | Server status returned HTTP/1.1 404