Trouble installing MineOS-node on Debian 7.5 Wheezy

[Ajb]

I apologize if this is posted in the wrong Section.
I am having trouble installing MineOS-node on Debian 7.5 Wheezy. Is this even possible on a Debian 7.5 OS? I’ve been trying for the past 30 minutes, looked up a few guides on how to update to Node v5.0, none of them seem to have helped. I don’t really want to upgrade to Debian 8, because prior experience with it. However if I have to I will.

I’m currently on Node 4.4.0 I think. The installation works, however there are tons of errors (I can post if you need them) from SSH during installation through npm. Also, here is a picture of the current Web-UI, none of my Servers Show, nor any profiles, new or old. http://imgur.com/a/UveBg

Thanks in Advance!

[hexparrot]

What are the errors you see?

What does /var/log/mineos.log say?

Currently wheezy is probably the #1 most common distro release used for MineOS, so it definitely works. For the most part, if you see any errors, you can expect the webui not to work, so no need to check the webui until you see a successful, error-free installation.

[Ajb]

I looked, and saw that in the mineos.log it spams with:

{“level”:“info”,“message”:"[bungee] Discovered server",“timestamp”:“2016-03-13T00:33:51.535Z”}
{“level”:“error”,“message”:"[bungee] Create tail on logs/latest.log failed",“timestamp”:“2016-03-13T00:33:51.537Z”}
{“level”:“info”,“message”:"[bungee] Watching for file generation: logs/latest.log",“timestamp”:“2016-03-13T00:33:51.537Z”}
{“level”:“error”,“message”:"[bungee] Create tail on server.log failed",“timestamp”:“2016-03-13T00:33:51.548Z”}
{“level”:“info”,“message”:"[bungee] Watching for file generation: server.log",“timestamp”:“2016-03-13T00:33:51.548Z”}
{“level”:“info”,“message”:"[bungee] Created tail on proxy.log.0",“timestamp”:“2016-03-13T00:33:51.548Z”}
{“level”:“info”,“message”:"[development] Discovered server",“timestamp”:“2016-03-13T00:33:51.602Z”}
{“level”:“info”,“message”:"[development] Created tail on logs/latest.log",“timestamp”:“2016-03-13T00:33:51.603Z”}
{“level”:“error”,“message”:"[development] Create tail on server.log failed",“timestamp”:“2016-03-13T00:33:51.603Z”}
{“level”:“info”,“message”:"[development] Watching for file generation: server.log",“timestamp”:“2016-03-13T00:33:51.603Z”}
{“level”:“error”,“message”:"[development] Create tail on proxy.log.0 failed",“timestamp”:“2016-03-13T00:33:51.603Z”}
{“level”:“info”,“message”:"[development] Watching for file generation: proxy.log.0",“timestamp”:“2016-03-13T00:33:51.603Z”}
{“level”:“info”,“message”:"[ftbinfinity] Discovered server",“timestamp”:“2016-03-13T00:33:51.604Z”}
{“level”:“info”,“message”:"[ftbinfinity] Created tail on logs/latest.log",“timestamp”:“2016-03-13T00:33:51.604Z”}
{“level”:“error”,“message”:"[ftbinfinity] Create tail on server.log failed",“timestamp”:“2016-03-13T00:33:51.604Z”}
{“level”:“info”,“message”:"[ftbinfinity] Watching for file generation: server.log",“timestamp”:“2016-03-13T00:33:51.604Z”}
{“level”:“error”,“message”:"[ftbinfinity] Create tail on proxy.log.0 failed",“timestamp”:“2016-03-13T00:33:51.605Z”}
{“level”:“info”,“message”:"[ftbinfinity] Watching for file generation: proxy.log.0",“timestamp”:“2016-03-13T00:33:51.605Z”}
{“level”:“info”,“message”:"[kingdoms] Discovered server",“timestamp”:“2016-03-13T00:33:51.605Z”}
{“level”:“info”,“message”:"[kingdoms] Created tail on logs/latest.log",“timestamp”:“2016-03-13T00:33:51.605Z”}
{“level”:“error”,“message”:"[kingdoms] Create tail on server.log failed",“timestamp”:“2016-03-13T00:33:51.605Z”}
{“level”:“info”,“message”:"[kingdoms] Watching for file generation: server.log",“timestamp”:“2016-03-13T00:33:51.605Z”}
{“level”:“error”,“message”:"[kingdoms] Create tail on proxy.log.0 failed",“timestamp”:“2016-03-13T00:33:51.606Z”}
{“level”:“info”,“message”:"[kingdoms] Watching for file generation: proxy.log.0",“timestamp”:“2016-03-13T00:33:51.606Z”}
{“level”:“info”,“message”:"[lobby] Discovered server",“timestamp”:“2016-03-13T00:33:51.606Z”}
{“level”:“info”,“message”:"[lobby] Created tail on logs/latest.log",“timestamp”:“2016-03-13T00:33:51.606Z”}
{“level”:“error”,“message”:"[lobby] Create tail on server.log failed",“timestamp”:“2016-03-13T00:33:51.606Z”}
{“level”:“info”,“message”:"[lobby] Watching for file generation: server.log",“timestamp”:“2016-03-13T00:33:51.607Z”}
{“level”:“error”,“message”:"[lobby] Create tail on proxy.log.0 failed",“timestamp”:“2016-03-13T00:33:51.607Z”}
{“level”:“info”,“message”:"[lobby] Watching for file generation: proxy.log.0",“timestamp”:“2016-03-13T00:33:51.607Z”}
{“level”:“info”,“message”:"[mainserver] Discovered server",“timestamp”:“2016-03-13T00:33:51.608Z”}
{“level”:“info”,“message”:"[mainserver] Created tail on logs/latest.log",“timestamp”:“2016-03-13T00:33:51.608Z”}
{“level”:“error”,“message”:"[mainserver] Create tail on server.log failed",“timestamp”:“2016-03-13T00:33:51.608Z”}
{“level”:“info”,“message”:"[mainserver] Watching for file generation: server.log",“timestamp”:“2016-03-13T00:33:51.608Z”}
{“level”:“error”,“message”:"[mainserver] Create tail on proxy.log.0 failed",“timestamp”:“2016-03-13T00:33:51.608Z”}
{“level”:“info”,“message”:"[mainserver] Watching for file generation: proxy.log.0",“timestamp”:“2016-03-13T00:33:51.608Z”}
{“level”:“info”,“message”:"[minigames] Discovered server",“timestamp”:“2016-03-13T00:33:51.609Z”}
{“level”:“info”,“message”:"[minigames] Created tail on logs/latest.log",“timestamp”:“2016-03-13T00:33:51.610Z”}
{“level”:“error”,“message”:"[minigames] Create tail on server.log failed",“timestamp”:“2016-03-13T00:33:51.610Z”}
{“level”:“info”,“message”:"[minigames] Watching for file generation: server.log",“timestamp”:“2016-03-13T00:33:51.610Z”}
{“level”:“error”,“message”:"[minigames] Create tail on proxy.log.0 failed",“timestamp”:“2016-03-13T00:33:51.610Z”}
{“level”:“info”,“message”:"[minigames] Watching for file generation: proxy.log.0",“timestamp”:“2016-03-13T00:33:51.610Z”}
{“level”:“info”,“message”:"[skyblock] Discovered server",“timestamp”:“2016-03-13T00:33:51.611Z”}
{“level”:“info”,“message”:"[skyblock] Created tail on logs/latest.log",“timestamp”:“2016-03-13T00:33:51.611Z”}
{“level”:“error”,“message”:"[skyblock] Create tail on server.log failed",“timestamp”:“2016-03-13T00:33:51.611Z”}
{“level”:“info”,“message”:"[skyblock] Watching for file generation: server.log",“timestamp”:“2016-03-13T00:33:51.611Z”}
{“level”:“error”,“message”:"[skyblock] Create tail on proxy.log.0 failed",“timestamp”:“2016-03-13T00:33:51.611Z”}
{“level”:“info”,“message”:"[skyblock] Watching for file generation: proxy.log.0",“timestamp”:“2016-03-13T00:33:51.612Z”}
{“level”:“info”,“message”:"[skygrid] Discovered server",“timestamp”:“2016-03-13T00:33:51.612Z”}
{“level”:“info”,“message”:"[skygrid] Created tail on logs/latest.log",“timestamp”:“2016-03-13T00:33:51.612Z”}
{“level”:“error”,“message”:"[skygrid] Create tail on server.log failed",“timestamp”:“2016-03-13T00:33:51.612Z”}
{“level”:“info”,“message”:"[skygrid] Watching for file generation: server.log",“timestamp”:“2016-03-13T00:33:51.612Z”}
{“level”:“error”,“message”:"[skygrid] Create tail on proxy.log.0 failed",“timestamp”:“2016-03-13T00:33:51.613Z”}
{“level”:“info”,“message”:"[skygrid] Watching for file generation: proxy.log.0",“timestamp”:“2016-03-13T00:33:51.613Z”}
{“level”:“info”,“message”:"[temporary] Discovered server",“timestamp”:“2016-03-13T00:33:51.613Z”}
{“level”:“info”,“message”:"[temporary] Created tail on logs/latest.log",“timestamp”:“2016-03-13T00:33:51.613Z”}
{“level”:“error”,“message”:"[temporary] Create tail on server.log failed",“timestamp”:“2016-03-13T00:33:51.614Z”}
{“level”:“info”,“message”:"[temporary] Watching for file generation: server.log",“timestamp”:“2016-03-13T00:33:51.614Z”}
{“level”:“error”,“message”:"[temporary] Create tail on proxy.log.0 failed",“timestamp”:“2016-03-13T00:33:51.614Z”}
{“level”:“info”,“message”:"[temporary] Watching for file generation: proxy.log.0",“timestamp”:“2016-03-13T00:33:51.614Z”}
{“level”:“info”,“message”:"[vanilla] Discovered server",“timestamp”:“2016-03-13T00:33:51.615Z”}
{“level”:“info”,“message”:"[vanilla] Created tail on logs/latest.log",“timestamp”:“2016-03-13T00:33:51.615Z”}
{“level”:“error”,“message”:"[vanilla] Create tail on server.log failed",“timestamp”:“2016-03-13T00:33:51.615Z”}
{“level”:“info”,“message”:"[vanilla] Watching for file generation: server.log",“timestamp”:“2016-03-13T00:33:51.615Z”}
{“level”:“error”,“message”:"[vanilla] Create tail on proxy.log.0 failed",“timestamp”:“2016-03-13T00:33:51.615Z”}
{“level”:“info”,“message”:"[vanilla] Watching for file generation: proxy.log.0",“timestamp”:“2016-03-13T00:33:51.615Z”}
{“level”:“info”,“message”:“Starting up server, using commit: 1853741 fixed issue: crash when pocketmine returned html not json\n”,“timestamp”:“2016-03-13T00:33:51.663Z”}
{“level”:“info”,“message”:"[development] eula.txt detected: ACCEPTED (eula=true)",“timestamp”:“2016-03-13T00:33:56.212Z”}
{“level”:“info”,“message”:"[ftbinfinity] eula.txt detected: ACCEPTED (eula=true)",“timestamp”:“2016-03-13T00:33:56.212Z”}
{“level”:“info”,“message”:"[kingdoms] eula.txt detected: ACCEPTED (eula=true)",“timestamp”:“2016-03-13T00:33:56.213Z”}
{“level”:“info”,“message”:"[lobby] eula.txt detected: ACCEPTED (eula=true)",“timestamp”:“2016-03-13T00:33:56.213Z”}
{“level”:“info”,“message”:"[mainserver] eula.txt detected: ACCEPTED (eula=true)",“timestamp”:“2016-03-13T00:33:56.213Z”}
{“level”:“info”,“message”:"[minigames] eula.txt detected: ACCEPTED (eula=true)",“timestamp”:“2016-03-13T00:33:56.213Z”}
{“level”:“info”,“message”:"[skyblock] eula.txt detected: ACCEPTED (eula=true)",“timestamp”:“2016-03-13T00:33:56.213Z”}
{“level”:“info”,“message”:"[skygrid] eula.txt detected: ACCEPTED (eula=true)",“timestamp”:“2016-03-13T00:33:56.214Z”}
{“level”:“info”,“message”:"[temporary] eula.txt detected: ACCEPTED (eula=true)",“timestamp”:“2016-03-13T00:33:56.214Z”}
{“level”:“info”,“message”:"[vanilla] eula.txt detected: ACCEPTED (eula=true)",“timestamp”:“2016-03-13T00:33:56.214Z”}

