UCP Daemon Showing Red Flames

I’m running a brand-new installation of FreePBX ( on hyper-V on Windows 2012 Server R2. Everything is working just fine except for the UCP Daemon showing red flames. If my hold my mouse over it the pop-up message says UCP Node is not running.

I can login with a User Control Panel, however, I see the following error at the top of the screen, “Unable to connect to the UCP Node Server because: ‘Error: xhr poll error’”.

/var/log/asterisk/ucp_err.log shows…

_ throw err;_
_ ^_
Error: Cannot find module ‘asterisk-manager’
_ at Function.Module.resolveFilename (module.js:338:15)
_ at Function.Module.load (module.js:280:25)
_ at Module.require (module.js:364:17)_
_ at new require (module.js:380:17)_
_ at connect2AstMan (/var/www/html/admin/modules/ucpnode/node/lib/freepbx.js:111:11)_
_ at EventEmitter. (/var/www/html/admin/modules/ucpnode/node/lib/freepbx.js:42:6)_
_ at EventEmitter.emit (events.js:95:17)_
_ at /var/www/html/admin/modules/ucpnode/node/lib/config.js:32:7_
_ at Query. (/var/www/html/admin/modules/ucpnode/node/lib/config.js:55:4)_
_ at Query.emit (events.js:95:17)_

Any suggestions on how I can fix this?

Todd –

BTW, ucpnode is actually running…

fwconsole stop ucpnode
Running FreePBX shutdown…

Stopping UCP Server
Stopped UCP Server

f_wconsole start ucpnode_

Running FreePBX startup…
Taking too long? Customize the chown command, See http://wiki.freepbx.org/display/FOP/FreePBX+Chown+Conf
Setting Permissions…
_ Collecting Files…Done_
_ 5396/5396 [============================] 100%_
Finished setting permissions
Unable to run Pre-Asterisk hooks, because Asterisk is already running on PID 1713 and has been running for 22 hours, 2 minutes, 25 seconds
Starting UCP Server
Started UCP Server

Where are all the random “_” coming from?

killall node
fwconsole start ucpnode

I just fixed it by doing the following…

yum remove nodejs
amportal a ma uninstall ucpnode
amportal a ma remove ucpnode
amportal a ma download ucpnode
amportal a ma install ucpnode
yum install nodejs

Looking at the ucpnode install.log files it appears the install had issues. Anyway, a reinstall fixed the issue. Thanks for your help!!

Todd -

1 Like