You guys do an amazing job!
We used the script last night on our VPS instance and everything upgraded without a problem. According to the admin interface, we are running “Asterisk (Ver. 12.4.0)” and FreePBX “6.12.65-13” now.
I have a couple observations that may be of help to you. There is also a minor nuisance where you may be able to point me in the right direction.
The first observation might fall into the category of “user error” or “not supported”. The upgrade script was stored in a folder that had some white spaces in the path (our environment is “white space tolerant”). The script had a few error messages such as a “cd” to the folder of the script failed probably due to unquoted variables:
/var/lib/asterisk/bin/freepbx_engine: line 97: cd /PATH/INLY/TO/FIRST/WHITE/SPACE : No such file or directory
The script eventually ended after downloading a lot of items with these lines:
Module framework successfully downloaded
Module framework successfully installed
An error has occurred updating to FreePBX 12
The second observation is, that the script did not prevent us from trying to upgrade from 5.211.65-9. It detected the version, indicated it was not sufficient, yet still continued:
Check to make sure this is a FreePBX Distro system before executing
This appears to be a FreePBX Distro system as it has a Distro Version of 5.211.65-9
Make sure this is version 5.211.65-14 or greater before executing
This appears to be FreePBX Distro version 188.8.131.52 so we can now upgrade you to the 6.12.65 track as version 6.12.65-13
So we went into the admin interface, upgraded to 5.21.65-15, and reran the script with no errors.
Somewhere along the upgrade path from 5.211.65-9 … 5.211.65-15 … 6.12.65-13, the Superfecta image files mentioned in other posts got screwed up. They became symbolic links to themselves (such as /var/www/html/admin/assets/superfecta/images/bottom.gif --> /var/www/html/admin/assets/superfecta/images/bottom.gif) and the script had warnings such as
find: `/var/www/html/admin/assets/superfecta/images/bottom.gif': Too many levels of symbolic links
We simple removed the symbolic links and retrieved the image files from backup and everything is fine.
Now to the minor nuisance. Crontab has an entry to execute “/usr/sbin/sysadmin_update_system -a” once every minute. I am not sure whether that was there before the update or not. In any case, the program prints to stdout which leads cron to send us an email every minute now with the program output:
[status] => error
[data] => SimpleXMLElement Object
 => This system is up to date.
Should this system check really run every minute?
Is there anything we can do to make the program print info only in cases that need our attention? What I mean is the program should not print anything in the normal case.
The output is a little ambiguous. It both indicates an error, and it says the system is up to date. Anything we should do about that?
Thanks again for an amazing product!