beau
April 26, 2017, 1:12am
1
Installed a brand new shiny version of the FreePBX 64 stable distro on Vultr.com . Everything goes great until I upgrade the modules. I am getting this error:
Symfony \ Component \ Process \ Exception \ ProcessFailedException
I have reinstalled several times today and the same error is thrown with each new install.
Also, the UCP acts like it is working and when trying to upload an audio file to the voicemail greetings it immediately goes into offline mode. The UCP is showing as working in the dashboard.
Any ideas?
beau
April 26, 2017, 1:36am
2
I’ve replicated the UCP error on Firefox and Internet Explorer. Could that one possibly be a permissions error?
sorvani
April 26, 2017, 2:24am
3
After you install, but before you do anything else , you need to perform a yum update -y
beau
April 26, 2017, 3:30am
4
I was able to reproduce the UCP error in both the current stable release and the RC1 so maybe a bug?
As soon as this new (#8 !) instance installs I’ll try the yum update -y suggestion prior to doing anything else.
tm1000
April 26, 2017, 3:52am
5
Curious as Rc1 doesn’t have an offline mode. It will be way more verbose and completely different looking
beau
April 26, 2017, 3:55am
6
I get the exact same error in the UCP after following the yum update -y suggestion.
It did however resolve the other Symfony error.
I’m out of ideas. Any suggestions?
Edit: This was done on a fresh install from the stable freepbx.org iso file.
tm1000
April 26, 2017, 3:57am
7
You couldn’t have gotten the same error between 13 and 14. It’s a completely different interface. There’s no offline mode.
beau
April 26, 2017, 4:00am
8
The behavior was the same. I apologize; should have been clearer. No “offline mode” error was given. I added a voicemail widget and tried uploading both a wav and mp3 file. Both times the file never appeared to upload in any way. I tried on both Chrome and Firefox.
tm1000
April 26, 2017, 4:01am
9
That’s not the same error at all. In one it goes offline meaning it crashed. In the other it does nothing.
beau
April 26, 2017, 4:32am
10
I really just need some help getting the voicemail greeting uploaded manually. I’ve been at this since 8AM this morning through 8 instances trying to get this phone system working.
tm1000
April 26, 2017, 4:44am
11
It’s probably a bug. Nothing more you’ll be able to do until it’s fixed. Upload the file somewhere and we can test.
I had the same problem when updated “Process Management” module to version 13.0.3.6. There is a ticket [FREEPBX-14629] pm2 problem after update - Sangoma Issue Tracker about this, but it is closed. I fixed the issue with following commands:
cd www/html/admin/modules/pm2/node/node_modules/pm2/bin
It is definitely a bug in this module, which should be fixed, instead of asking to execute manually, as suggested in the ticket:
fwconsole install pm2
I didn’t try if this suggestion fixes the problem.
tm1000
April 26, 2017, 3:47pm
13
Because it already is fixed:
$set['name'] = 'NPM Proxy Server Address';
$set['description'] = 'The NPM Proxy server address to use';
$set['emptyok'] = 0;
$set['type'] = CONF_TYPE_TEXT;
$set['level'] = 2;
$set['readonly'] = 1;
$this->freepbx->Config->define_conf_setting('PM2PROXY',$set);
// PM2USECACHE
$set['value'] = true;
$set['defaultval'] =& $set['value'];
$set['options'] = '';
$set['name'] = 'Use package caching for NPM';
$set['description'] = 'This should only be turned off if you have issues installing node modules from NPM';
$set['emptyok'] = 0;
$set['level'] = 1;
$set['readonly'] = 1;
$set['type'] = CONF_TYPE_BOOL;
$this->freepbx->Config->define_conf_setting('PM2USECACHE',$set);
We asked you to reinstall the module.
beau
April 26, 2017, 4:12pm
14
I am still having the voicemail upload issue on brand new installations of both RC1 and the stable version.
I’m going to use the stable version to build out the phone system. Any ideas on fixing the offline mode error so I can upload greetings to voicemails?
beau
April 26, 2017, 4:50pm
16
beau
April 26, 2017, 4:56pm
17
The files both work on my production server. But both fail on a freshly installed server. Could this be a permissions issue?