FreePBX - npm-cache: command not found
-
In February Sangoma said to hold tight as it is broken and needs to be updated. Are you sure that you are on the latest release and fully updated right now? Maybe it has been fixed but the fixed has not been added to yours yet?
-
Why are you on a command line at all?
-
@scottalanmiller said in FreePBX - npm-cache: command not found:
In February Sangoma said to hold tight as it is broken and needs to be updated. Are you sure that you are on the latest release and fully updated right now? Maybe it has been fixed but the fixed has not been added to yours yet?
Current systems have pm2 implemented
-
@JaredBusch said in FreePBX - npm-cache: command not found:
@scottalanmiller said in FreePBX - npm-cache: command not found:
In February Sangoma said to hold tight as it is broken and needs to be updated. Are you sure that you are on the latest release and fully updated right now? Maybe it has been fixed but the fixed has not been added to yours yet?
Current systems have pm2 implemented
Yeah, that's why I was wondering if he was on something from pre-February 11th.
-
@scottalanmiller said in FreePBX - npm-cache: command not found:
@JaredBusch said in FreePBX - npm-cache: command not found:
@scottalanmiller said in FreePBX - npm-cache: command not found:
In February Sangoma said to hold tight as it is broken and needs to be updated. Are you sure that you are on the latest release and fully updated right now? Maybe it has been fixed but the fixed has not been added to yours yet?
Current systems have pm2 implemented
Yeah, that's why I was wondering if he was on something from pre-February 11th.
To reinforce this, I have systems predating Feb that use pm2 because they were all updated following the normal update processes.
-
@JaredBusch said in FreePBX - npm-cache: command not found:
Why are you on a command line at all?
Just to troubleshoot
-
@aaronstuder said in FreePBX - npm-cache: command not found:
@JaredBusch said in FreePBX - npm-cache: command not found:
Why are you on a command line at all?
Just to troubleshoot
Then post your actual problem. Not a problem with your troubleshooting
-
Anyone care to wager? I bet the issue is he tried to update modules without updating firmware.
-
@JaredBusch said in FreePBX - npm-cache: command not found:
Anyone care to wager? I bet the issue is he tried to update modules without updating firmware.
You might be right. How do I fix it?
-
@aaronstuder said in FreePBX - npm-cache: command not found:
@JaredBusch said in FreePBX - npm-cache: command not found:
Anyone care to wager? I bet the issue is he tried to update modules without updating firmware.
You might be right. How do I fix it?
https://mangolassi.it/topic/13143/upgrading-the-freepbx-firmware
-
@JaredBusch said in FreePBX - npm-cache: command not found:
@scottalanmiller said in FreePBX - npm-cache: command not found:
In February Sangoma said to hold tight as it is broken and needs to be updated. Are you sure that you are on the latest release and fully updated right now? Maybe it has been fixed but the fixed has not been added to yours yet?
Current systems have pm2 implemented
FreePBX 14 RC1 is missing this and the command line won't add it. But the GUI does.
-
How is FreePBX 14 RC 1 looking?
-
@StrongBad said in FreePBX - npm-cache: command not found:
How is FreePBX 14 RC 1 looking?
So far it has been great. Found one really minor issue, but trivial to fix. Otherwise so far it's been really good.
-
Still having the issue. All updates are installed.
-
npm ERR! Linux 2.6.32-642.6.2.el6.x86_64 npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" npm ERR! node v0.12.18 npm ERR! npm v2.15.11 npm ERR! code ECONNREFUSED npm ERR! errno ECONNREFUSED npm ERR! syscall connect npm ERR! Error: connect ECONNREFUSED npm ERR! at exports._errnoException (util.js:746:11) npm ERR! at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1012:19) npm ERR! { [Error: connect ECONNREFUSED] npm ERR! code: 'ECONNREFUSED', npm ERR! errno: 'ECONNREFUSED', npm ERR! syscall: 'connect', npm ERR! parent: 'pm2' } npm ERR! npm ERR! If you are behind a proxy, please make sure that the npm ERR! 'proxy' config is set properly. See: 'npm help config' npm ERR! Please include the following file with any support request: npm ERR! /var/www/html/admin/modules/pm2/node/npm-debug.log [root@localhost ~]#` -
Loaded plugins: fastestmirror, kmod Setting up Remove Process Resolving Dependencies --> Running transaction check ---> Package nodejs.x86_64 0:0.12.18-1nodesource.el6 will be erased --> Processing Dependency: nodejs for package: freepbx-13.0.192.8-1.shmz65.1.56.noarch --> Running transaction check ---> Package freepbx.noarch 0:13.0.192.8-1.shmz65.1.56 will be erased --> Finished Dependency Resolution Dependencies Resolved Package Arch Version Repository Size Removing: nodejs x86_64 0.12.18-1nodesource.el6 @pbx 25 M Removing for dependencies: freepbx noarch 13.0.192.8-1.shmz65.1.56 @pbx 200 M Transaction Summary Remove 2 Package(s) Installed size: 225 M Is this ok [y/N]: y Downloading Packages: Running rpm_check_debug Running Transaction Test Transaction Test Succeeded Running Transaction Erasing : freepbx-13.0.192.8-1.shmz65.1.56.noarch 1/2 Erasing : nodejs-0.12.18-1nodesource.el6.x86_64 2/2 Verifying : freepbx-13.0.192.8-1.shmz65.1.56.noarch 1/2 Verifying : nodejs-0.12.18-1nodesource.el6.x86_64 2/2 Removed: nodejs.x86_64 0:0.12.18-1nodesource.el6 Dependency Removed: freepbx.noarch 0:13.0.192.8-1.shmz65.1.56 Complete! -
@aaronstuder said in FreePBX - npm-cache: command not found:
Erasing : freepbx-13.0.192.8-1.shmz65.1.56.noarch
Um.... This seems bad? @JaredBusch
-
@aaronstuder said in FreePBX - npm-cache: command not found:
Still having the issue. All updates are installed.
have you moved to FreePBX 14 now?
-
@scottalanmiller Nope, still 13.
-
WTF are you doing?
Why are you even touching things like this.
