After doing what looked like a successful trac-admin /path/to/trac/
project/ resync.

I "cd" to the project/db directory and find that there's still a
persistent trac-db-journal file sitting there. Am I suppose to let the
sync finish some other tasks? Or should this file not be there after
the resync has completed?

Note that this file is not static. It's constantly being updated every
second and changing size, and also changing the time stamp on the
trac.db sharing the same directory --  but does not change its size.

I've tried shutting down Trac's Apache and moving the file out. Then
restarting Trac, only to see the file pop back there again and start
updating itself.

Should I reboot the whole trac server? Or just move the original
trac.db back in place and then go from there?

Be aware that the reason i did the resync in the first place was just
to fix a "TypeError: expecting datetime, int, long, float, or None" on
just one of the custom query within a specific project.


-- 
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en.

Reply via email to