[Bug Report] unknown RCON_PORT leads to error in backup

judos commented 7 months ago

Have you read the Important information text above

[X] Yes i did

Current behavior

Errors in Log, yes they are duplicated due to https://github.com/jammsen/docker-palworld-dedicated-server/issues/169, but a backup file is still generated, so this is not dramatic.

Logs

``` time="2024-02-09T19:00:00+01:00" level=info msg=starting iteration=15 job.command=/backupmanager.sh job.position=1 job.schedule="0 * * * *" time="2024-02-09T19:00:00+01:00" level=info msg=starting iteration=15 job.command=/backupmanager.sh job.position=0 job.schedule="0 * * * *" time="2024-02-09T19:00:00+01:00" level=info msg="cli: execute: auth: rcon: dial tcp: address tcp/###RCON_PORT###: unknown port" channel=stderr iteration=15 job.command=/backupmanager.sh job.position=1 job.schedule="0 * * * *" time="2024-02-09T19:00:00+01:00" level=info msg="cli: execute: auth: rcon: dial tcp: address tcp/###RCON_PORT###: unknown port" channel=stderr iteration=15 job.command=/backupmanager.sh job.position=0 job.schedule="0 * * * *" time="2024-02-09T19:00:05+01:00" level=info msg="cli: execute: auth: rcon: dial tcp: address tcp/###RCON_PORT###: unknown port" channel=stderr iteration=15 job.command=/backupmanager.sh job.position=0 job.schedule="0 * * * *" time="2024-02-09T19:00:05+01:00" level=info msg="cli: execute: auth: rcon: dial tcp: address tcp/###RCON_PORT###: unknown port" channel=stderr iteration=15 job.command=/backupmanager.sh job.position=1 job.schedule="0 * * * *" time="2024-02-09T19:00:05+01:00" level=info msg="cli: execute: auth: rcon: dial tcp: address tcp/###RCON_PORT###: unknown port" channel=stderr iteration=15 job.command=/backupmanager.sh job.position=1 job.schedule="0 * * * *" time="2024-02-09T19:00:05+01:00" level=info msg="cli: execute: auth: rcon: dial tcp: address tcp/###RCON_PORT###: unknown port" channel=stderr iteration=15 job.command=/backupmanager.sh job.position=0 job.schedule="0 * * * *" time="2024-02-09T19:00:06+01:00" level=info msg="cli: execute: auth: rcon: dial tcp: address tcp/###RCON_PORT###: unknown port" channel=stderr iteration=15 job.command=/backupmanager.sh job.position=1 job.schedule="0 * * * *" time="2024-02-09T19:00:06+01:00" level=info msg="cli: execute: auth: rcon: dial tcp: address tcp/###RCON_PORT###: unknown port" channel=stderr iteration=15 job.command=/backupmanager.sh job.position=0 job.schedule="0 * * * *" time="2024-02-09T19:00:06+01:00" level=info msg="cli: execute: auth: rcon: dial tcp: address tcp/###RCON_PORT###: unknown port" channel=stderr iteration=15 job.command=/backupmanager.sh job.position=0 job.schedule="0 * * * *" time="2024-02-09T19:00:06+01:00" level=error msg="error running command: exit status 1" iteration=15 job.command=/backupmanager.sh job.position=0 job.schedule="0 * * * *" time="2024-02-09T19:00:06+01:00" level=info msg="cli: execute: auth: rcon: dial tcp: address tcp/###RCON_PORT###: unknown port" channel=stderr iteration=15 job.command=/backupmanager.sh job.position=1 job.schedule="0 * * * *" time="2024-02-09T19:00:06+01:00" level=error msg="error running command: exit status 1" iteration=15 job.command=/backupmanager.sh job.position=1 job.schedule="0 * * * *" ```

Desired behavior

No Error since port is actually set. docker-compose.yml:

...
    environment:
      - RCON_ENABLED=false
      - RCON_PORT=25575

~$ docker exec -it palworld bash

steam@a8d96adfe66c:~/steamcmd$ echo $RCON_PORT
25575

Links to screenshots

No response

To Reproduce

Steps to reproduce the behavior:

Check docker container logs, there's unfortunately no more details

Software setup

OS: Linux 4.19.0-23-amd64 #1 SMP Debian 4.19.269-1 (2022-12-20) x86_64 GNU/Linux
Docker version 23.0.1, build a5ee5b1
Docker Compose version v2.16.0

Hardware setup

vCPU: AMD Ryzen 5 5600G with Radeon Graphics (12 cores)
RAM: 32 GB
Disk: 512 GB SSD

Additional context

No response

judos commented 7 months ago

Note: I had used an old image from around 9days ago. I just updated to the latest image (tag f30bef1) to check whether it still happens.

Can't find old image tag in dockerhub but it was this one.

``` "Id": "sha256:c824f4db1bb383ce80b2cec350d3945d8c03d185c903ff03df343fb031177ade", "RepoTags": [], "RepoDigests": [ "jammsen/palworld-dedicated-server@sha256:e1b30e46fe1c5c77badc25ce4718f7f4f22a4575490fbf8f6613e3463e80c2a7" ], "Parent": "", "Comment": "buildkit.dockerfile.v0", "Created": "2024-01-31T16:58:04.434581211Z", ```

thejcpalma commented 7 months ago

You have RCON set to false so it's normal for the rcon commands used in the backup cron job to give that error.

If RCON is true it will configure the rcon.yaml (the file containing the IP - in this case localhost - and the port) and those errors won't show up. It's expected behavior for this to happen for now.

judos commented 7 months ago

Ah ok, it'll enable it then. Doesn't really matter as long as I haven't a port forwarded for it I guess. Is there a client to interact with this rcon?

jammsen commented 7 months ago

@judos

Is there a client to interact with this rcon?

Sure, https://github.com/jammsen/docker-palworld-dedicated-server/blob/develop/README.md#gameserver-with-rcon-cli-tool

jammsen / docker-palworld-dedicated-server