#9031 closed defect (fixed)
Trac browser locked up
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | 0.11.7 |
| Component: | version control/browser | Version: | 0.11.6 |
| Severity: | major | Keywords: | mysql |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
There is a Trac installation that operates in r/o mode. The only information that updated is repository browser. It fetches revision from local r/o mirror of subversion repository. Mirror updated by cron job using svnsync.
http://farmanager.rainforce.org/browser
I am not resyncing repository to give a chance to debug the issue.
Attachments (1)
Change History (11)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
It uses MySQL, you are right, but how can I check if it's ill-configured?
comment:5 by , 14 years ago
| Resolution: | duplicate |
|---|---|
| Status: | closed → reopened |
Collation is ok. MySQL 5.0.67-log
- SHOW VARIABLES LIKE 'collation_database'
collation_database utf8_bin
- SHOW CREATE DATABASE farmanager;
CREATE DATABASE `farmanager` /*!40100 DEFAULT CHARACTER SET utf8 COLLATE utf8_bin */
comment:6 by , 14 years ago
Seems like there was no race condition, so resync should give the same error. The offending commit.
comment:7 by , 14 years ago
DB collation is utf8_bin, tables collation is urf8_bin, but column! collation is utf8_unicode_ci. I did't expect that columns have collations too.
trac-admin should check if DB is utf8 when creating tables, enforce collations and check them on upgrade.
comment:8 by , 14 years ago
There's definitely something wrong with collation and indexes. You have two files that only differ in case:
trunk/plugins/newarc.ex/Framework/Include/FarLNG.hpp trunk/plugins/newarc.ex/Framework/Include/FarLng.hpp
This seems to be resulting in the same primary key. Did you change the collation at some point? Is it necessary to rebuild all the indexes after that? Or do you maybe have a different collation on the node_change table?
comment:9 by , 14 years ago
| Keywords: | mysql added |
|---|---|
| Resolution: | → fixed |
| Status: | reopened → closed |
My own instructions on collation conversion were not sufficient - see MySqlDb. This changes DEFAULT collation for table, but column collation stays the same. I've updated MySqlDb#Conversion section.
Now this page contains sufficient information to automate MySqlDb troubleshooting and reduce administration narratives.
Well, the following error:
sounds like the typical ill-configured MySQL db…