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

    Meteor Node Fibers Error

    Scheduled Pinned Locked Moved IT Discussion
    meteornodenode.jsfibersnode-fibersrocketchat
    11 Posts 2 Posters 10.1k Views
    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.
    • scottalanmillerS
      scottalanmiller
      last edited by

      And when you try to install...

      # npm install fibers
      /
      > [email protected] install /opt/Rocket.Chat/node_modules/fibers
      > node build.js || nodejs build.js
      
      sh: node: command not found
      sh: nodejs: command not found
      
      npm ERR! [email protected] install: `node build.js || nodejs build.js`
      npm ERR! Exit status 127
      npm ERR! 
      npm ERR! Failed at the [email protected] install script.
      npm ERR! This is most likely a problem with the fibers package,
      npm ERR! not with npm itself.
      npm ERR! Tell the author that this fails on your system:
      npm ERR!     node build.js || nodejs build.js
      npm ERR! You can get their info via:
      npm ERR!     npm owner ls fibers
      npm ERR! There is likely additional logging output above.
      npm ERR! System Linux 3.10.0-327.4.5.el7.x86_64
      npm ERR! command "/root/.nvm/v0.10.40/bin/node" "/root/.nvm/v0.10.40/bin/npm" "install" "fibers"
      npm ERR! cwd /opt/Rocket.Chat/server
      npm ERR! node -v v0.10.40
      npm ERR! npm -v 1.4.28
      npm ERR! code ELIFECYCLE
      npm ERR! not ok code 0
      
      1 Reply Last reply Reply Quote 0
      • A
        Alex Sage
        last edited by

        I had this issue, I tried again and it worked.....

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

          @anonymous said:

          I had this issue, I tried again and it worked.....

          I did it once and it worked. The second time, it failed. That's not encouraging at all. Sounds like maybe there is an issue on the server side? I'm concerned about stability here.

          You did a FULL install from scratch or just from partway through?

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

            @scottalanmiller said:

            You did a FULL install from scratch or just from partway through?

            FULL. New VM and Everything.

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

              @anonymous That's what I was afraid of.

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

                I bet Ubuntu would be just fine.....

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

                  @anonymous said:

                  I bet Ubuntu would be just fine.....

                  Ubuntu doesn't even support Mongo (or vice versa) so not likely. I tried Ubuntu and it didn't even get close.

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

                    Of FreeBSD, Ubuntu and CentOS, CentOS is the only one that I got working. But only one out of two times, thus far.

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

                      Okay, so the fibers issue is related to it not liking the NVM installation of Node.

                      So on CentOS 7, the secret is to install the epe-release, then install nodejs. This installs Node v0.10.36, which is not what anyone wants. But once that is installed, you can go back to using NVM and a modern Node release and fibers is able to install!

                      So...

                      yum -y install epel-release
                      yum -y install nodejs
                      npm install fibers
                      

                      Ta da

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

                        This post is deleted!
                        1 Reply Last reply Reply Quote 0
                        • 1 / 1
                        • First post
                          Last post