[Ajb]

Also I rebooted my Server Box, and reinstalled the MineOS-node from the Tutorial on the Wiki, and now I can no longer even access the Web-UI.

[hexparrot]

is this the complete log?

[Ajb]

Yes, that’s all the entire log file is, it’s spamming it right now, everytime I refresh the SFTP the file gets bigger.

[Ajb]

Do you also need the log of npm-debug, it’s flooded with spam and errors too.

[hexparrot]

@Ajb

Yes, that’s all the entire log file is, it’s spamming it right now, everytime I refresh the SFTP the file gets bigger.

Seems like it’s incomplete, because each time the webui starts up, it records what git commit it’s running off of.[quote=“Ajb, post:7, topic:1112, full:true”]
Do you also need the log of npm-debug, it’s flooded with spam and errors too.
[/quote]

If there’s any errors, anywhere, it’d probably be useful to know what they are.

[Ajb]

After running “npm install” logged in as Root, in the directory of /usr/games/minecraft:

/usr/games/minecraft# npm install

posix@4.0.0 install /usr/games/minecraft/node_modules/posix
node-gyp rebuild

make: Entering directory `/usr/games/minecraft/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 /usr/games/minecraft/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 /usr/games/minecraft/node_modules/posix
gyp ERR! node -v v4.4.0
gyp ERR! node-gyp -v v3.3.0
gyp ERR! not ok
npm WARN deprecated graceful-fs@2.0.3: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.

userid@0.2.0 install /usr/games/minecraft/node_modules/userid
node-gyp rebuild

make: Entering directory `/usr/games/minecraft/node_modules/userid/build’
CXX(target) Release/obj.target/userid/src/userid.o
SOLINK_MODULE(target) Release/obj.target/userid.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/userid.node] Error 1
make: Leaving directory /usr/games/minecraft/node_modules/userid/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 /usr/games/minecraft/node_modules/userid
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”
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! /usr/games/minecraft/npm-debug.log

