Getting disconnected after ending queue with Docker.

[namanhishere]

Hi I'm getting disconnected after ending the queue. The message in my minecraft play screen is: Connection refused: no further infomation Here is the screenshoot of my minecraft playscreen

Here is the logs I get by using docker logs

P: 7 E: 0h 10m - Moka_Sakura
P: 6 E: 0h 9m - Moka_Sakura
P: 5 E: 0h 7m - Moka_Sakura
P: 4 E: 0h 6m - Moka_Sakura
P: 3 E: 0h 4m - Moka_Sakura
P: 2 E: 0h 3m - Moka_Sakura
P: 1 E: 0h 1m - Moka_Sakura
$ Reading position in queue from tab failed! Is the queue empty, or the server isn't 2b2t?
npm notice
npm notice New minor version of npm available! 8.12.1 -> 8.16.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v8.16.0>
npm notice Run `npm install -g [email protected]` to update!
npm notice
npm ERR! path /srv/app
npm ERR! command failed
npm ERR! signal SIGTERM
npm ERR! command sh -c node check.js

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-08-04T03_01_46_347Z-debug-0.log

I connect to the host in local network and my host is an arm x64 machine

[rob9315]

SIGTERM usually indicates that it was manually terminated, like by using ctrl+c or killed using htop/kill. I assume though that you did not do that. do you mind posting the log file the npm err points to?

[namanhishere]

Here is what I get from the logs 2022-08-04T03_01_46_347Z-debug-0.log :

1 info using [email protected]
2 info using [email protected]
3 timing npm:load:whichnode Completed in 6ms
4 timing config:load:defaults Completed in 19ms
5 timing config:load:file:/usr/local/lib/node_modules/npm/npmrc Completed in 8ms
6 timing config:load:builtin Completed in 11ms
7 timing config:load:cli Completed in 13ms
8 timing config:load:env Completed in 3ms
9 timing config:load:file:/srv/app/.npmrc Completed in 2ms
10 timing config:load:project Completed in 53ms
11 timing config:load:file:/root/.npmrc Completed in 1ms
12 timing config:load:user Completed in 4ms
13 timing config:load:file:/usr/local/etc/npmrc Completed in 1ms
14 timing config:load:global Completed in 2ms
15 timing config:load:validate Completed in 1ms
16 timing config:load:credentials Completed in 13ms
17 timing config:load:setEnvs Completed in 9ms
18 timing config:load Completed in 138ms
19 timing npm:load:configload Completed in 140ms
20 timing npm:load:mkdirpcache Completed in 10ms
21 timing npm:load:mkdirplogs Completed in 3ms
22 verbose title npm start
23 verbose argv "start"
24 timing npm:load:setTitle Completed in 11ms
25 timing config:load:flatten Completed in 35ms
26 timing npm:load:display Completed in 46ms
27 verbose logfile logs-max:10 dir:/root/.npm/_logs
28 verbose logfile /root/.npm/_logs/2022-08-04T03_01_46_347Z-debug-0.log
29 timing npm:load:logFile Completed in 59ms
30 timing npm:load:timers Completed in 2ms
31 timing npm:load:configScope Completed in 1ms
32 timing npm:load Completed in 288ms
33 silly logfile done cleaning log files
34 http fetch GET 200 https://registry.npmjs.org/npm 2374ms (cache updated)
35 http fetch GET 200 https://registry.npmjs.org/npm 2559ms (cache updated)
36 timing command:run-script Completed in 15051872ms
37 timing command:start Completed in 15051907ms
38 notice
38 notice New minor version of npm available! 8.12.1 -> 8.16.0
38 notice Changelog: <https://github.com/npm/cli/releases/tag/v8.16.0>
38 notice Run `npm install -g [email protected]` to update!
38 notice
39 verbose stack Error: command failed
39 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:63:27)
39 verbose stack     at ChildProcess.emit (node:events:537:28)
39 verbose stack     at maybeClose (node:internal/child_process:1091:16)
39 verbose stack     at ChildProcess._handle.onexit (node:internal/child_process:302:5)
40 verbose pkgid [email protected]
41 verbose cwd /srv/app
42 verbose Linux 5.9.0-arm-64
43 verbose node v18.4.0
44 verbose npm  v8.12.1
45 error path /srv/app
46 error command failed
47 error signal SIGTERM
48 error command sh -c node check.js
49 verbose exit 1
50 timing npm Completed in 15052307ms
51 verbose code 1
52 error A complete log of this run can be found in:
52 error     /root/.npm/_logs/2022-08-04T03_01_46_347Z-debug-0.log

[namanhishere]

Ps: I also got kicked at queue 8 by server with this message:

[nanospearing]

Is it possible that your computer fell asleep?

[nanospearing]

Ps: I also got kicked at queue 8 by server with this message:

Are you connect to the 2b2t server or the localhost server?

[nanospearing]

SIGTERM usually indicates that it was manually terminated, like by using ctrl+c or killed using htop/kill. I assume though that you did not do that. do you mind posting the log file the npm err points to?

That may be happening becuase they are using docker. To me it looks like something is pushing them out of the queue (possibly becuase they are connecting to the wrong server)

[namanhishere]

Is it possible that your computer fell asleep?

I don't think my computer fall as sleep cause I hosted it on my separate "computer"- which also hosting my website and I did not receive any downtime report at this time

Are you connect to the 2b2t server or the localhost server?

The local server

That may be happening becuase they are using docker. To me it looks like something is pushing them out of the queue (possibly becuase they are connecting to the wrong server)

I still can see the "black screen of the queue" before being kicked