hexparrot / mineos-node

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

Segfault when starting Minecraft server #230

Closed Athorcis closed 7 years ago

Athorcis commented 7 years ago

When i try to start the Minecraft server i work but mineos crashes

info: [server_hartefak] 127.0.0.1 issued command : "start"
info: [server_hartefak] received request "start"
error: { [Error: connect ECONNREFUSED]
  code: 'ECONNREFUSED',
  errno: 'ECONNREFUSED',
  syscall: 'connect' }
error: { [Error: connect ECONNREFUSED]
  code: 'ECONNREFUSED',
  errno: 'ECONNREFUSED',
  syscall: 'connect' }
error: { [Error: connect ECONNREFUSED]
  code: 'ECONNREFUSED',
  errno: 'ECONNREFUSED',
  syscall: 'connect' }
Erreur de segmentation

And if i try to restart mineos it crashes until the Minecraft server is stopped.

hexparrot commented 7 years ago

A few questions:

1) is this the first server you're trying to set up? (no other servers running, etc.) 2) have you restarted the host and the problem persists? 3) what settings did you fill in for this server that are changing the default? 4) what install is this, MineOS Turnkey? Installed on a self-installed distro?

Athorcis commented 7 years ago
  1. yes this is the first time i use MineOS
  2. i did but the problem is still there
  3. I tried with the default settings and it didn't worked either, but my settings are:

     use_https = false
     socket_host = '127.0.0.1'
     socket_port = 8080
     base_directory = '/var/games/minecraft'
    
     webui_locale = 'fr_FR'
  4. I installed mineos-node from git and i'm on Debian 8
hexparrot commented 7 years ago

socket_host = '127.0.0.1' use_https = false

Why did you make these changes? They will adversely affect the way the webui works. For example, HTTPS....really has no reason to be off, and socket host 0.0.0.0 is the appropriate value rather than 127.0.0.1. The defaults are sane, and I recommend you use them to help eliminate additional (and easily avoidable) causes of errors.

I suggest you try and successfully get a vanilla server up with no modifications and see if the error persists.

Have you also changed the Minecraft server's IP to 127.0.0.1 and port?

Athorcis commented 7 years ago

I did these changes to have MineOS behind Apache on port 443. I resetted /etc/mineos.conf but it's still crashing. I did not changed the ip and the port for the minecraft server I'll try to install MineOS on a fresh VM and i'll let you know

Athorcis commented 7 years ago

When I tried to install it on a fresh vm the installed version of node v0.10.x, which caused npm install to failed, so I installed v0.12.18 and it worked, no crash when starting minecraft. I installed a new copy of node v0.12.8 (because that was already the version I was supposed to have) on my host, I deleted the node_modules folder in /usr/games/minecraft, then ran npm install again and it worked I have an error though Cannot bind broadcaster to ip should I ignore it ?