Ticket #2973 (closed bug: fixed)
IntegrityError: (1062, "Duplicate entry 'usd2-1-timeline.daysba' for key 1")
| Reported by: | usd2 | Owned by: | |
|---|---|---|---|
| Priority: | critical | Milestone: | 1.8.3 |
| Component: | [meta] ui.site | Version: | |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
Description
How to Reproduce
While doing a GET operation on /timeline, Trac issued an internal error.
(please provide additional details here)
Request parameters:
{'changeset': u'on',
'daysback': u'30',
'from': u'06/08/2008',
'update': u'Update'}
System Information
| Trac | 0.11rc1 |
| Python | 2.4.4 (#2, Apr 26 2007, 00:02:45) [GCC 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)] |
| setuptools | 0.6c8 |
| MySQL | server: "5.0.51a-3-log", client: "5.0.51a", thread-safe: 1 |
| MySQLdb | 1.2.2 |
| Genshi | 0.4.4 |
| Pygments | 0.9 |
| Subversion | 1.4.4 (r25188) |
Python Traceback
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/Trac-0.11rc1-py2.4.egg/trac/web/main.py", line 417, in _dispatch_request
dispatcher.dispatch(req)
File "/usr/lib/python2.4/site-packages/Trac-0.11rc1-py2.4.egg/trac/web/main.py", line 222, in dispatch
req.session.save()
File "/usr/lib/python2.4/site-packages/Trac-0.11rc1-py2.4.egg/trac/web/session.py", line 93, in save
"VALUES(%s,%s,%s,%s)", attrs)
File "/usr/lib/python2.4/site-packages/Trac-0.11rc1-py2.4.egg/trac/db/util.py", line 57, in executemany
return self.cursor.executemany(sql_escape_percent(sql), args)
File "/usr/lib/python2.4/site-packages/Trac-0.11rc1-py2.4.egg/trac/db/util.py", line 57, in executemany
return self.cursor.executemany(sql_escape_percent(sql), args)
File "/var/lib/python-support/python2.4/MySQLdb/cursors.py", line 218, in executemany
r = self._query('\n'.join([query[:p], ',\n'.join(q), query[e:]]))
File "/var/lib/python-support/python2.4/MySQLdb/cursors.py", line 312, in _query
rowcount = self._do_query(q)
File "/var/lib/python-support/python2.4/MySQLdb/cursors.py", line 276, in _do_query
db.query(q)
IntegrityError: (1062, "Duplicate entry 'usd2-1-timeline.daysba' for key 1")
Change History
comment:1 Changed 5 years ago by paul
- Owner changed from paul to eduardo
- Status changed from new to assigned
comment:3 Changed 5 years ago by eduardo
- Status changed from assigned to closed
- Resolution set to fixed
comment:4 Changed 4 years ago by rdworth
- Priority changed from major to critical
- Resolution fixed deleted
- Status changed from closed to reopened
- Component changed from [meta] ui.themeroller to [meta] ui.site
- Milestone changed from 1.5 to 1.6
This error is reproduced by not being logged in. Should not be closed fix until you can run reports and timeline without being logged in to Trac.
comment:5 Changed 4 years ago by rdworth
- Owner eduardo deleted
- Status changed from reopened to assigned
comment:7 Changed 4 years ago by joern.zaefferer
Created a ticket on Trac's tracker: http://trac.edgewall.org/ticket/8279
comment:8 Changed 4 years ago by joern.zaefferer
They suggest to fix the MySQL bindings (to get thread-safe: 1) or switching to InnoDB tables (we are using MyISAM), ala http://www.linux.com/feature/46370
comment:10 Changed 3 years ago by rdworth
- Status changed from assigned to closed
- Resolution set to fixed
Upgraded to latest stable Trac 0.11.7. Seems to have fixed this issue, finally.
Note: See
TracTickets for help on using
tickets.

