Problems after crash, update or not?

[chebert]

Dear all,
following a crash of the server hosting the virtual machine on which our OTRS is installed, we cannot restart it. (Please dont ask why we do not want to recover from a bakcup ...)

After cleaning all the caches, restarting apache and otrs, we always get the "too old browser error", and errors that apache cannot write in a certain directory.

We have made sure this directory *is* writable for the user runing apache, and loging under this user, one *can* write in this directory.

Is there any obvious thing that we missed ?

OTRS is under 3.2.11. We want anyway to update to 3.3.4. Now I see 3 options:

1) trying to reinstall OTRS 3.2.11 from the beginning, keeping the same database. Question: how to save and reuse the config files ? Then update

2) reinstall everything from scratch under 3.2.11, with an empty database, and reimport a dump of the database into mysql after install Then update.

3) clear everything, install OTRS 3.3.4 from scratch and then import the mysql dump (originating from 3.2.11)

Which option (if any...) is more likely to work ?

[crythias]

1) Seems legit. All things being relatively equal, you should be able to copy Kernel/Config.pm and Kernel/Config/* and below to the new system.
(Watch out that you'll want Database user and password changes to reflect the new install). Backup files before clobber

2) I thought this was 1) Oh, well, roughly the same.

3) not *horrible*, but you'll still need to run the UPGRADING procedure against your data.

Note that you should verify tables aren't crashed.