Upgraded/Migrated FusionPBX to new server

Status
Not open for further replies.

dlasecki

New Member
Jun 27, 2023
4
1
3
34
Trumbull, CT
www.sjcadets.org
Hello All,

Background:
We had an instance of Debian 8 running FusionPBX 4.4.1. I was able to upgrade that instance on Debian 8 to 5.1.0 RC1 from the 4.4.1. As I was not happy with the fact of being on Debian 8 as it was severely out of date (inherited when I started the job), I was able to create a new VM using Debian 11 (up-to-date).

I ran the fusionPBX install, changed the DB password in the config.php install section to match the current DB, and proceeded on the fresh install fresh version of FusionPBX.

I used the Backup / Restore scripts from the documentation to move the Debian 8 system to the Debian 11. After copying a couple of config files for fail2ban and a couple of other settings syncing, I was able to get it up and running. However, now I'm running into a couple of problems that I am trying to diagnose, and it's probably staring me in the face with all the searches I've done, but I think I'm hitting the tunnel vision part of trying to diagnose.

Problem(s):

  1. I think this has to do with the /etc/fusionpbx/config.conf file after migration. I believe this has to do with the Memcached vs cache method being file now(?). As I am having an issue with the following in the logs:
    1. Code:
      2023-07-05 11:51:30.693191 96.93% [ERR] mod_memcache.c:425 Error while running command get: CONNECTION FAILURE
      2023-07-05 11:51:30.753192 96.93% [ERR] mod_memcache.c:425 Error while running command set: CONNECTION FAILURE
      2023-07-05 11:51:33.833195 96.93% [WARNING] sofia_reg.c:1846 SIP auth challenge (INVITE) on sofia profile 'internal' for [352@x.x.x.x] from ip x.x.x.61
      2023-07-05 11:51:33.833195 96.93% [WARNING] sofia_reg.c:1846 SIP auth challenge (INVITE) on sofia profile 'internal' for [308@x.x.x.x] from ip x.x.x.61
      2023-07-05 11:51:33.833195 96.93% [WARNING] sofia_reg.c:1846 SIP auth challenge (INVITE) on sofia profile 'internal' for [305@x.x.x.x] from ip x.x.x.61
      2023-07-05 11:51:33.833195 96.93% [WARNING] sofia_reg.c:1846 SIP auth challenge (INVITE) on sofia profile 'internal' for [605@x.x.x.x] from ip x.x.x.61
      2023-07-05 11:51:33.833195 96.93% [WARNING] sofia_reg.c:1846 SIP auth challenge (INVITE) on sofia profile 'internal' for [325@x.x.x.x] from ip x.x.x.61
      2023-07-05 11:51:33.893190 96.93% [ERR] mod_memcache.c:425 Error while running command get: CONNECTION FAILURE
      2023-07-05 11:51:33.933190 96.93% [ERR] mod_memcache.c:425 Error while running command set: CONNECTION FAILURE
      2023-07-05 11:51:33.993190 96.93% [ERR] mod_memcache.c:425 Error while running command get: CONNECTION FAILURE
      2023-07-05 11:51:34.033189 96.93% [ERR] mod_memcache.c:425 Error while running command set: CONNECTION FAILURE
  2. I think this is tied to the first issue above, as you can see that the same IP is trying to register on multiple extensions though the phones all have different IP addresses being assigned via DHCP (sterilized IP above, but ext@x.x.x.x is our internal IP of the system, and x.x.x.61 is the same IP as well as others coming across).

  3. This is minor, but since doing the new version, I keep getting a Postgres backup in /var/backups/postgress every morning. I don't see anything in crontab, cron.daily and during install I did not set the backup database to true (though that may have nothing to do with the daily), so I'm not quite sure why I am getting a daily backup of the database at around 625am every morning since updating. This may just be because of the updated version and I might have missed that somewhere in the threads.

Any advice or suggestions, I am open to them. Appreciate your time reading and responding!
 

s2svoip

Member
Dec 9, 2019
234
7
18
44
my process to update is to spin up a new server as you have done, but also run the update at least twice to update your db schema, you just overwrote your new install with the old db

cd /var/www/fusionpbx
php /var/www/fusionpbx/core/upgrade/upgrade.php

and once your into the GUI, also run updates Steps 2+2B thru 5

I found this cleared up some weirdness which was to be expected
 

dlasecki

New Member
Jun 27, 2023
4
1
3
34
Trumbull, CT
www.sjcadets.org
I wound up finding the issue. config.conf and config.lua which synced over was causing an issue. I was able to remove that .lua folder after double-checking the config.conf file had all the correct information. I had to go and update the default settings, which were still pointing to location as /tmp and method as memcache to location /var/cache/fusionpbx and method file.

Clearing the cache buttons and flushing now works correctly. Was able to reboot all the phones via switch PoE, and everything seems to be working.
 
Status
Not open for further replies.