Difference between revisions of "Talk:Raspberry Pi Script"

From FusionPBX
Jump to: navigation, search
m
Line 18: Line 18:
  
 
I'm running this on a BeagleBone Black, not on a RaspberryPi, but that shouldn't make the difference ;)
 
I'm running this on a BeagleBone Black, not on a RaspberryPi, but that shouldn't make the difference ;)
 +
 +
Script failing for me using a clean build of Raspbian with updates and upgrade applied an a multi-core Pi.
 +
 +
"Compiling FreeSWITCH. This might take a while [~30 minutes]...  multicore processor detected. Compiling with -j 4
 +
make: *** No rule to make target 'core'.  Stop.
 +
Command exited with non-zero status 2
 +
0.01user 0.00system 0:00.02elapsed 50%CPU (0avgtext+0avgdata 1972maxresident)k
 +
0inputs+0outputs (0major+130minor)pagefaults 0swaps
 +
make: *** No targets specified and no makefile found.  Stop.
 +
Command exited with non-zero status 2
 +
0.01user 0.00system 0:00.01elapsed 90%CPU (0avgtext+0avgdata 1972maxresident)k
 +
0inputs+0outputs (0major+130minor)pagefaults 0swaps
 +
ERROR: FreeSWITCH Build Failure.
 +
"

Revision as of 18:35, 12 September 2015

The script seems to have a bug, from what I can tell. The symptom is, that at the very end of the script, when one's prompted to finish from the web browser, one gets an "502 bad gateway error" page served up by nginx instead of the expected configuration page.

Using the Google a bit, it turns out this is an issue when php-fpm and nginx try to talk with each other on different channels.

The script configures /etc/php5/fpm/pool.d/www.conf with a line like:

listen = /var/run/php5-fpm.sock

but it should be

listen = 127.0.0.1:9000

so that configuration file has to be modified and then php-fpm needs to be restarted:

/etc/init.d/php5-fpm stop && sleep 10 && /etc/init.d/php5-fpm start

after that, the configuration page shows up as expected.

I'm running this on a BeagleBone Black, not on a RaspberryPi, but that shouldn't make the difference ;)

Script failing for me using a clean build of Raspbian with updates and upgrade applied an a multi-core Pi.

"Compiling FreeSWITCH. This might take a while [~30 minutes]... multicore processor detected. Compiling with -j 4 make: *** No rule to make target 'core'. Stop. Command exited with non-zero status 2 0.01user 0.00system 0:00.02elapsed 50%CPU (0avgtext+0avgdata 1972maxresident)k 0inputs+0outputs (0major+130minor)pagefaults 0swaps make: *** No targets specified and no makefile found. Stop. Command exited with non-zero status 2 0.01user 0.00system 0:00.01elapsed 90%CPU (0avgtext+0avgdata 1972maxresident)k 0inputs+0outputs (0major+130minor)pagefaults 0swaps ERROR: FreeSWITCH Build Failure. "