Just a heads-up that I (inadvertently) upgraded last night, and it broke my web services. So rolled back (schnapps rocks!) and will diagnose as time permits. The problem is usually that I have a highly configured lighttpd reverse proxy configuration that the upgrade breaks, and so diffing those configs generally sorts me out. But the updater was not comforting with a load of worrying output like:
Command failed: Not found
(without a reference to what command though appearing after “INFO: Running”)
I will try and extract all the INFO/fail pairs from my log (I took a copy from the console though wonder if there’s one on disk?)
I would not be surprised if these are so widespread because of a domino effect. One premise early broken and so a lot of downstream failures. We shall see.