I have an old system that is EOL. I want to use the scrips from Sangoma to move to an entirely new machine running the current version and I see there is a tool to do that. However the tool requires the System Admin module to run on both machines and I can’t get it running on the old one.
I read some threads of other people who couldn’t get System Admin to run and it sounds like FOP2 might be stopping it from working. I tried to remove FOP2 by removing the /var/www/html/admin/modules/fop2admin directory as instructed in those old threads but I was still not able to get the System Admin to install.
I ran the yum update sysadmin from the root which returns a “No packages marked for Update” message and the System Admin still doesn’t install. What do I try next?
The old machine is FreePBX 220.127.116.11 with Asterisk 18.104.22.168
The instructions are for registering both “Brand-new installation” and “existing installation” and instructions are for both version 12.0.19 or newer as well as a set for 12.0.18 or older.
If you ONLY had to run System Admin on the new machine, which would be the current Distro, why would they provide instructions for how to activate the license on the old machine? The instructions on the first page start under the How it Works section by saying you NEED to install a fresh FreePBX Distro 10.13.66 machine. So if that’s the first requirement, there would be no need to talk about 12.0.18 machines or order UNLESS they both have to be activated.
Any suggestions for why the script doesn’t do anything when I run it on the donor machine then? Does this machine need to be outside of my network for the script to run? Currently my Donor is inside my router and the new machine is in the DMZ.
It’s the certificate on the FreePBX side.
curl: (60) SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
More details here: http://curl.haxx.se/docs/sslcerts.html
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). The default
bundle is named curl-ca-bundle.crt; you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
I ran it again with the -k option and it appears to be doing something. I don’t know how long it takes to run so I’ll just leave it alone for several minutes.
Creating encrypted backup for new machine. This may take some time.
Backing up the following:
The script completed, sort of. The new machine wasn’t able to read the file from the old machine so it’s asking me to copy the encrypted file from the old machine to the new one.
The doner machine has a report showing it’s results. While it appear it did copy a few of the items it skipped more than it copied. For example the Module conferences skipped 21, completed 4. It reads that way down the list. It skipped most, completed a few. Given how many it skipped I’m not sure how much value there was in the script as it will still require manual entry of 80% of the module entries.
Earlier it was mentioned that there was an alpha script that might do a better job. How does a person go about getting this alpha script?