MineOS-node released on Turnkey ISO

nerdherdtnh · August 13, 2015, 11:54pm

Is this a new version of MineOS? I’d love to take it for a whirl but I have no idea how to update my old server. Should I just backup my server files (just worlds, come to think of it) and pop them onto this new distribution?

Thanks,
nerdherdtnh

hexparrot · August 14, 2015, 3:09pm

It is recommended that you simply install the latest MineOS from the ISO and just import your previous servers.

By no means is this required, but my experience with the community at large shows that it takes less time and has substantially less room for error.

As a side note, of course you do not need the Turnkey ISO, just as before, the webui can be installed atop an existing distribution (but here, you just want to avoid the removal steps of the previous one).

Matt_Davis · August 16, 2015, 9:53pm

Okay, so this could be a silly questions but I’ll ask anyway.

I’m currently running a Ubuntu 14.04 server ( For MineOS and Teamspeak3) I’d like to take advantage of the new features but I’m unsure if I would be able to install the MineOS-Node ISO.

Essentially, is the MineOS iso a completely different OS that will not allow me to run my Teamspeak 3 server?

hexparrot · August 17, 2015, 12:12am

Quite the opposite. The only thing changing here is the MineOS webui is the Node.js version vs the Python version. The underlying OS is 100% the exact same Turnkey Core; identical in all ways.

Matt_Davis · August 17, 2015, 12:56am

Awesome, thanks for the info!

josh4trunks · August 19, 2015, 6:03am

Congratulations @hexparrot on the release of MineOS-Node!

I’m looking into updating the FreeNAS plugin, and here are my observations thus far…

npm-uname wouldn’t compile for me (trying this in a freebsd jail)
from poking around it looks like there is no longer a config file to set things like base_directory, webui port, or https
am I missing something?
will this functionality be added back in the future?

QueBall · August 20, 2015, 8:47pm

I installed the node.js version but it seems to have a glitch detecting that the server started. It always shows the server is down but it actually does start up. I can connect to the minecraft server. The server console log shows it’s started. Just the webui does not see it.

WebUI shows version 1.2.2

Doing the debug command:
root@core ~# cd /usr/games/minecraft/
root@core games/minecraft# ./mineos_console.js -d /var/games/minecraft ping_debug
path.js:488
throw new TypeError(‘Arguments to path.join must be strings’);
^
TypeError: Arguments to path.join must be strings
at Object.posix.join (path.js:488:13)
at new mineos.mc (/usr/games/minecraft/mineos.js:127:15)
at Object. (/usr/games/minecraft/mineos_console.js:119:16)
at Module._compile (module.js:460:26)
at Object.Module._extensions…js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Function.Module.runMain (module.js:501:10)
at startup (node.js:129:16)
at node.js:814:3
root@core games/minecraft#

jghake · August 31, 2015, 11:19pm

I’m having significant performance problems and lost ticks. Would upgrading to node help me alleviate these problems?

hexparrot · August 31, 2015, 11:27pm

No, the webui should never really be a factor in server performance, so switching from one to the other should have zero performance impact on your servers.

You should instead look into what the bottleneck is–I/O? CPU? Memory & swapping?

Twistit · September 10, 2015, 7:50am

I am unable to add multiple additional Java arguments.

hexparrot · September 11, 2015, 8:47pm

This issue was identified and fixed in a recent commit that wasn’t on the ISO. If you update your scripts in git, multiple java arguments will be properly parsed.

iMelsom · September 14, 2015, 6:50am

Any plans or changes coming as a result of the release of node.js 4.0?

github.com

nodejs/node/blob/v4.0.0/CHANGELOG.md

# Node.js ChangeLog

## 2015-09-08, Version 4.0.0 (Stable), @rvagg

### Notable changes

This list of changes is relative to the last io.js v3.x branch release, v3.3.0. Please see the list of notable changes in the v3.x, v2.x and v1.x releases for a more complete list of changes from 0.12.x. Note, that some changes in the v3.x series as well as major breaking changes in this release constitute changes required for full convergence of the Node.js and io.js projects.

