Initialhandler has pinged как исправить

Всем привет! У меня такая проблема:
В консоль bungeecord’а спамит вот этим:

> 16:48:59 [INFO] [/185.180.43.202:49262] <-> InitialHandler has pinged
> 16:48:59 [INFO] [/185.180.43.202:49312] <-> InitialHandler has pinged
> 16:48:59 [WARNING] Error whilst handling query packet from /185.180.43.202:57246
java.lang.IllegalStateException: No session!
at net.md_5.bungee.query.QueryHandler.handleMessage(QueryHandler.java:95)
at net.md_5.bungee.query.QueryHandler.channelRead0(QueryHandler.java:56)
at net.md_5.bungee.query.QueryHandler.channelRead0(QueryHandler.java:22)
at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:99)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357)
at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379)
at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365)
at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919)
at io.netty.channel.epoll.EpollDatagramChannel.read(EpollDatagramChannel.java:679)
at io.netty.channel.epoll.EpollDatagramChannel.access$100(EpollDatagramChannel.java:58)
at io.netty.channel.epoll.EpollDatagramChannel$EpollDatagramChannelUnsafe.epollInReady(EpollDatagramChannel.java:497)
at io.netty.channel.epoll.EpollEventLoop.processReady(EpollEventLoop.java:475)
at io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:378)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at java.lang.Thread.run(Thread.java:748)
> 16:49:00 [WARNING] Query - Incorrect magic!: /185.180.43.202:40532

В чём может быть проблема и как ее решить?

185.180.43.202 — айпи мониторинга, на который добавлен сервер

Gru2303
Активный участник
Пользователь

Баллы:

76

Имя в Minecraft:

Gru2303
Я уже заходил на зарубежные форумы «github» и «spigotmc» Там был ответ октлючить query port.
Так это и решается да, ограничь доступ к квери порту.
Если я отключу квери порт, другие мониторинги не смогут подключаться к серверу. Попробую удалить сервер с того мониторинга. Отпишусь
Не совсем закрыть, а ограничить от всего кроме мониторингов. Этой херней еще и досят.
Зачем вообще нужен кьери?
Полезен что не меняется протокол от версии к версии и можно мониторить все версии ничего не изменяя. А еще он дает чуть больше инфы о сервере.
Тоесть закрыть порт от всех IP кроме разрешённых?
Спасибо за помощь.
Я конечно понимаю, что проблему эту ты решил. Но почему бы не поделиться как именно ты это сделал? Что использовал для фильтрации ip адресов?
imDaniX
Активный участник
Пользователь

Баллы:

96

Имя в Minecraft:

imDaniX

Да элементарный iptables справится по-моему.
Проблема началась с того, что на одном мониторинге я зарегистрировал свой сервер 2 раза, с разными доменами. И он посылал мне query запросы. И возможно при подключении возникала ошибку, когда он не может присоединиться по одному домену, потому что уже подключен по другому домену.

Я просто удалил вторую страницу сервера на мониторинге.

Зато узнал про iptables .

Поделиться этой страницей

Русское сообщество Bukkit

Источник

Mass «InitialHandler has pinged» Messages

Describe the bug

When running geyser with bungeecord I am getting nonstop messages about InitialHandler has pinged as described in the previous bug ticket #583

Spigot: 3486-Spigot-b6d12d1-f3c7a6a (MC: 1.18.2) (Implementing API version 1.18.2-R0.1-SNAPSHOT)
Bungee: BungeeCord-Bootstrap:1.18-R0.1-SNAPSHOT
Geyser: Geyser 2.0.3-SNAPSHOT

To Reproduce

Set up and Run Bungeecord
Run geyser
See mass alerts of initial handler has pinged

Expected behaviour

no initialhandler spam

Screenshots / Videos

Server Version and Plugins

No response

Geyser Dump

No response

Geyser Version

Geyser 2.0.3-SNAPSHOT

Minecraft: Bedrock Edition Device/Version

No response

Additional Context

No response

Camotoy

Disabling the legacy ping passthrough setting should fix this. Let us know if it doesn’t.

my legacy ping passthrough setting is false in the geyser config already

I can attach my config if that is helpful or provide any additional information to help resolve this.

Camotoy

Please provide a Geyser dump.

Run geyser dump (server console) / /geyser dump (ingame chat) on your Geyser instance or server, then copy the link it will give you and paste it here. A Geyser dump is a way of providing us with a bunch of useful information about your server and Geyser config. This doesn’t include any IPs or sensitive data.

Camotoy

The standalone version always uses the legacy ping passthrough method. Unless you disable ping passthrough settings, increase the amount of time between pings, or filter the log in BungeeCord, there isn’t anything we can do.

Источник

Содержание

