ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    FreePBX - npm-cache: command not found

    IT Discussion
    4
    28
    3.6k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      Alex Sage
      last edited by

      Still having the issue. All updates are installed.

      scottalanmillerS 1 Reply Last reply Reply Quote 0
      • A
        Alex Sage
        last edited by Alex Sage

        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 ~]#`
        1 Reply Last reply Reply Quote 0
        • A
          Alex Sage
          last edited by Alex Sage

          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!
          1 Reply Last reply Reply Quote 0
          • A
            Alex Sage
            last edited by

            @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

            1 Reply Last reply Reply Quote 0
            • scottalanmillerS
              scottalanmiller @Alex Sage
              last edited by

              @aaronstuder said in FreePBX - npm-cache: command not found:

              Still having the issue. All updates are installed.

              have you moved to FreePBX 14 now?

              A 1 Reply Last reply Reply Quote 0
              • A
                Alex Sage @scottalanmiller
                last edited by

                @scottalanmiller Nope, still 13.

                1 Reply Last reply Reply Quote 0
                • JaredBuschJ
                  JaredBusch
                  last edited by

                  WTF are you doing?

                  Why are you even touching things like this.

                  scottalanmillerS A 2 Replies Last reply Reply Quote 0
                  • scottalanmillerS
                    scottalanmiller @JaredBusch
                    last edited by

                    @jaredbusch said in FreePBX - npm-cache: command not found:

                    WTF are you doing?

                    Why are you even touching things like this.

                    Because his fwconsole threw an error that npm-cache could not be found and fwconsole failed because of it.

                    1 Reply Last reply Reply Quote 0
                    • A
                      Alex Sage @JaredBusch
                      last edited by

                      @jaredbusch So can I fix this?

                      1 Reply Last reply Reply Quote 0
                      • JaredBuschJ
                        JaredBusch
                        last edited by

                        I don't even know how you broke it.

                        Making live changes during the day is a bad idea because I assume you cannot roll your VM back right now.

                        Not sure why you uninstalled nodejs.

                        Did you ever update firmware? It is up to 21 now.

                        A 2 Replies Last reply Reply Quote 0
                        • A
                          Alex Sage @JaredBusch
                          last edited by

                          @jaredbusch I am on 20. 21 must have just been released.

                          1 Reply Last reply Reply Quote 0
                          • A
                            Alex Sage @JaredBusch
                            last edited by

                            @jaredbusch The PBX is still running. I guess I'll just roll back to this morning after hours?

                            1 Reply Last reply Reply Quote 0
                            • 1
                            • 2
                            • 2 / 2
                            • First post
                              Last post