* **child_process**: `ChildProcess.prototype.send()` and `process.send()` operate asynchronously across all platforms so an optional callback parameter has been introduced that will be invoked once the message has been sent, i.e. `.send(message[, sendHandle][, callback])` (Ben Noordhuis) [#2620](https://github.com/nodejs/node/pull/2620).
* **node**: Rename "io.js" code to "Node.js" (cjihrig) [#2367](https://github.com/nodejs/node/pull/2367).
* **node-gyp**: This release bundles an updated version of node-gyp that works with all versions of Node.js and io.js including nightly and release candidate builds. From io.js v3 and Node.js v4 onward, it will only download a headers tarball when building addons rather than the entire source. (Rod Vagg) [#2700](https://github.com/nodejs/node/pull/2700)
* **npm**: Upgrade to version 2.14.2 from 2.13.3, includes a security update, see https://github.com/npm/npm/releases/tag/v2.14.2 for more details, (Kat Marchán) [#2696](https://github.com/nodejs/node/pull/2696).
* **timers**: Improved timer performance from porting the 0.12 implementation, plus minor fixes (Jeremiah Senkpiel) [#2540](https://github.com/nodejs/node/pull/2540), (Julien Gilli) [nodejs/node-v0.x-archive#8751](https://github.com/nodejs/node-v0.x-archive/pull/8751) [nodejs/node-v0.x-archive#8905](https://github.com/nodejs/node-v0.x-archive/pull/8905)
* **util**: The `util.is*()` functions have been deprecated, beginning with deprecation warnings in the documentation for this release, users are encouraged to seek more robust alternatives in the npm registry, (Sakthipriyan Vairamani) [#2447](https://github.com/nodejs/node/pull/2447).
* **v8**: Upgrade to version 4.5.103.30 from 4.4.63.30 (Ali Ijaz Sheikh) [#2632](https://github.com/nodejs/node/pull/2632).
 - Implement new `TypedArray` prototype methods: `copyWithin()`, `every()`, `fill()`, `filter()`, `find()`, `findIndex()`, `forEach()`, `indexOf()`, `join()`, `lastIndexOf()`, `map()`, `reduce()`, `reduceRight()`, `reverse()`, `slice()`, `some()`, `sort()`. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray for further information.
 - Implement new `TypedArray.from()` and `TypedArray.of()` functions. See https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/TypedArray for further information.
 - Implement arrow functions, see https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Arrow_functions for further information.
 - Full ChangeLog available at https://github.com/v8/v8-git-mirror/blob/4.5.103/ChangeLog

This file has been truncated. show original

hexparrot · September 18, 2015, 9:38pm

Checked and works under nodev4. Not yet pulled in all the dependency updates because it breaks it on FreeBSD. Waiting for the update of npm crypt3 and it’ll be full stable 4.1.0.

DMplay · September 26, 2015, 3:31am

Does the new turnkey release FIX that bug where firewall entries were not saved in the system webmin? I recall having to actually manually write them to get things to work. I see the versions are the same in the new iso released.

I’d like to upgrade from my old mineos Turnkey to the new one but i’ve made a bunch of customizations to the turnkey and it just works. Is there a way to install the MineOSnodejs part only? It seems node-js is not a package for this older turnkey release.

tripkin · September 26, 2015, 5:09pm

I don’t know if it will work for you, but I went to the install docs for the python version and uninstalled it following the install directions in reverse. Don’t take any shortcuts and leave stuff because ‘it should be the same’, it isn’t. Then I followed the install instructions for node webui and it worked, brought up all my worlds, everything was good.

The only thing that didn’t come back were my old vanilla minecraft profiles and I don’t know how to add them back in but I was able to set the servers to the Mojang profiles and they are running fine.

Otherwise, this should work. I don’t know which instructions you should follow for Turnkey Linux - maybe Debian/Ubuntu? Perhaps someone else can answer that if you don’t know. I am running Ubuntu 14.04, and like I said it worked flawlessly.

Good luck! And make a backup before you start this - just in case! 8’)

EDIT: Based on Debian, so you should be able to use those instructions.

DMplay · September 26, 2015, 11:41pm

it seems the nodejs is not getable using the apt-get library for that turnkey version

carstorm · November 3, 2015, 3:42am

I saw awhile ago somewhere but can not find the info now. How would I go about doing this? What are the exact commands I would type in to update the webUI (any any other updates to the OS that there may be)?

hexparrot · November 3, 2015, 3:15pm

See the wiki for updating the webui.

And updating the OS would be through apt-get, which is a normal Debian/Ubuntu utility. Many guides and tutorials can teach you the very simple use of apt-get for keeping your OS updated.

carstorm · November 3, 2015, 5:58pm

Ahh already did the apt-get upgrade (and dist-upgrade), thought there was more to it than that. Thanks for the quick reply, I have also updated my WebUI now!

Dr_Glickenstine · November 3, 2015, 6:53pm

Where would you post changelogs, and how can I get notification of new updates?