Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

many errors cli: execute: rcon: read tcp 127.0.0.1:PORT->127.0.0.1:25575: i/o timeout and disconnected #492

Closed
DesistDaydream opened this issue Mar 7, 2024 · 6 comments
Labels
wontfix This will not be worked on

Comments

@DesistDaydream
Copy link

DesistDaydream commented Mar 7, 2024

Describe the bug

After the first player logs in, the following content will continue to be output

cli: execute: rcon: read tcp 127.0.0.1:46026->127.0.0.1:25575: i/o timeout
cli: execute: rcon: read tcp 127.0.0.1:44320->127.0.0.1:25575: i/o timeout
cli: execute: rcon: read tcp 127.0.0.1:56154->127.0.0.1:25575: i/o timeout
cli: execute: rcon: read tcp 127.0.0.1:49222->127.0.0.1:25575: i/o timeout
cli: execute: rcon: read tcp 127.0.0.1:47212->127.0.0.1:25575: i/o timeout
cli: execute: rcon: read tcp 127.0.0.1:56456->127.0.0.1:25575: i/o timeout
cli: execute: rcon: read tcp 127.0.0.1:49470->127.0.0.1:25575: i/o timeout
cli: execute: rcon: read tcp 127.0.0.1:52900->127.0.0.1:25575: i/o timeout
cli: execute: rcon: read tcp 127.0.0.1:42510->127.0.0.1:25575: i/o timeout
cli: execute: rcon: read tcp 127.0.0.1:39202->127.0.0.1:25575: i/o timeout
cli: execute: rcon: read tcp 127.0.0.1:60108->127.0.0.1:25575: i/o timeout
......MORE AND MORE

The second player to log in disconnects after a while in the game

To Reproduce

Steps to reproduce the behavior:

  1. run cmd
docker compose up

Expected behavior

  1. There shouldn't be so many error logs
  2. The second player should not disconnect at irregular intervals

Actual behavior

Describe the bug

Screenshots

image

OS information

  • OS: Ubuntu 2204
  • Palworld Version: 0.1.5.1
  • Docker Image Version: latest, IMAGE ID: 256899e761df
    • In fact, it started from a certain version last week, I forgot which one it was.

Hardware information

  • CPU: Intel(R) Celeron(R) J4125 CPU @ 2.00GHz
  • Memory: 32G DDR4

docker-compose.yml contents

services:
  palworld:
    image: thijsvanloef/palworld-server-docker:latest
    restart: unless-stopped
    container_name: palworld-server-home
    stop_grace_period: 30s
    ports:
      - 8213:8211/udp
      - 27017:27015/udp  # Required if you want your server to show up in the community servers tab
    environment:
      PUID: 1000
      PGID: 1000
      PORT: 8211  # Optional but recommended
      PLAYERS: 4  # Optional but recommended
      SERVER_PASSWORD: "home"  # Optional but recommended
      MULTITHREADING: true
      RCON_ENABLED: true
      RCON_PORT: 25575
      TZ: "CST"
      ADMIN_PASSWORD: "home"
      COMMUNITY: false  # Enable this if you want your server to show up in the community servers tab, USE WITH SERVER_PASSWORD!
      SERVER_NAME: "HomeServer"
      SERVER_DESCRIPTION: "Home PalWorld"
    volumes:
      - ./palworld:/palworld/

Container/Host Logs

Describe the bug

Additional context

None

@thijsvanloef
Copy link
Owner

Could you share the logging from the server starting?

@DesistDaydream
Copy link
Author

image

@sonroyaalmerol
Copy link
Contributor

I believe this is a known issue with Palworld's implementation of the rcon protocol. Non-ascii characters is causing it to timeout and is something only Pocketpair can fix. See gorcon/rcon-cli#35

@pipixi
Copy link

pipixi commented Mar 8, 2024

have same error too

@DesistDaydream
Copy link
Author

I saw PalWorld’s official explanation of this issue on this

As for the second user's disconnection after playing the game for a while, I wonder if there is a direct causal relationship with the player's name?

@thijsvanloef thijsvanloef added the wontfix This will not be worked on label Mar 18, 2024
@thijsvanloef
Copy link
Owner

As @sonroyaalmerol mentioned, this is not something I am able to fix, I'm marking this issue as wontfix.

@thijsvanloef thijsvanloef closed this as not planned Won't fix, can't repro, duplicate, stale Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

4 participants