Opened 13 years ago
Closed 13 years ago
#9672 closed defect (fixed)
TestManager Fails with MySQL
Reported by: | Owned by: | Roberto Longobardi | |
---|---|---|---|
Priority: | high | Component: | TestManagerForTracPlugin |
Severity: | critical | Keywords: | |
Cc: | Trac Release: | 0.11 |
Description
I am trying to set up test manager as we migrate to a new system. I have tested this on two systems (System A and System B) Here are my steps and environment:
System A::
{ Ubuntu 10.10 }
{ Trac: .12 }
{ Python: 2.6.6 }
{ easy_install: distro 0.6.14 }
{ Genshi: .6 }
{ MySQL: ver 14.14 distro 5.1.49 on the LOCAL machine }
{ Apache: 2.2.16 }
{ mod_wsgi: 3.3 }
{ MySQLforPython: 1.2.3 }
{ Authentication: LDAP }
System B ::
{ Ubuntu 10.10 }
{ Trac: .12.2 }
{ Python: 2.6.6 }
{ easy_install: distro 0.6.14 }
{ Genshi: .6 }
{ MySQL: ver 14.14 distro 5.1.49 on the REMOTE machine }
{ Apache: 2.2.16 }
{ mod_wsgi: 3.3 }
{ MySQLforPython: 1.2.3 }
{ Authentication: LDAP }
Installations:
- As instructed via the BUILD.txt and INSTALLATION.txt files.
- Did NOT opt to build into the environment for System B.
- Did opt to build into the environment for System A.
Tests:
Enabled all componets via Admin GUI
Restart Apache
Upgrade Database via sudo trac-admin /path/to/my/environment upgrade
Upgrade Wiki via sudo trac-admin /path/to/my/environment wiki upgrade
Get 500 interal server error.
Log files attached.
NOTE: Error in both:
Error getting configuration property 'testcatalog_dbversion' from table 'tracgenericclassconfig'
NOTE: A seperate issue with System B, it had to be upgraded with flag --no-backup
Attachments (2)
Change History (3)
Changed 13 years ago by
Attachment: | trac_system_A.log added |
---|
Changed 13 years ago by
Attachment: | trac_system_B.log added |
---|
comment:1 Changed 13 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Please note: found a resolution to this issue.
Was not activating plugins in the same order as listed in the INSTALLATION.txt, but rather a blanketed activation of all.
When activated in sequence the issue was resolved.
If possible, please update INSTALLATION.txt so others might have less of a headache with this issue.