hexparrot / mineos-node

node.js implementation of mineos minecraft management
GNU General Public License v3.0
335 stars 169 forks source link

All servers disappeared after a reboot. #133

Closed yiays closed 8 years ago

yiays commented 9 years ago

I'm pretty sure this was an error awhile ago, but it still hasn't been fixed for me, I copied some servers over from MineOS 1 to MineOS 2 without error after upgrading my debian based mineos server to mineos 2 via a fresh install, but a vanilla server that I then created didn't show up, so I tried rebooting to no avail. Now none of the servers appear. screenshot-192 168 1 101 8443 2015-10-04 14-28-54 Also, I don't have a git commit number; screenshot-192 168 1 101 8443 2015-10-04 14-32-31 I've moved all but the primary server (named "creative") to the serversold folder in order to try and fix it, but it makes no difference. capture capture My server (named creative) has no server.config file. And creating a new server named "creative" does nothing as well.

hexparrot commented 9 years ago

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

Also, does your /var/games/minecraft/servers/creative contain a server.properties file?

yiays commented 9 years ago

After upgrading node.js to 4.0 using the top answer (by eballeste) here, mineos crashes whenever I log in. Here is the log after attempting to get mineos to run 3 times; [JSON] mineos.log - Pastebin.com

hexparrot commented 9 years ago

Something looks wrong with your server.config files. Are they present or somehow not working? The error logs suggest an issue trying to read values from the file, so you might try deleting the server.config file and letting it get regenerated (and then re-modifying any values you need to)

hexparrot commented 9 years ago

I've found the most straightforward way to update node to be from source node:

http://minecraft.codeemo.com/mineoswiki/index.php?title=MineOS-node_(apt-get)#node_4.0

yiays commented 9 years ago

server.config was already missing, I tried creating a blank server.config file, but no difference. Installing node via that method stopped it from crashing, but creating a server still doesn't work, no folder is created and the webui refuses to open it. New log; mineos.log

hexparrot commented 9 years ago

Alright, so I'm not sure what happened there; server.config never should have been missing, but the webui had marked it as having existed at one point (which it surely did).

Regardless of how it got deleted, the webui should handle it better and I made a commit that should address this crashing: 4c9ae0e4976cc7b2ed276073be1a2f4feb6a68dd

Now, regardless of whether that file is deleted unintentionally or intentionally, the webui will acknowledge it as simply being absent, and it should continue working. Update to the latest commit and I think this is settled.

(Remember, if the file is missing, you'll still need to set the XMX value and runnable jar!)

yiays commented 8 years ago

I've been updating the webui and using npm-install often, but, since commit 4c9ae0e, when I log in as any account, it logs in successfully, but nodejs refuses to send any data to the client, and if I refresh the page, I'm logged out again. According to Chrome's Developer console, communications using socket.js are "400 - Bad Request"s capture Each time the server is started, this one line appears in the log file; mineos.log - looks like a dependancy issue. But how come I can still login, and why isn't anything put in the log when I do?

hexparrot commented 8 years ago

It's definitely not seeing the version it's expecting of the userid module. Let's try this: removing the npm modules directly and having it redownload (and hopefully only the expected ones now).

cd /usr/games/minecraft git fetch git reset --hard origin/master rm -rf node_modules npm install

yiays commented 8 years ago

Great, this seems to have fixed the issue, I've continued testing, and I haven't ran into any further issues.