I’ve been using rt 1.0 successfully for many months, but recently I’ve had
some information go missing.
To give an example, I created a request on 17th Mar with serial number 199.
The web interface shows the request correctly, but with a blank transaction
history. The directory /usr/local/rt/transactions/2000/Mar/17 contains a
file named 199.868 which contains what I would have expected to see, but the
web interface isn’t showing it.
I’m not too familiar with the database structure of RT, but a look at the
transactions table appeared to show some sort of corruption…
Yipe. That’s not good. I’d suggest you “mysqldump rt” and see if you
see the corruption there. What rev of mysql are you running?
jesseOn Tue, Mar 21, 2000 at 04:18:31PM -0000, Paul Dixon wrote:
I’ve been using rt 1.0 successfully for many months, but recently I’ve had
some information go missing.
To give an example, I created a request on 17th Mar with serial number 199.
The web interface shows the request correctly, but with a blank transaction
history. The directory /usr/local/rt/transactions/2000/Mar/17 contains a
file named 199.868 which contains what I would have expected to see, but the
web interface isn’t showing it.
I’m not too familiar with the database structure of RT, but a look at the
transactions table appeared to show some sort of corruption…
jesse reed vincent – jrvincent@wesleyan.edu – jesse@fsck.com
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
Linux is like a Vorlon. It is incredibly powerful, gives terse,
cryptic answers and has a lot of things going on in the background.
Since you know the file is there, you might want to check the permissions on the
file. I had this happen ages ago with older versions of RT where the permissions
on the files weren’t being set properly. This is usually due to improper
permissions on the installation binaries.
If it is corrected when you fix the permissions (or if you do a chmod a+r
/usr/local/rt/transactions/2000/Mar/17/199.868), then you might want to go back to
your source tree, and run ‘make fixperms’ (I think that’s the right make option).
I’m not too familiar with the database structure of RT, but a look at the
transactions table appeared to show some sort of corruption…
Ouch … what version of mysql are you using? Maybe it’s time to check
out the mysql development. Both me and Jesse (running old versions of
mysql) have had some problems recently with mysql.
I think you should delete those extreme records.
Sometimes requests get “inaccessible” because they are merged.
mysql Ver 9.29 Distrib 3.22.19a, for pc-linux-gnu (i686)
I guess the newest is 3.23.9 or something like that. I guess I could take
a peek at some changelog and/or bug database to see if there is a list of
critical bugs that has been wiped out, and/or if people report bugs from
the more recent versions as well. Anyway, I’m too lazy (ehrm … “busy”
is a better word for that.
Hopefully someone else might be able to
for that.