Service Temporarily Unavailable after Upgrade

MarkDale

Hello,
I am attempting to upgrade from v1.7.0 to 1.12.2
I have created a duplicate of the live site on a test server.
The first time I ran the upgrade it appeared to run successfully - but I could not see any open tickets.
I decided to roll back and attempt the upgrade again, so I restored the database and the helpdesk directory and now version 1.7.0 is loading correctly.
However, whenever I copy the files from upload over the top of the helpdesk directory I get a 503 Service Temporarily Unavailable message.
In the apache logs it just says 503 and then
(104)Connection reset by peer: AH01075: Error dispatching request to

Any help would be much appreciated!

Thanks

ntozier

If you couldn't see any tickets, its likely that your Agent account didn't have access to the departments that the tickets were in. You would need to take a look at your [unknown] webserver logs to see why a 503 error is being thrown. You would also want to look at your PHP error logs to see if anything is being logged.

MarkDale

Thanks ntozier

Apache log says
86.174.45.127 - - [08/Aug/2019:21:56:45 +0100] "GET /helpdesk_new/scp/ HTTP/1.0" 503 2833 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/75.0.3770.142 Safari/537.36"

PHP log says
[Thu Aug 08 21:56:48.210669 2019] [proxy_fcgi:error] [pid 2587:tid 140016479164160] (104)Connection reset by peer: [client 86.174.45.127:42554] AH01075: Error dispatching request to:

What's odd is that the site worked using the latest front end files until I restored the database back to the source.

Can you think of anything that might cause this behaviour?

Thanks

MarkDale

I have since done a fresh installation of version 1.12.2 under a new site - all went well.
I then tried pointing this installation at the old database by editing the ost-config.php file - which I assume should have kicked off the upgrade process.
Same result - Service Temporarily Unavailable
So it appears to be something to do with the database - is there anything I have to do to the database for the upgrade to work?
Thanks

MarkDale

Finally resolved this by first upgrading to 1.10.7 and then to 1.12.2
For any others in the same boat - the first time I downloaded the 1.10.7 package the upgrade started but failed. But was able to diagnose issue by looking in the syslog table in the DB - tried to delete the cannedresponse_attachment table but it didn't exist.
So went and downloaded the installer without the attachments plug-in, restored back to 1.7.0 and re-ran the upgrade.
Then ran the upgrade to 1.12.2 (no attachments) - and all is now well.
Gah

ntozier

Glad that you got this sorted. Should I mark this as resolved and close the thread?