Since you got it to work first try, I suppose I must have changed/installed something that conflicts with NodeJS or something like that. I don’t install many things though, only software that is needed for Server use. Do you know of any programs that might conflict or be bad to use with NodeJS? I could send you a list of all programs installed if you need that.
Also just checked the /var/log/mineos.log and found this:
What ISO did you install your system with? (provide URL if possible) The errors from the very first npm post have made it clear there is an issue with your build environment in building the node dependencies.
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.22 internal error, aborting at …/…/bfd/reloc.c line 443 in bfd_get_reloc_size
I’m not sure entirely how to solve this problem. Your build environment just doesn’t seem to be in good shape somehow. Again from my Wheezy installation (the Python ISO)
This is where your build is failing. It’s not failing on the MineOS scripts, executing it or installing it, but just building the dependencies. If you get an error from the following commands, we have reduced the problem to the smallest possible repro case.
cd
mkdir tempdir
cd tempdir/
npm install posix
You can then delete this temporary directory rm -rf ~/tempdir. At any rate, if this is where you can’t get past, you’ll have to go back to the Python webui; unfortunately I don’t know what’s wrong with your build environment.
It might be possible to use the sid repos and go past 2.22, but to be honest, that’s a pretty drastic change. sid is considered the unstable branch, so to do this to your production system is probably an iffy idea at best, and would (if things don’t go as you expect them to) take longer to remedy than probably just starting from a new, fresh install and installing your other server things like teamspeak.
Also, I’m not sure if my Web Browser is blocking it, but for some reason Google Chrome allows me to connect to the MineOS Panel and Firefox does not. It might have been working the entire time, except I was only trying to connect on Firefox.
I’ll try what you suggested hexparrot, thanks for all the support.
Update:
Just tried the commands you told me to do, and I see errors sadly:
make: Entering directory `/root/tempdir/node_modules/posix/build’
CXX(target) Release/obj.target/posix/src/posix.o
SOLINK_MODULE(target) Release/obj.target/posix.node
/usr/bin/ld: BFD (GNU Binutils for Debian) 2.22 internal error, aborting at …/…/bfd/reloc.c line 443 in bfd_get_reloc_size
/usr/bin/ld: Please report this bug.
collect2: error: ld returned 1 exit status
make: *** [Release/obj.target/posix.node] Error 1
make: Leaving directory /root/tempdir/node_modules/posix/build' gyp ERR! build error gyp ERR! stack Error: make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23)
gyp ERR! stack at emitTwo (events.js:87:13)
gyp ERR! stack at ChildProcess.emit (events.js:172:7)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)
gyp ERR! System Linux 3.14.32-xxxx-grs-ipv6-64
gyp ERR! command “/usr/bin/nodejs” “/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js” “rebuild”
gyp ERR! cwd /root/tempdir/node_modules/posix
gyp ERR! node -v v4.4.0
gyp ERR! node-gyp -v v3.3.0
gyp ERR! not ok
npm ERR! Linux 3.14.32-xxxx-grs-ipv6-64
npm ERR! argv “/usr/bin/nodejs” “/usr/bin/npm” “install” “posix”
npm ERR! node v4.4.0
npm ERR! npm v2.14.20
npm ERR! code ELIFECYCLE
npm ERR! posix@4.0.0 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the posix@4.0.0 install script ‘node-gyp rebuild’.
npm ERR! This is most likely a problem with the posix package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs posix
npm ERR! Or if that isn’t available, you can get their info via:
npm ERR!
npm ERR! npm owner ls posix
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /root/tempdir/npm-debug.log
I think I’ll just stick with Python, it works perfectly fine for me, and I’m fine with sticking with it. Soon I’ll be upgrading to a new system, so I’ll likely try to install the MineOS-node on that system before anything else. Thanks for all the support! If you have any other suggestions I’d still be happy to try them! (I’m not giving up on switching to MineOS-node, I’m just not going to spend every minute of the day trying to find a way to fix it). That being said, still if you think of anymore ways to possibly fix these errors, I’m all ears.