[Ajb]

Also, to be clear, I am trying to purely upgrade from the Python Web-UI, to the MineOS-node. Since the upgrade didn’t work, I tried downgrading back to the Python Web-UI, and that failed, I’m very curious at to why. Before upgrading to MineOS-node, I backed up the /usr/games/minecraft folder to my Local Desktop PC, so in any case I could hopefully easily revert back to it, but I tried it and did not succeed. Also, I’m thinking the npm install error could be a result from my Server not having Node v5, instead it has Node v4.4, I’ve tried multiple times, and multiple different ways to upgrade to v5, but none of them work.

[hexparrot]

@Ajb

not having Node v5, instead it has Node v4.4

Node 4 is perfectly fine; in fact, I think even my new ISOs distribute 4.x because it’s the first stable version and I’m not using any features that would require 5.

@Ajb

Also, to be clear, I am trying to purely upgrade from the Python Web-UI, to the MineOS-node.

While there’s nothing incorrect about using the Python ISO and then wanting to use the NodeJS webui, one think to keep in mind is that the Python Iso is very old. So the problem you might be having is: have you upgraded your distro recently, i.e., apt-get dist-upgrade?

@Ajb

make: Entering directory `/usr/games/minecraft/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

These aren’t small errors. This should have been present in the first place, moreso than the screenshot of the webui not working–after all, the webui depends on these modules to operate and …as we see, there are some catastrophic failures.

I don’t know for sure, since I haven’t installed the Python ISO in years, but in all likelihood this issue can be solved if the packages on your system are dist-upgrade-ed (not simply upgrade-d).

At any rate, the appropriate path is to do one then the other, so here’s what you can try:

apt-get update
apt-get upgrade
[try the npm steps again]

If no success:

apt-get dist-upgrade
[try the npm steps again]

[Ajb]

I surely thought these steps would work, however with the npm install again it still flooded the SSH with Errors:

/usr/games/minecraft# npm install
npm WARN deprecated native-or-bluebird@1.2.0: please use ‘any-promise’ instead
npm WARN deprecated graceful-fs@3.0.8: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.
npm WARN deprecated static-favicon@1.0.2: use serve-favicon module

posix@4.0.0 install /usr/games/minecraft/node_modules/posix
node-gyp rebuild

make: Entering directory `/usr/games/minecraft/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 /usr/games/minecraft/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 /usr/games/minecraft/node_modules/posix
gyp ERR! node -v v4.4.0
gyp ERR! node-gyp -v v3.3.0
gyp ERR! not ok
npm WARN deprecated graceful-fs@2.0.3: graceful-fs version 3 and before will fail on newer node releases. Please update to graceful-fs@^4.0.0 as soon as possible.
|
utf-8-validate@1.2.1 install /usr/games/minecraft/node_modules/socket.io/node_modules/engine.io/node_modules/ws/node_modules/utf-8-validate
node-gyp rebuild

