Skip to content
This repository has been archived by the owner on Oct 20, 2023. It is now read-only.

Crash while queueing #59

Closed
VisibleReality opened this issue Apr 21, 2020 · 5 comments
Closed

Crash while queueing #59

VisibleReality opened this issue Apr 21, 2020 · 5 comments

Comments

@VisibleReality
Copy link

VisibleReality commented Apr 21, 2020

The proxy crashed while I was queuing, unfortunately I don't know much else about what happened. It was in queue for about 4 hours, I think. Here is the terminal output:

Edit: after doing a bit of googling, this might have been caused by 2b2t crashing/restarting.

(node:29365) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.

> 2bored2wait@1.0.0 start /home/pi/2b2w/2bored2wait
> node main.js

events.js:183
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRINUSE 0.0.0.0:25565
    at Object._errnoException (util.js:1022:11)
    at _exceptionWithHostPort (util.js:1044:20)
    at Server.setupListenHandle [as _listen2] (net.js:1367:14)
    at listenInCluster (net.js:1408:12)
    at doListen (net.js:1517:7)
    at _combinedTickCallback (internal/process/next_tick.js:141:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)

npm ERR! 2bored2wait@1.0.0 start: `node main.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the 2bored2wait@1.0.0 start script.
npm ERR! This is most likely a problem with the 2bored2wait package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node main.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls 2bored2wait
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 4.19.66-v7+
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "start"
npm ERR! cwd /home/pi/2b2w/2bored2wait
npm ERR! node -v v8.11.1
npm ERR! npm -v 1.4.21
npm ERR! code ELIFECYCLE
npm WARN This failure might be due to the use of legacy binary "node"
npm WARN For further explanations, please read
/usr/share/doc/nodejs/README.Debian

npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     /home/pi/2b2w/2bored2wait/npm-debug.log
npm ERR! not ok code 0```
@VisibleReality
Copy link
Author

Also, here is the contents of npm-debug.log

1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using npm@1.4.21
3 info using node@v8.11.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info prestart 2bored2wait@1.0.0
6 info start 2bored2wait@1.0.0
7 verbose unsafe-perm in lifecycle true
8 info 2bored2wait@1.0.0 Failed to exec start script
9 error 2bored2wait@1.0.0 start: `node main.js`
9 error Exit status 1
10 error Failed at the 2bored2wait@1.0.0 start script.
10 error This is most likely a problem with the 2bored2wait package,
10 error not with npm itself.
10 error Tell the author that this fails on your system:
10 error     node main.js
10 error You can get their info via:
10 error     npm owner ls 2bored2wait
10 error There is likely additional logging output above.
11 error System Linux 4.19.66-v7+
12 error command "/usr/bin/node" "/usr/bin/npm" "start"
13 error cwd /home/pi/2b2w/2bored2wait
14 error node -v v8.11.1
15 error npm -v 1.4.21
16 error code ELIFECYCLE
17 verbose exit [ 1, true ]```

@VisibleReality
Copy link
Author

If it was caused by a 2b2t crash/restart, maybe it would be a good idea to try and join again once the server is back online

@themoonisacheese
Copy link
Owner

looks like you have another program listening on port 25565, usually another minecraft server.

@VisibleReality
Copy link
Author

That's weird, because this is running on a rasbperry pi and I don't think i have any other minecraft server running. It seemed to be working fine until it crashed.

Maybe it was caused because I checked on it's queue progress and noticed that it had stopped queueing. I pressed start queue again and it crashed.

@themoonisacheese
Copy link
Owner

themoonisacheese commented Apr 21, 2020 via email

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants