your-land/bugtracker
your-land/bugtracker
40
21
Issues 3.6k Projects 4 Wiki

Connection to 5.9.0 on low bandwidth results in Timeout #7316

New Issue
Open
opened 2024-08-16 23:11:02 +02:00 by AliasAlreadyTaken · 6 comments
AliasAlreadyTaken commented 2024-08-16 23:11:02 +02:00
Owner
Copy Link

Similar to your-land/administration#208 people on low bandwidth connections report issues when connecting to the testserver.

Similar to your-land/administration#208 people on low bandwidth connections report issues when connecting to the testserver.
AliasAlreadyTaken commented 2024-08-16 23:15:20 +02:00
Author
Owner
Copy Link

On the 5.9.0 testserver (30001), I keep getting these:

2024-08-16 20:46:09: TRACE[ConnectionSend]: con(4/1) Handle per peer queues: peer_id=55489 packet quota: 2048
2024-08-16 20:46:09: VERBOSE[Server]: httpfetch_caller_alloc_secure: allocating 1451523435837045027
2024-08-16 20:46:09: TRACE[ConnectionSend]: con(4/1) processing queued reliable command 
2024-08-16 20:46:09: VERBOSE[ConnectionSend]: con(4/1)Ran out of sequence numbers!
2024-08-16 20:46:09: TRACE[ConnectionSend]: con(4/1) Failed to queue packets for peer_id: 55489, delaying sending of 601170 bytes

The client cannot log in, its either stuck or gets a timeout. That happens on the same device that can log in to the 5.8.0 main server (30000) without problems. The same device can also log in to the 5.9.0 testserver if it uses a normal DSL landline. If I use mobile data, I cannot log in. It eventually ends in a timeout.

This affects ALL servers that were upgraded to 5.9.0: Test, builder and even the NPC server (30003) which is not very content-heavy.

Diaeresis suggested to remove a check: c3a8205ed9

I did that, but yielded no positive result.

On the 5.9.0 testserver (30001), I keep getting these: ``` 2024-08-16 20:46:09: TRACE[ConnectionSend]: con(4/1) Handle per peer queues: peer_id=55489 packet quota: 2048 2024-08-16 20:46:09: VERBOSE[Server]: httpfetch_caller_alloc_secure: allocating 1451523435837045027 2024-08-16 20:46:09: TRACE[ConnectionSend]: con(4/1) processing queued reliable command 2024-08-16 20:46:09: VERBOSE[ConnectionSend]: con(4/1)Ran out of sequence numbers! 2024-08-16 20:46:09: TRACE[ConnectionSend]: con(4/1) Failed to queue packets for peer_id: 55489, delaying sending of 601170 bytes ``` The client cannot log in, its either stuck or gets a timeout. That happens on the same device that can log in to the 5.8.0 main server (30000) without problems. The same device can also log in to the 5.9.0 testserver if it uses a normal DSL landline. If I use mobile data, I cannot log in. It eventually ends in a timeout. This affects ALL servers that were upgraded to 5.9.0: Test, builder and even the NPC server (30003) which is not very content-heavy. Diaeresis suggested to remove a check: https://gitlab.com/tunnelers-abyss/minetest/-/commit/c3a8205ed9a808917d456f217ba99583bc99fa01 I did that, but yielded no positive result.
AliasAlreadyTaken added the
1. kind/bug
2. prio/critical
3. source/engine
 labels 2024-08-16 23:15:36 +02:00
AliasAlreadyTaken added this to the minetest 5.9.0 milestone 2024-08-16 23:15:39 +02:00
TheMadModder commented 2024-08-17 00:12:51 +02:00
Copy Link

Seeing that Alias was able to reproduce the issue. Along with having issues with logging in using a mobile connection. I reproduced the same tests he did. Finding that with a mobile connection I am able to connect to main, test, build server. However if using DSL I can log only onto main server. Not onto the test nor build getting hung up on loading item definitions. Than timing out.

Seeing that Alias was able to reproduce the issue. Along with having issues with logging in using a mobile connection. I reproduced the same tests he did. Finding that with a mobile connection I am able to connect to main, test, build server. However if using DSL I can log only onto main server. Not onto the test nor build getting hung up on loading item definitions. Than timing out.
AliasAlreadyTaken commented 2024-08-17 01:20:36 +02:00
Author
Owner
Copy Link

Apparently there is an upstream issue already, thank you Lars for notifying me!

https://github.com/minetest/minetest/issues/14765

We're also getting a "Ran out of sequence numbers!" spam. We had max_packets_per_iteration = 60000, but also decreasing to 2048 didn't change much.

Here are three debug.txt to the NPC server with debu_log_level = trace, the server is not very large on media compared to the others:

Since we have a repro, I offered them to bring more info, add debugging code or if we can otherwise assist, to please let me know