make: Entering directory `/usr/games/minecraft/node_modules/socket.io/node_modules/engine.io/node_modules/ws/node_modules/utf-8-validate/build’
CXX(target) Release/obj.target/validation/src/validation.o
SOLINK_MODULE(target) Release/obj.target/validation.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/validation.node] Error 1
make: Leaving directory /usr/games/minecraft/node_modules/socket.io/node_modules/engine.io/node_modules/ws/node_modules/utf-8-validate/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 /usr/games/minecraft/node_modules/socket.io/node_modules/engine.io/node_modules/ws/node_modules/utf-8-validate
gyp ERR! node -v v4.4.0
gyp ERR! node-gyp -v v3.3.0
gyp ERR! not ok

bufferutil@1.2.1 install /usr/games/minecraft/node_modules/socket.io/node_modules/engine.io/node_modules/ws/node_modules/bufferutil
node-gyp rebuild

make: Entering directory `/usr/games/minecraft/node_modules/socket.io/node_modules/engine.io/node_modules/ws/node_modules/bufferutil/build’
CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
SOLINK_MODULE(target) Release/obj.target/bufferutil.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/bufferutil.node] Error 1
make: Leaving directory /usr/games/minecraft/node_modules/socket.io/node_modules/engine.io/node_modules/ws/node_modules/bufferutil/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 /usr/games/minecraft/node_modules/socket.io/node_modules/engine.io/node_modules/ws/node_modules/bufferutil
gyp ERR! node -v v4.4.0
gyp ERR! node-gyp -v v3.3.0
gyp ERR! not ok
npm WARN optional dep failed, continuing utf-8-validate@1.2.1

