is there a migration guide for moving a FreePBX installation to a new server? The documentation in the wiki http://wiki.freepbx.org/display/FPG/Using+the+Backup+module seems to suggest that it is as easy as klicking some buttons. But it is not.
First Asterisk was not starting after reboot. “chkconfig asterisk” showed off for all runlevels. So I enabled it.
Next I can’t access the CDR reports and UCP. I got this error Unable to connect to CDR Database using string:mysql:host=localhost;port=3306;dbname=asteriskcdrdb,freepbxuser,2c9d0b3530d0
The right password I found in /etc/freepbx.conf wich works with mysql on the command line. I replaced all occurrences of “2c9d0b3530d0” in all files in /etc/asterisk/ with the right one, but it still doesn’t work. Where else do I need to look?
Also, the Dashboard tells me that the “Phone Apps Daemon” and “UCP Daemon” are not running. Before I restored the backup from the old server everything was working as far as I can tell. I will look into that tomorrow.
I’m running FreePBX 10.13.66-11 with FreePBX Framework 13.0.115 on both servers.
The Backup & Restore module doesn’t really fills me with confidence. Who knows what else is not working…
Sometimes restoring a backup will populate the CDR database fields in Advanced settings, there is an open ticket on this but i can’t find it at the moment. Just delete all the contents of fields in the section Remote CDR Database.
Yes I have. The odd thing was that there was only a cdr_mysql.conf.bak, so I renamed it. Still no luck.
Now I searched the asterisk database for “2c9d0b3530d0” and found it in the freepbx_settings table in the CDRDBPASS row. As I couldn’t find this setting anywhere in the GUI I changed it directly in the database and this error is gone now.
Next problem was the UCP and Phone Apps Daemon. I disabled both modules since I don’t have a license anyway and the errors are gone. But they were running on the old system. I wonder whether there is another underlaying problem.
Finally, the System Firewall is not running. I got the notification “Firewall Integrity Failed: Interface eth0 is not in the correct zone. This can be caused by manual alterations of iptables, or, an unexpected error. Please restart the firewall service.”
Uninstalling and reinstalling the Firewall Module solved that problem.
I think there should be a note in the Backup & Restore Module or in the wiki, that the module only works without problems when restoring to the same machine and when restoring to a new machine ,then certain steps are necessary.
Spoke too soon. After a reboot I get the same error regarding eth0 not being in the correct zone and the firewall is not running. After disabling and re-enabling the firewall the error is gone and the firewall runs (until the next reboot).
What should be the correct zone for eth0 (if this is really the error)? It is the only interface on this machine and is set to “Trusted”. After I disabled and re-enabled the firewall, eth0 is automatically set to “Internal” and everything works. When I reboot it is back to “Trusted” and when I try to set the zone to “Internal”, I lock myself out, even though my PC and the whole network is set to “Trusted”.
The server is only accessible from the LAN which is behind a NAT router. Do I need this firewall at all if it’s not exposed to the Internet? And why did the same configuration work on the old machine?
Here is the output of “iptables -L” after a reboot
I have the same issue with the firewall. I disabled it and it stills says the trusted zone error. I dont need that firewall since my is behind my firewall in house and I dont have my box directly on the web.
I switched off the firewall since my FreePBX sits behind a NAT router. But I have similar problems with another FreePBX installation which I didn’t migrate. So the problem might lay elsewhere and not with the migration to a new server.
