We've got serious problems with our OTRS database and I'm desperate for some help.
Here's a bit of version information to start:
OTRS: version 3.2.9
OS: CentOS release 6.5
MySQL: version 5.1.73 - using a MyISAM DB (yes, we should have switched to InnoDB but here we are
)Perl: version 5.10.1
I'm trying to work out what happened to our OTRS system and to fix it, I'll try to give as much information as possible but some of the logs from when it first happened may have been lost now. The problems started after a power outage took our OTRS server down in May, after the server came back up, the database was corrupted. Unfortunately OTRS was restarted and users logged in, updated tickets and the system processed the backlog of automated emails & tickets which by the time we noticed the problem meant that a restore from nightly backup would have lost too much data.
To fix the DB I tried doing a normal myisamchk -f -r on all the otrs database tables, this picked up some errors and repaired them but the database was still acting very strangely and OTRS wasn't working properly. To try to get around that problem I did a myisamchk -e -r -f *.MYI which still didn't fix the errors and may have caused more problems than it fixed.
Our users have been seeing this error most of them time since the outage:
Though it does go away for short periods sometimes, I'll be able to explain better after uploading some of the logs.
I'm investigating this issue on our test server, so I can experiment, I had originally thought the problem was fixed by deleting a single ticket row from the database, I tired it on the test system but the problem came back again soon after. Our users are now getting to their wits end, I had hoped to get the issue resolved by now, we'd arranged downtime for our production server this afternoon to fix the problem but I doubt it's going to be that easy or quick to fix.
I tried attaching a copy of the log file with errors but no matter what I change the filename to, the messageboard tells me that the file extension is is not allowed
can you tell me how to attach the log please?