userid@0.2.0 install /usr/games/minecraft/node_modules/userid
node-gyp rebuild

make: Entering directory `/usr/games/minecraft/node_modules/userid/build’
CXX(target) Release/obj.target/userid/src/userid.o
SOLINK_MODULE(target) Release/obj.target/userid.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/userid.node] Error 1
make: Leaving directory /usr/games/minecraft/node_modules/userid/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 /usr/games/minecraft/node_modules/userid
gyp ERR! node -v v4.4.0
gyp ERR! node-gyp -v v3.3.0
gyp ERR! not ok
npm WARN optional dep failed, continuing bufferutil@1.2.1

utf-8-validate@1.2.1 install /usr/games/minecraft/node_modules/socket.io/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/node_modules/utf-8-validate
node-gyp rebuild

make: Entering directory `/usr/games/minecraft/node_modules/socket.io/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/node_modules/utf-8-validate/build’
CXX(target) Release/obj.target/validation/src/validation.o
SOLINK_MODULE(target) Release/obj.target/validation.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/validation.node] Error 1
make: Leaving directory /usr/games/minecraft/node_modules/socket.io/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/node_modules/utf-8-validate/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 /usr/games/minecraft/node_modules/socket.io/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/node_modules/utf-8-validate
gyp ERR! node -v v4.4.0
gyp ERR! node-gyp -v v3.3.0
gyp ERR! not ok

