Just moved the install to a different server. It works fine now.
Must of been some weird coincidence that what ever happened, happened while doing the update. That activity must have been the straw that broke the back. This server was for Blesta only, though I did have two light websites temporarily on this server. Certainly was not working hard, so who knows what happened. Some PHP files must have got corrupted
Years ago it was common for amazon aws instances to just go bad, nothing could be done, delete and start up new one. Netflix spent a lot of time trying to figure that one out, and never did, per their blog. Only solution was delete instance start new one. Even though a lot of people and companies like Netfix have experienced data corruption, amazon aws has never admitted that data corruption ever happened. I have not had a server failure that necessitated deleting and starting a new one in a couple of years. I suppose I was due.
Sucks when something happens and there are no logs to even point in what direction. Specially when it happens while doing an update, as it appears it is a problem with the update. Fortunately building a new server is a trivial matter. I would much rather rebuild a server than rebuild Blesta.
