Now should I pass ‘asterisk-version-switch’ before or after the reboot if I want Asterisk 12 too (says any time).
Update1: Well I tried it before reboot, in the spirit of beta testing.
Update2: things seem to be working well, apart from the 42 unsigned modules (which seems to be a lot more than anyone else has reported in this thread).
It doesn’t appear to be cached, refreshing doesn’t fix. It looks like the version numbers of the 42 unsigned modules are older (2.11) branch… maybe the script could be modified to FORCE update of all modules?
I wonder if this happened because I ran the script that had the extra ’ in it? The new one you provided completes without error, but it obviously didn’t update some modules.
Mmmm… only for test purpose I reverted to 5.211.65-14. Then I upgraded to 5.211.65-15 through web gui.
This time the upgrade script to 6.12.65 hangs in this manner:
Yes, I did after I saw so many unsigned modules. When I get a chance I may roll back to 5.211.65-13 and try the upgrade from there. Thanks for doing your testing.
mmmm… Tony,
now I reverted to 5.211.65-14, but the new upgrade script to 6.12 stops in the same way.
As you can see in the past posts I used your old upgrade script with success from 5.211.65-14 to 6.12
Moreover, I have a copy of your old script dated 9 july 2014 and if I run this old script I can go on 6.12 without any issues
I believe you, but I took the same test right now and I get the same result:
From 5.211.65-14 + new upgrade script = An error has occurred updating to FreePBX 12
from 5.211.65-15 + new upgrade script = An error has occurred updating to FreePBX 12
From 5.211.65-9/13 + old upgrade script(7/9/14) = Upgrade OK(but only if I previusly uninstall userman&xmpp)
From 5.211.65-14 + old upgrade script(7/9/14) = Upgrade Ok(userman was up to date in snapshot)
from 5.211.65-15 + old upgrade script(7/9/14) = Upgrade Ok(userman was up to date in snapshot)
It’s not a big deal for me, because I can upgrade easly, but I think it’s best to signaling you this behaviour.
PS: after the error I receive this mail:
SECURITY NOTICE: There is 1 module vulnerable to security threats framework (Cur v. 2.11.0.38) should be upgraded to v. 12.0.1alpha22 to fix security issues: SEC-2014-001, SEC-2012-001
If I uninstall each module and then reinstall, it doesn’t fix the issue.
If I uninstall, remove, re-download and install it takes each module out of the unsigned list.
Sounds like the script may force reinstall on the modules, but if the user has a locally stored installer package it skips downloading them over and this is where the unsigned module part comes into play.
Is there a way to whack all my locally stored installer packages, re-run the script, and have it force update these modules? I REALLY don’t want to have to uninstall, remove, reinstall 40 times.
will delete all of the modules, then re-install them… most of your data will survive, but some modules and settings will be wiped by the removal of all modules, and require re-entry.
Deleteall & installall got me down to 20 or so unsigned modules, I ran refreshsignatures again and it somehow broke the webgui, amportal restart didn’t fix.
Finally, I ran the upgrade script again (thinking wth not) and noticed it took a lot longer this time and now everything is happy after reboot. Don’t know if all of these convoluted steps will help anyone, but it is what it is.
After all of the above I still had some weirdness where it said there was an update available for tts, so I uninstalled tts and ttsengine, removed them, and reinstalled them.
Now no unsigned modules or security warnings.
I do however have:
PJSIP Not Supported
Your SIP Channel Driver (ASTSIPDRIVER) was automatically changed from both to chan_sip because chan_pjsip is not supported on your Asterisk installation
Even thought I AM running Asterisk 12… Should I switch to 11 and then back to 12 since I had the other problems along the way?