Apparently there is an upstream issue already, thank you Lars for notifying me! https://github.com/minetest/minetest/issues/14765 We're also getting a "Ran out of sequence numbers!" spam. We had `max_packets_per_iteration = 60000`, but also decreasing to 2048 didn't change much. Here are three debug.txt to the NPC server with debu_log_level = trace, the server is not very large on media compared to the others: * https://your-land.de/additional/7316/attempt1.txt * https://your-land.de/additional/7316/attempt2.txt * https://your-land.de/additional/7316/attempt3.txt Since we have a repro, I offered them to bring more info, add debugging code or if we can otherwise assist, to please let me know
AliasAlreadyTaken commented 2024-08-30 21:35:56 +02:00
Author
Owner
Copy Link

Testing with poor network connection on the Your NeighboursServer, due to a smaller media footprint.

https://your-land.de/additional/7316/attempt4.txt : YN main, packet quota 1024, deleted media cache, none of the patches: Took a while, but I was able to log in.
https://your-land.de/additional/7316/attempt5.txt : YL Testserver, packet quota 2048, deleted media cache, none of the patches: Took a while, but I was able to log in. I saw the message "Ran out of sequence numbers" but then it started anew.

Finally, I used up all my data volume:

https://your-land.de/additional/7316/attempt6.txt : YN main, packet quota 1024, deleted media cache, none of the patches: Timeout and many "ran out of sequence numbers". Yay, a repro.

Now I built https://github.com/sfan5/minetest.git branch lessbrokennetwork:

https://your-land.de/additional/7316/attempt7.txt : YN main, packet quote 1024, kept media cache, patch df8b3b6631a488d818f30d27f6d44cfeddb30f14: Many Ran out of sequence numbers!, then DC

https://your-land.de/additional/7316/attempt8.txt : YN main, packet quote 1024, kept media cache, patch f28d2a78edfaab8f6cced5b7921c647dd5fa0ff1: Many Ran out of sequence numbers!, then DC

Even with both commits I can still reproduce the problem. NOK

Testing with poor network connection on the `Your Neighbours`Server, due to a smaller media footprint. https://your-land.de/additional/7316/attempt4.txt : YN main, packet quota 1024, deleted media cache, none of the patches: Took a while, but I was able to log in. https://your-land.de/additional/7316/attempt5.txt : YL Testserver, packet quota 2048, deleted media cache, none of the patches: Took a while, but I was able to log in. I saw the message "Ran out of sequence numbers" but then it started anew. Finally, I used up all my data volume: https://your-land.de/additional/7316/attempt6.txt : YN main, packet quota 1024, deleted media cache, none of the patches: Timeout and many "ran out of sequence numbers". Yay, a repro. Now I built https://github.com/sfan5/minetest.git branch lessbrokennetwork: https://your-land.de/additional/7316/attempt7.txt : YN main, packet quote 1024, kept media cache, patch df8b3b6631a488d818f30d27f6d44cfeddb30f14: Many Ran out of sequence numbers!, then DC https://your-land.de/additional/7316/attempt8.txt : YN main, packet quote 1024, kept media cache, patch f28d2a78edfaab8f6cced5b7921c647dd5fa0ff1: Many Ran out of sequence numbers!, then DC > Even with both commits I can still reproduce the problem. NOK
AliasAlreadyTaken commented 2024-09-01 00:51:26 +02:00
Author
Owner
Copy Link

Yes, with max_packets_per_iteration=128 and good connection I can do stuff, with bad connection DCs. Please note, YN main (address: your-land.de port 30003) does not have much going on, it's mostly static with few NPCs standing around.

Good connection to 5.9.0 server with 5.9.0 mobile client:

https://your-land.de/additional/7316/attempt9.txt : YN main, packet quote 128, kept media cache, none of the patches: I can log in and run around

Bad connection to 5.9.0 server with 5.9.0 mobile client:

https://your-land.de/additional/7316/attempt10.txt : YN main, packet quote 128, kept media cache, none of the patches: Many Ran out of sequence numbers!, then DC

Bad connection to 5.8.0 server with 5.9.0 mobile client:

YL main, packet quote 60000, kept media cache, server 5.8.0: DC. No debug.txt, because main server

Bad connection to 5.9.0 server with 5.9.0 mobile client:

https://your-land.de/additional/7316/attempt11.txt : YN main, packet quote 1024, kept media cache, commit 1b952a9e34ef5841c0f39513bf6a5ddee3ba53a8: Took a while, then brief login, then DC again

Eventually we'll have to admit that Minetest requires a bandwidth and ping above carrier pidgeon grade - at least smoke signals.

