#11173 closed defect (worksforme)
Trac does not sync all svn changesets
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | version control/changeset view | Version: | 1.0 |
| Severity: | normal | Keywords: | svn, sync, postgresql, needinfo |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
This seems to have just stopped working all of a sudden for no reason. Trac only reports 857 of 2980 changeset in an SVN repository. I verified all SVN changesets with svnadmin - no issues. I ran trac-admin repository resync several times but it stops at 857 with no errors reported. No error in Trac log file. Restarted Apache to no avail. This was working just fine but it just stopped working. We have several repositories pointing to this one Trac instance. The one I'm having an issue with is the default repository. Using Trac 1.0. with Apache (WSGI, SSL) on a PostGreSQL db.
Attachments (0)
Change History (10)
comment:1 by , 12 years ago
| Keywords: | svn sync postgresql added |
|---|
comment:2 by , 12 years ago
| Keywords: | needinfo added |
|---|---|
| Milestone: | → unscheduled |
comment:3 by , 12 years ago
And what about tracadmin sync (not resync), which is supposed to resume synchronization where it left?
Running the Sync command vice Resync has the same effect - it simply stop at changeset 857.
Anything special with r857? Can you show us the content of that revision, and the revision and changeset tables like it was done in ticket:5932#comment:25.
The chaneset consist of only 1 modified file, a Simulink model file that is just an XML file. At first I thought the issue might be with an improperly Trac reference in the SVN log message. However, I edited the message and re-ran sync and re-sync and the issue persists.
Also, the mention of PostgreSQL makes me think about #4043, #9979… (and see also ticket:8067#comment:10).
I'm not getting the errors referenced in these tickets. I get no errors at all either in the command window or the Trac log file. The sync and resync operation simply stops at changeset 857 where there are over 2000 changesets in the repository.
comment:4 by , 12 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I have solved this issue. This was indeed an issue with PostGreSQL. I executed an VACCUME operation on the Trac database and re-ran trac-admin sync. Issue solved.
comment:5 by , 12 years ago
| Resolution: | fixed → worksforme |
|---|
comment:6 by , 12 years ago
Ah ha, "Database is full" error ;-)
And nothing informative did show up in the Trac log?
Anyway, thanks for letting us know.
comment:7 by , 12 years ago
Aparrently this is a particular issue with PostgreSQL, something having to do with "dead tupples". Running the vacuum operation fixes the issue. I have the "auto vacuum" batch process enabled but I read some post concerning issues with auto vacuum working correctly. No errors are reported in trac.log. Here's a link for future reference:
comment:8 by , 12 years ago
| Summary: | Trac does not report all SVN Chanesets → Trac does not sync all svn changesets |
|---|
comment:9 by , 12 years ago
| Milestone: | unscheduled |
|---|
comment:10 by , 10 years ago
| Keywords: | svn sync postgresql needinfo → svn, sync, postgresql, needinfo |
|---|
And what about
tracadmin sync(notresync), which is supposed to resume synchronization where it left?Anything special with
r857? Can you show us the content of that revision, and the revision and changeset tables like it was done in ticket:5932#comment:25.Also, the mention of PostgreSQL makes me think about #4043, #9979… (and see also ticket:8067#comment:10).