Roundup Tracker - Issues

Issue 2550813

classification
files/msgs disassociated with database
Type: behavior Severity: normal
Components: Database, Web interface Versions:
process
Status: closed
:
: : ber, dpmills, rouilj
Priority: :

Created on 2013-06-19 15:35 by dpmills, last changed 2016-04-09 02:23 by rouilj.

Messages
msg4907 Author: [hidden] (dpmills) Date: 2013-06-19 15:35
After a machine crash, the web interface has seemingly reverted back to an earlier state (the 
newest available issues are 11 months old). I have found the files and the messages that 
should be associated with issues newer than that, but I don't know how to make the database 
look and find those new issues.

2 questions:
1) is this something that someone else has encountered?
2) (If so,) is there some sort of script that could be ran to make the database find the 
"missing" issues?

Thanks,
Daniel Mills
msg4908 Author: [hidden] (ber) Date: 2013-06-19 22:10
Hi Daniel,

a crash of the machine could have lead to a number of problems unrelated
to roundup, which may affect it, though.

Best would be to try a recent backup of the machine's disk with a consistent 
state. But I guess you would have done this, if you would have a usable backup.
So you are facing a harder problem. 
Best is to seek help on the user list, you could of course write a script to 
reconnect some of the data again to recover. 

I don't think this is a general roundup issue, it depends on the database backend 
used and on the type of the damage done. Roundup must make some 
assumptions about the consistency of its computing environment and cannot cope 
for general "crashes".

Best Regards,
Bernhard
msg4909 Author: [hidden] (dpmills) Date: 2013-06-20 17:52
Yeah, I restored the MySQL database from the last clean backup, so now it's only a few weeks 
before...so the bosses are happy (but I'm still intrigued).

If I have orphaned entries in /msg and /file, how can I plug those back in?
msg4910 Author: [hidden] (ber) Date: 2013-06-20 20:19
Depending on how much info you have lost you could write python scripts to recreate 
issues, just created them as new. Usually you'd need all the other information that is 
not kept in the msg and file files, so it depends on your tracker.

Without the extra information that would allow you  guess the rest and create 
complete new issues and attach the "file"s and "msg"s you are lost though.
Sometime mysql keeps some logs or your can recover something of the broken 
datebases (depends on the mysql table type I guess).
msg5501 Author: [hidden] (rouilj) Date: 2016-04-09 02:23
Closing as this seems to be abandoned.
History
Date User Action Args
2016-04-09 02:23:31rouiljsetstatus: new -> closed
nosy: + rouilj
messages: + msg5501
2013-06-20 20:19:58bersetmessages: + msg4910
2013-06-20 17:52:47dpmillssetmessages: + msg4909
2013-06-19 22:10:59bersetnosy: + ber
messages: + msg4908
2013-06-19 15:35:35dpmillscreate