Yes, with `max_packets_per_iteration=128` and good connection I can do stuff, with bad connection DCs. Please note, YN main (address: your-land.de port 30003) does not have much going on, it's mostly static with few NPCs standing around. Good connection to 5.9.0 server with 5.9.0 mobile client: https://your-land.de/additional/7316/attempt9.txt : YN main, packet quote 128, kept media cache, none of the patches: I can log in and run around Bad connection to 5.9.0 server with 5.9.0 mobile client: https://your-land.de/additional/7316/attempt10.txt : YN main, packet quote 128, kept media cache, none of the patches: Many Ran out of sequence numbers!, then DC Bad connection to 5.8.0 server with 5.9.0 mobile client: YL main, packet quote 60000, kept media cache, server 5.8.0: DC. No debug.txt, because main server Bad connection to 5.9.0 server with 5.9.0 mobile client: https://your-land.de/additional/7316/attempt11.txt : YN main, packet quote 1024, kept media cache, commit 1b952a9e34ef5841c0f39513bf6a5ddee3ba53a8: Took a while, then brief login, then DC again Eventually we'll have to admit that Minetest requires a bandwidth and ping above carrier pidgeon grade - at least smoke signals.
AliasAlreadyTaken commented 2025-03-08 18:21:21 +01:00
Author
Owner
Copy Link

This was fixed with 5.11.0 and fixed again for 5.12.0

This was fixed with 5.11.0 and fixed again for 5.12.0
AliasAlreadyTaken modified the milestone from minetest 5.9.0 to luanti 5.12.0 2025-03-08 18:25:56 +01:00
AliasAlreadyTaken added the
4. step/ready to QA test
 label 2025-04-26 01:44:29 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
1. kind/balancing

Depends on balancing

  
1. kind/breaking

something that alters or disables an existing game mechanic

  
1. kind/bug

Something is not working

  
1. kind/construction

A build needs fixing

  
1. kind/documentation

Needs proper documentation

  
1. kind/enhancement

New feature

  
1. kind/griefing

players despoiling builds or nature

  
1. kind/invalid

Not a valid report, e.g. created by mistake with no content.

  
1. kind/meme

issue is mostly a joke

  
1. kind/node limit

something which works for or against the node limit

  
1. kind/other

Something not within the other kinds

  
1. kind/protocol

something concerning how staff should react to player requests, or how players should treat each other

  
2. prio/controversial

not likely to happen w/out a lot of discussion

  
2. prio/critical

Very important

  
2. prio/elevated

something players are eager to have fixed

  
2. prio/good first issue

the resolution to this is could be done by a new minetest contributor, who doesn't yet understand the mod ecosystem

  
2. prio/interesting

one of us has real interest in getting this implemented or fixed. however, more research might be needed.

  
2. prio/low

Not so important

  
3. source/art

art needs to be created or found for this to exist. includes sound, 3d modelling, and in-game building.

  
3. source/client

Issue is with the minetest client, or with player client configuration or the technical details of their setup

  
3. source/engine

Issue is due to a bug or feature of the minetest engine

  
3. source/ingame

Problem and solution exist in-game, e.g. builds or player moderation

  
3. source/integration

Two or more nonbuggy mechanics conflict, or our attempts to rectify conflicting mechanics have created a new bug

  
3. source/lag

A problem which is caused or made worse by lag, due to server processing issues, client processing issues, or network issues

  
3. source/license

A licensing problem is involved

  
3. source/mod upstream

Problem is upstream (not engine/client)

  
3. source/petz

yet another petz bugz.

  
3. source/testserver

Originates on the testserver, no effect on main yet

  
3. source/unknown

   
3. source/website

Affects the website

  
4. step/approved

Alias has approved this feature, someone should implement it

  
4. step/at work

Being worked on

  
4. step/blocked

we plan to do this, but other work has to be finished first

  
4. step/discussion

issue is under discussion, a solution has not been dictated or agreed upon

  
4. step/help wanted

Need some help

  
4. step/needs confirmation

   
4. step/partially fixed

this is mitigated or partially solved, but more work needs to be done

  
4. step/QA main

That's something we can only wait and see whether it hapens again: On the main server

  
4. step/QA NOK

Fix didn't yield the expected results

  
4. step/QA OK

tested

  
4. step/question

More information is needed

  
4. step/ready to deploy

has been QA tested by another person. has no outstanding issues. might be installed on prod, but needs final testing

  
4. step/ready to QA test

the code is supposedly fixed, but needs to be tested.

  
4. step/want approval

Someone can quickly implement this if Alias approves the change/feature

  
5. result/cannot reproduce

   
5. result/duplicate

This issue or pull request already exists

  
5. result/fixed

problem is fixed

  
5. result/maybe

not planned currently, but maybe some day

  
5. result/wontfix

the reported issue won't be changed, whether it's intentional or not.

No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/petz
3. source/testserver
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/QA main
4. step/QA NOK
4. step/QA OK
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
Milestone
Clear milestone
No items
No Milestone
luanti 5.12.0
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/bugtracker#7316
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?