bufferutil@1.2.1 install /usr/games/minecraft/node_modules/socket.io/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/node_modules/bufferutil
node-gyp rebuild

make: Entering directory `/usr/games/minecraft/node_modules/socket.io/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/node_modules/bufferutil/build’
CXX(target) Release/obj.target/bufferutil/src/bufferutil.o
SOLINK_MODULE(target) Release/obj.target/bufferutil.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/bufferutil.node] Error 1
make: Leaving directory /usr/games/minecraft/node_modules/socket.io/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/node_modules/bufferutil/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 /usr/games/minecraft/node_modules/socket.io/node_modules/socket.io-client/node_modules/engine.io-client/node_modules/ws/node_modules/bufferutil
gyp ERR! node -v v4.4.0
gyp ERR! node-gyp -v v3.3.0
gyp ERR! not ok
npm WARN optional dep failed, continuing utf-8-validate@1.2.1
npm WARN optional dep failed, continuing bufferutil@1.2.1
npm ERR! Linux 3.14.32-xxxx-grs-ipv6-64
npm ERR! argv “/usr/bin/nodejs” “/usr/bin/npm” “install”
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! /usr/games/minecraft/npm-debug.log

[Ajb]

Also, is there a way to safely remove the MineOS Python? It seems to still start up even though it’s removed in /usr/games

[hexparrot]

@Ajb

Also, is there a way to safely remove the MineOS Python? It seems to still start up even though it’s removed in /usr/games

If it’s absent in /usr/games/minecraft, it probably wouldn’t be able to run… What are you seeing that suggests it’s still running?

[Ajb]

Never mind about that, I was confused. Anyways, do you possibly know of a fix for this? Recently I’ve decided to quit on NodeJS, so I deleted the NodeJS version of /usr/games/minecraft and installed purely the Python one again, and it won’t work either. The webpage won’t load up, and I’ve followed all the instructions.

[hexparrot]

@Ajb

installed purely the Python one again, and it won’t work either.

That’s not a lot to work with

Have you considered backing up all your servers and a fresh install? While I’m certain that the OS shouldn’t prohibit either from running eventually, figuring out how to do so could take a long time, with this back-and-forth and not knowing exactly what you’re doing on your end.

[Ajb]

That’s the last thing I want to do at the moment. The Servers a very big in file sizes, and I’d have to backup all website files, TeamSpeak, and find anymore important files on the Server, and have to redo everything. It’s not too difficult and it would be probably worth a shot, but it takes forever to back it all up, and to re-install everything.

[hexparrot]

Ok, so I installed on a machine the old Python ISO:

And here is 100% of what I typed in to get mineos-node working. It kinda just started working immediately, I’m not sure what to say.

After all this, I did apt-get upgrade, deleted all the node decencies built, and tried again. It worked.

I also followed that up with apt-get dist upgrade. I expected it to make huge changes to all the packages, but it didn’t. All the same, after deleting all the node deps, they all rebuilt again.

Did you do anything that might have affected this differently, in the events of you maintaining the server and installing all that other software? Changing apt-get repos, adding new ones, etc.?

[Ajb]

I can’t think of anything that could have affected the apt-get repos, or anything in the install process. Do you know of any commands/ways that I should do about completely deleting node, and all the deps and builds of it or whatever, and basically do a fresh installation of node without having to do a fresh installation of my entire OS?

[hexparrot]

Deleting all of the nodejs webui consists of this:

rm /etc/supervisor/conf.d/mineos.conf
rm /etc/mineos.conf
rm -rf /usr/games/minecraft
apt-get -y remove supervisor

This is literally everything the webui uses that is MineOS. We obviously keep git, screen, rdiff-backup, Java, etc.