comanage-users - [comanage-users] Database schema upgrade failed (1.0.6->2.0.0)
Subject: COmanage Users List
List archive
- From: "Matthew X. Economou" <>
- To: <>
- Subject: [comanage-users] Database schema upgrade failed (1.0.6->2.0.0)
- Date: Thu, 25 May 2017 10:48:01 -0400
- Ironport-phdr: 9a23:ooXEYRZUGycygGMK4cskNw//LSx+4OfEezUN459isYplN5qZoMS7bnLW6fgltlLVR4KTs6sC0LuJ9fu7EjNeqb+681k6OKRWUBEEjchE1ycBO+WiTXPBEfjxciYhF95DXlI2t1uyMExSBdqsLwaK+i764jEdAAjwOhRoLerpBIHSk9631+ev8JHPfglEnjSwbLdwIRmsowjcuMYajIljJ60s1hbHv3xEdvhMy2h1P1yThRH85smx/J5n7Stdvu8q+tBDX6vnYak2VKRUAzs6PW874s3rrgTDQhCU5nQASGUWkwFHDBbD4RrnQ5r+qCr6tu562CmHIc37SK0/VDq+46t3ThLjlSEKPCM7/m7KkMx9lK1Urw6uqRJixYDaeY+bOvlifq3dY90XXnZBXt9SWiBdHo+wc5UDAuwcNuhYtYn9oF4OoAOwCQerHuzv1iNIhn/o0qw0zu8uEBvK1xEvEd0St3TUqtL1NKIVUeCowqXD0DLObvxI1jf774jIahAhofaKXb9rcMrR01UvFwXCjlWfs4DlOCmV1usUvmWd8uFuW+Wvi2s9pAFwpDii3sgsiojVhoIV11DL7j91z5oyJd29TkNwfN2qEINIui2EOIZ6WN4uT39mtSog17ELt4S3cSkXxJkh2hXRceaIc5KS7RLmTOuRISl3hHZieL+nghaz/lWsxvf9VsmuzFZKqC1FktbWunAKzRzT5dCLSvp7/ki/xTaCzx7f5+5eLUwpi6bWJYQtzqM+m5YJsEnPAzf6mEDsg6+XckUk9PKo6+PiYrj+qZ6TKYl0igbmMqQuncy/B/81MgkUX2iH/+S807Lj8Vf+QLVQgf06irPZv4zCJcQHuq65BBdY3Zok6xa6FTim1s4XnXYZI15cZRKHlJbmO0vVIP3jCfe/gk+skCtwx/zYJLHhA5PNLmTdn7f7e7Zy9VJcxBQpwd9B+p1UF+JJHPWmDkT2sdXeBxA0dhGvzvz8INR7yo4EX2+TWOmUPL6E4nGS4ed6acyFeJMVtSm1G75tyvXpi3g8nkJXNf250J0QcHC/GNxnOVmfZnWqhc0ORzRZ9jEiRfDn3QXRGQVYYGy/Cvox
Dear all,
The database schema management script threw the following errors during
its run, and I'm not sure how to fix it:
Loading schema from file
/opt/comanage-registry/app//Config/Schema/schema.xml...
Possibly failed to update database schema
Loading schema from file
/opt/comanage-registry/app//Plugin/GrouperProvisioner/Config/Schema/sche
ma.xml...
Possibly failed to update database schema
Loading schema from file
/opt/comanage-registry/app//Plugin/LdapProvisioner/Config/Schema/schema.
xml...
Possibly failed to update database schema
When I try to log into COmanage Registry, I get "An Internal Error Has
Occurred". When I look at the registry's error.log, it has entries
similar to the following:
2017-05-25 13:56:19 Error: [MissingTableException] Table cm_co_themes
for model CoTheme was not found in datasource default.
2017-05-25 13:57:35 Error: [MissingTableException] Table cm_co_services
for model CoService was not found in datasource default.
I've posted the complete logs to
https://gist.github.com/xenophonf/399b1c62ed4ad9211215b6871d4d9438. The
server is running CentOS 7 with MariaDB 5.5, Apache 2.4 (installed via
SCL), PHP 5.6 (also installed via SCL), and Shibboleth 2.6.0 (installed
via OBS).
I tried forcing the schema upgrade to re-run via the following command:
sudo -u apache scl enable httpd24 rh-php56 -- bash ./Console/cake
upgradeVersion -f 1.0.6
This returned errors similar to the above ("Possibly failed to update
database schema").
How should I proceed?
Best wishes,
Matthew
--
"The lyf so short, the craft so longe to lerne."
- [comanage-users] Database schema upgrade failed (1.0.6->2.0.0), Matthew X. Economou, 05/25/2017
- <Possible follow-up(s)>
- RE: [comanage-users] Database schema upgrade failed (1.0.6->2.0.0), Matthew X. Economou, 05/25/2017
- Message not available
- [comanage-users] Database schema upgrade failed (1.0.6->2.0.0), Scott Koranda, 05/25/2017
- Re: [comanage-users] Database schema upgrade failed (1.0.6->2.0.0), Benn Oshrin, 05/25/2017
- RE: [comanage-users] Database schema upgrade failed (1.0.6->2.0.0), Matthew X. Economou, 05/26/2017
- [comanage-users] Database schema upgrade failed (1.0.6->2.0.0), Scott Koranda, 05/25/2017
- Message not available
Archive powered by MHonArc 2.6.19.