PIONEERS Rocky Roadmap & Bug Fixes

[kenn10]

Rocky 8 is a mess. Don't waste your time.

 

[wardmundy]

Rocky 8 is a mess. Don't waste your time.

Amen. I wrestled with it most of the day... still a mess. Problem is there are loads of mismatched components because FreePBX uses a bunch of deprecated node components for openers.

 

[wardmundy]

Pretty clear now that we will probably never have a smooth, direct transition to Asterisk 20 and FreePBX 16 with Rocky 8. But, having said that, the original release of Incredible PBX 2027 for Rocky 8 still works fine even though it's a two-step process. First, you install Asterisk 20 with FreePBX 15. Then, you run another script to upgrade FreePBX 15 to 16. Just tested again on Vultr, and it still works fine even though there are a couple disabled modules that need to be updated when you're finished. Those upgrades also work just fine using Module Admin. TEDIOUS is probably the best description, but if you're a diehard RedHat/CentOS/Rocky addict, the original Incredible PBX 2027 tutorial for Rocky 8 will get you there.

So why does the one-step work with Debian and Ubuntu and fails miserably with Rocky 8? The short answer is that the RedHat repos apparently have components that are extremely sensitive to perfectly matched versions of PHP and other RedHat components, and the install process goes through a number of iterations that don't appear to use the correct versions of PHP. With the two-step process, we use PHP 5.6 to get to a stable FreePBX 15 deployment. And then we use PHP 7.4 to get to a mostly stable version of FreePBX 16. That's the best answer I can muster as a mere mortal.

 

[redstonemason]

Nice to see that you have the stick-to-it-ive-ness on this one.
Maybe I shoudl spin up a really high power instance on Vultr so that I can watch closer with the expectations that I can catch something in the first 5 to 10 minutes. I will follow Orignal Tutorial for Rocky 8

 

[wardmundy]

Nice to see that you have the stick-to-it-ive-ness on this one.
Maybe I shoudl spin up a really high power instance on Vultr so that I can watch closer with the expectations that I can catch something in the first 5 to 10 minutes. I will follow Orignal Tutorial for Rocky 8

Should you wish to play with the Rocky 8 one-step installer (which blows up spectacularly), here's a link:

wget http://incrediblepbx.com/IncrediblePBX2027-R.sh

 

[redstonemason]

No harm in a little bit of what we used to call UAT (user acceptance testing)

 

[wardmundy]

No harm in a little bit of what we used to call UAT (user acceptance testing)

Vultr TIP: The one-step is worth wasting 5¢ on, but no more.

 

[redstonemason]

Yup. Blows up real good. If I had to guess, it goes into the weeds with NodeJS/NPM related stuff. But I will cut my costs now. Maye Almalinux next

 

[krzykat]

I've been using Rocky8 with Asterisk 20 in production on several machines now without issue. I do know that I once encountered an issue that was from some automated updates that I had to disable. Since that made it work, I didn't really have time to dig into it any further.

 

[wardmundy]

@krzykat: So now you have a Spring Break project to see where our installer goes off the rails. HINT: It does appear to have something to do with deprecated Node.js and NPM code. And, yes, we can get things working reliably by first installing FreePBX 15.

 

[krzykat]

Yes sir, I'll fit that in after I get this properly deployed ... almost there. Going to reserve some of the resources for some PIAF items including a Git server. Check out that RAM - woo woo

 

[wardmundy]

I think we've narrowed this down to the later versions of UCP which also reload npm which promptly blows up.

 

[redstonemason]

Spring Break. PBX gone wild !

 

[hecatae]

anyone using Rocky 8.10 with this?