Minecraft Forums
ReadTimeoutException: Null
exception connecting readtimeoutexception null
Share This Page
Readtimeoutexception null что делать
Comments
Shlobdon commented Feb 15, 2014
exception connecting readtimeoutexception null
Share This Page
Readtimeoutexception null что делать
Comments
Shlobdon commented Feb 15, 2014
Spring 5 Webclient throws ReadTimeout Exception [SPR-17610] #22142
Comments
Minecraft Forums
Waterfall & PaperSpigot — readTimeoutException: null

Minecraft Forums

This thread was marked as Locked by master801 .

ReadTimeoutException: Null

li» data-page-inline=»False» data-scroll-inline=»False»>

Stone Miner
Join Date: 4/19/2013
Posts: 74
Member Details

Diamond Miner
Join Date: 4/3/2012
Posts: 798
Minecraft: Rilesthegiles
Xbox: Opop12345678
Member Details

Stone Miner
Join Date: 4/19/2013
Posts: 74
Member Details

Tree Puncher
Location: Sydney
Join Date: 8/4/2013
Posts: 24
Minecraft: fortress111
Member Details

I know the problem. ReadTimeoutException: Null is some technical jargon to do with Java and that. Try to relog onto the server, and if that doesn’t work, restart your Internet or Minecraft.

As for the full server theory, the reserved slots aren’t shown on signs and the like.

Redstone Miner
Location: Here->
Join Date: 5/22/2013
Posts: 507
Minecraft: QuantumCayo
Member Details

I know the problem. ReadTimeoutException: Null is some technical jargon to do with Java and that. Try to relog onto the server, and if that doesn’t work, restart your Internet or Minecraft.

As for the full server theory, the reserved slots aren’t shown on signs and the like.

This can mean a couple of thinks.
1) You Ping got to large for the server to handle
2) The server got full.
3) The server Terminal kicked you (unlikely)

Источник

exception connecting readtimeoutexception null

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

Thread Status: Not open for further replies.

The administration works very hard to bring you unique, originally created content. Purchasing ranks, boosters, and mystery boxes helps support us in making more, higher quality content.

Readtimeoutexception null что делать

Автор Влад Влад задал вопрос в разделе Браузерные

Помогите что мне делать я захажу в сервер майнкарфт.. Internal Exception: io.netty.handler.timeout.ReadTimeoutException и получил лучший ответ

Ответ от Андрей Шавель[новичек]
Сервер крашнулся. Непарся)
Андрей Шавель
Ученик
(104)
Сервер на хостинге?

Copy link Quote reply

Hello, this has been happening to me a lot lately. Not just me, lots of others within the server. Not sure what it is, can someone help me figure it out?

Lots of other players & I get this error ALL at the same time, then disconnecting us and being buggy on minecraft server list in client. : [Server] INFO disconnected with: ReadTimeoutException : null

Here is a paste of the console for sorta proof that it’s not «just me not making a connection to the server».

Can someone please help me find out what the problem is? I’m currently using BungeeCord build #841.

Источник

exception connecting readtimeoutexception null

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

Thread Status: Not open for further replies.

The administration works very hard to bring you unique, originally created content. Purchasing ranks, boosters, and mystery boxes helps support us in making more, higher quality content.

Readtimeoutexception null что делать

Автор Влад Влад задал вопрос в разделе Браузерные

Ответ от Андрей Шавель[новичек]
Сервер крашнулся. Непарся)
Андрей Шавель
Ученик
(104)
Сервер на хостинге?

Copy link Quote reply

Hello, this has been happening to me a lot lately. Not just me, lots of others within the server. Not sure what it is, can someone help me figure it out?

Lots of other players & I get this error ALL at the same time, then disconnecting us and being buggy on minecraft server list in client. : [Server] INFO disconnected with: ReadTimeoutException : null

Here is a paste of the console for sorta proof that it’s not «just me not making a connection to the server».

Can someone please help me find out what the problem is? I’m currently using BungeeCord build #841.

Источник

Spring 5 Webclient throws ReadTimeout Exception [SPR-17610] #22142

Viswanathan Manickam opened SPR-17610 and commented

I am getting readtimeout exception when I try to load test 1000 requests per second for 30 mins. Also, when the server sits idle for sometime and when I send request, same error occurs the very first time but further requests process fine.

The response time for some requests is around 5 sec but other requests are in 250ms.

Please find the configuration below:

Please find the log I received:

Let me know if I miss anything

Affects: 5.1.3

The text was updated successfully, but these errors were encountered:

Brian Clozel commented

Thanks for raising this issue — the logs you’ve shared are somewhat different, since now it seems the timeout doesn’t happen right away but is triggered 5 seconds after the HTTP call. Let me track down where that timeout comes from and how we can override it.

Brian Clozel As I mentioned, I have 2 issues:

When I run load test 1000 request per second for 30 mins, I see the following read timeouts where I don’t see that 5 seconds different

When the server sits idle for sometime and when they process the first request, I get the read time out with 5 seconds difference

Brian Clozel commented

If I remember correctly, the suffix number you’re seeing in the logs like reactor.Mono.SwitchIfEmpty.48759 is tied to the subscriber.

