Fixed: pass-wd-master BUG

[wolfeman]

I did a new install today (twice) with version 1.7.5.5 downloaded this morning using the Silver install.

After doing the update-scripts, then update-fixes I rebooted for good measure and Asterisk started up fine.

Then I did a passwd-master and rebooted. Asterisk failed to start at boot. However I could do a manual #asterisk and get it to start up fine.

#amportal throws the following 2 errors:
/var/lib/asterisk/bin/freepbx_engine: line 40: [: =: unary operator expected
**** WARNING: ERROR IN CONFIGURATION ****
astrundir in '/etc/asterisk' is set to but the directory
does not exists. Attempting to create it with: 'mkdir -p '
mkdir: missing operand

Try `mkdir --help' for more information.
**** ERROR: COULD NOT CREATE ****
Attempt to execute 'mkdir -p ' failed with an exit code of 1
You must create this directory and the try again.

 

[blanchae]

The correct way to start asterisk is "amportal start"

 

[wolfeman]

This command also produces the same error.

[update]
I do see that the /etc/amportal.conf is there but empty (size zero)

 

[lopaka]

I've had the same issue on my last few loads. I documented some of them in the "FOP panel error" thread, and the problems seemed to start after running the passwd-master. I had the same error running asterisk with the amportal start command, but can still start asterisk through webmin.

If you start asterisk through webmin interface, you'll get the FOP error I was describing.

I don't know how to fix it, but can say I've seen it. I ended up putting FOP2 on the box and it does run fine, although I start and stop asterisk through webmin since the command line "amportal stop / start" no longer works

lopaka

 

[wardmundy]

If someone would record your setup process showing this error, it would help us a lot.

 

[gaijin]

I just had this issue with 1.7.5.5
Installed a fresh 1.7.5.5 GOLD
when running passwd-master or update-fixes (not sure which one) it wiped out my amportal.conf file and replaced it with JUST the ARI stuff:

ARI_ADMIN_USERNAME=admin
ARI_ADMIN_PASSWORD=?????????


The file had two lines in it...

To fix I just copied & pasted from a backup (it was a forklift upgrade)
Rebooted the box and all fixed

Tom, it appears that for some reason one of the scripts replaced rather than appended to the amportal.conf

 

[wardmundy]

> instead of >> perhaps. Thanks.

 

[wardmundy]

Tom is out diving today so here's a copy of the file to get you back in business. Copy the tarball to your /etc folder and then tar zxvf amportal.tar.gz. Edit the file and change the ARI_ADMIN_PASSWORD (last line in file) to something really secure. Save file and then amportal restart.

 

[darmock]

very arcane sed bug was found. I have updated everything and it is being propagated into PIAF space. Ward will post when it is completed. then use update-scripts to get the latest version

Tom

 

[wardmundy]

All set. Be sure to restore your amportal.conf file above if you had a problem. Then...

update-scripts
passwd-master

 

[gaijin]

In case others are affected by this...

It may be unrelated, but I found I also had to delete and recreate the extensions. The hint status was "unavailable" and the extensions could not receive calls.