Incredible PBX hangs on install (pic)

[briankelly63]

I had started this issue in someone else's thread so with more information I thought it best to create its own.

Included is a picture of where the Incrediblepbx install ends up after leaving overnight. I've started from scratch a number of times over the last couple of days.

I'm installing incrediblepbx18b.x also tried 18.x. This is after a fresh iso cd install of centos & purple that I had just downloaded a couple of days ago.

The only questionable section of the log is the following PARTIAL list of warning messages in the Asterisk log:

[Jan 10 23:23:36] VERBOSE[25373] pbx.c: -- Time to delete the old dialplan: 0.000189 sec
[Jan 10 23:23:36] VERBOSE[25373] pbx.c: -- Total time merge_contexts_delete: 0.002328 sec
[Jan 10 23:23:36] WARNING[25373] pbx.c: Context 'default' tries to include nonexistent context 'ext-local'
[Jan 10 23:23:36] WARNING[25373] pbx.c: Context 'from-internal-xfer' tries to include nonexistent context 'from-internal-custom'
[Jan 10 23:23:36] WARNING[25373] pbx.c: Context 'from-did-direct' tries to include nonexistent context 'ext-findmefollow'
[Jan 10 23:23:36] WARNING[25373] pbx.c: Context 'from-pstn' tries to include nonexistent context 'from-pstn-custom'
[Jan 10 23:23:36] WARNING[25373] pbx.c: Context 'from-internal-additional' tries to include nonexistent context 'from-internal-additional-custom'
[Jan 10 23:23:36] WARNING[25373] pbx.c: Context 'macro-dial-one' tries to include nonexistent context 'macro-dial-one-custom'
[Jan 10 23:23:36] WARNING[25373] pbx.c: Context 'macro-hangupcall' tries to include nonexistent context 'macro-hangupcall-custom'
[Jan 10 23:23:36] WARNING[25373] pbx.c: Context 'macro-simple-dial' tries to include nonexistent context 'macro-simple-dial-custom'
[Jan 10 23:23:36] WARNING[25373] pbx.c: Context 'macro-exten-vm' tries to include nonexistent context 'macro-exten-vm-custom'

The picture of where things end in the install process is pictured in the attached pdf file. A ctrl-c is then required to get a prompt. The last line (INIT) takes a very log time to appear.

In the status screen "Running Asterisk Version" indicates LOADING

Any combination of amportal start stop restart command leaves you with the same status.

Doing a shutdown -r will allow things to come back up and then the LOADING is replaced by the version number as usual 1.8.1.1

Things function but I'm concerned about what didn't complete properly in the install and I have not been able to get gvoice to work...

Brian

 

[briankelly63]

Conducting further testing to confirm... may be UTC clock setting causing failure of Incrd PBX to complete properly.. Will update.

Still getting seg fault from asterisk on gvoice dialout.

 

[briankelly63]

nope wasn't clock.. may be existence or non-existence of analog card...

 

[blanchae]

Context 'macro-exten-vm' tries to include nonexistent context 'macro-exten-vm-custom'

This is normal error reporting. It just means that the context doesn't exist. Hasn't been used or configured yet.

 

[wardmundy]

Brian: I'm installing incrediblepbx18b.x also tried 18.x. This is after a fresh iso cd install of centos & purple that I had just downloaded a couple of days ago.

No reason to ever use incrediblepbx18b.x. It is NOT current. incrediblepbx18.x has all the patches. That may be your problem. Just loaded incrediblepbx18.x on new PIAF-Purple build with Aspire Revo (no cards) and had no issues.

 

[briankelly63]

will go back and try 18.x One of the threads gave me the impression that the 18b.x was later and included fixes.

 

[briankelly63]

I have discovered that the Incrd PBX install will complete if I have my AEX800 Digium card installed. Without it the install process will hang as described every time.

SEE THE ATTACHED for error messages within the GUI that require a shutdown reboot to resolve otherwise you can't do a relad in Asterisk even after a "successful" install of Incrd Pbx.

GV will still not function and generates a SEG Fault in Asterisk everytime after I finish dialing..

Did create new GV account, configs are proper and 5222 is mapped.

Brian

 

[wardmundy]

Let me preface this by saying that whenever I see a screenshot that reveals we're dealing with eMachines hardware, all bets are off. These systems are not compatible with the rest of the industry, period!

Judging by where your last message appears in the script, what follows is a series of MySQL updates to populate random passwords in the FreePBX database tables. To do that, we use the PHP randomizer which I suspect is causing the problem because of some incompatibility in the eMachines processor or motherboard. This probably returns a divide by zero condition which blows up your machine. No idea why inserting a card in the machine makes the problem go away. But at least you can get it working. We install dozens of these in systems with no cards every week and never experience this. But we don't use eMachines!

The next section of code populates the new registry, but it doesn't appear that you ever get that far. Sorry.

 

[briankelly63]

Generally I share your feelings on the emachines, especially the low end power supplies but I have never had an issue with this particular model no matter what distro I installed. Also the purple version of PIAF does work just fine on it its just the Incrd Pbx (this version) that runs into this issue... Asus has been improving on these machines, sometimes I'm able to chose hardware based on the motherboard. In this case its a decent one with an Intel E2210 Pentium Proc.

I have 1.4 and Incred PBX + Aastra scripts running on the exact same emachine.

After the extra steps everything about Incrd PBX seems to have been installed and works except the GV stuff...

They do have a slightly different bios available for Linux... I may try that... Also they have been taken over by Acer...

I'll try a later revision further down the road and see if that installs a little more smoothly on this machine.

Thanks for the reply.

Brian