In your case, this means that

are not about the same HTTP requests. Reactor is scheduling tasks on worker threads, so when you’re seeing things happening sequentially on the same thread, it doesn’t mean those units of work are being done for the same subscriber.

If you follow the subscriber id in the logs, you should see that the amount of time between requesting the data and not getting is about 5 seconds.

Not on that last point, I’ve created a Reactor HTTP server that sends the response body after 10 seconds:

And a WebClient that fetches this data:

I’m not getting any read timeout. So something in your application must be configuring such a timeout.

I’m closing this issue for now, don’t hesitate to reopen it if you manage to reproduce it and provide me with a sample project that I can run on my computer (something that I could clone from github, or even a zip file I could download).

If you look at the second issue logs, the suffix number is 11 for all logs.

Brian Clozel commented

Yes, but in this case this is consistent with your configuration. You’re configuring a read timeout of 5 seconds in your WebClient and the timeout is triggered after 5 seconds. Am i missing something here?

Server always return the response with in 500ms, why I am getting read timeouts? Is there any block? I am trying to understand where the issue occurs.

Thanks for your time.

Brian Clozel commented

In the sample you’re showing, this is not the case:

There are more than 5 seconds between 14:39:33.093 and 14:39:38.128 .

Thank you for your time Brian Clozel Really appreciate your help.

Finally, What would you recommend to avoid read timeouts

Increase read time out seconds?

Brian Clozel commented

It really depends on your use case and constraints. I don’t know if you’re running a benchmark to optimize for throughput, if expecting this load on a regular basis, or if your app is doing some kind of batch processing, if the load is generated by hits on your own app, etc.

If fetching the responses in a timely manner is not really important and you’re running some kind of batch processing, In this case, you probably have a Flux and you want to do HTTP calls for each element. In this case, you could use the limitRate operator and operator variants that accept a concurrency parameter. This will prevent your application from flooding the remote service and hitting those high latencies.

Adding retries will work for the odd case, but if your app is consistently flooding the remote service, then you’re not really solving the issue. But in a regular case, retries are pretty useful.

Changing the timeout configuration at the HTTP level or with timeout operators can work, but you have to operate within your constraints. Your service should probably respond and not create too much latency for others.

In the end, you’re also limited by the performance of the remote system you’re querying.

Brian Clozel Thank you for your comments.

For the issue (When the server sits idle for sometime and when they process the first request, I get the read time out with 5 seconds difference), I did try increase the timeout up to 30 seconds and still getting read timeout. Is thread block on reading the response and throw readtimeout exception when timeout occurs? Can you suggest anything to resolve this?

Also, I tried hitting our remote server using jmeter with same load and not getting any timeouts/exception. All requests processed successfully and return response.

I really appreciate your time.

I am getting same error . @Viswanathan Manickan : Is this issue resolved? If yes , how it got resolved? Appreciate any reference for the same

Источник

Minecraft Forums

Waterfall & PaperSpigot — readTimeoutException: null

li» data-page-inline=»False» data-scroll-inline=»False»>

Newly Spawned
Join Date: 2/8/2020
Posts: 1
Member Details

I think I tried everything, but maybe there is something I overlooked. Connecting to lobby usually works fine, but sometimes it just decides to not let me in with the error as in the title. Here are the logs while joining:
Lobby:

[22:22:54 INFO]: [email protected][id=12ae899b-2b06-3493-8ef1-65539f5ade01,name=r_0_m_a_n,properties=

[22:22:15 INFO]: [/xx.xx.xx.xx:51644] InitialHandler has pinged
[22:22:23 INFO]: [/xx.xx.xx.xx:51654] InitialHandler has connected
[22:22:24 INFO]: [r_0_m_a_n|/xx.xx.xx.xx:51654] ServerConnector [lobby] has connected
[22:22:53 WARN]: [/xx.xx.xx.xx:51654|r_0_m_a_n] -> UpstreamBridge — read timed out
[22:22:53 INFO]: [r_0_m_a_n] disconnected with: ReadTimeoutException : null
[22:22:53 INFO]: [/xx.xx.xx.xx:51654|r_0_m_a_n] -> UpstreamBridge has disconnected
[22:22:54 WARN]: [r_0_m_a_n|/xx.xx.xx.x:51654] ServerConnector [lobby] — read timed out
[22:22:54 INFO]: [r_0_m_a_n|/xx.xx.xx.xx:51654] ServerConnector [lobby] has disconnected

Here are startup logs:
Lobby:

The problem is really inconsistent, sometimes it happens right after reboot, sometimes I can join for hours without trouble. It usually lasts about few minutes, but once I couldn’t connect for about a hour. I tried removing plugins on lobby, however even with only necessary plugins the error persists. It’s worth to mention that players have to spawn in End. Restarting Waterfall doesn’t do anything, while restarting Lobby fixes issue temporarily.

Источник

Gru2303
Активный участник
Пользователь