Question - stdout continues saying '10.244.0.1:<portnumber> is connecting...'

Question

Question - stdout continues saying '10.244.0.1:<portnumber> is connecting...'

karlrissland opened this issue 4 years ago · 3 comments

Any thoughts on why I am getting constant is connecting... messages? The server is up, and I can connect, but can't seem to track down the source of these messages... it looks like the container is port scanning...

Thanks...

Answer 1 · 2021-02-01T23:07:44.000Z

That looks like really odd behavior, I am not sure. Is that 10.244.0.1 the ip of the terraria container? That log message seems to be originating from within your k8s cluster. This is the source for the tshock container <https://github.com/ryansheehan/terraria/blob/master/tshock/Dockerfile>. Just double checking it, I don't see any red flags. The bootstrapper <https://github.com/ryansheehan/terraria/blob/master/tshock/bootstrap.sh> isn't doing anything crazy either. If you're running the tshock version of the container, you may want to ask the question to the tshock team <https://github.com/Pryaxis/TShock/discussions>.

…

On Mon, Feb 1, 2021 at 4:46 PM karlrissland ***@***.***> wrote: Any thoughts on why I am getting constant is connecting... messages? The server is up, and I can connect, but can't seem to track down the source of these messages... it looks like the container is port scanning... [image: image] <https://user-images.githubusercontent.com/9871029/106527380-2d7da800-64b5-11eb-8ce0-a4ff49c13083.png> Thanks... — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#61>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB46ERZKBTIN4SE53Z2CDSLS44VMNANCNFSM4W5TAYAA> .

Answer 2 · 2021-02-02T16:22:19.000Z

It appears to be coming from the container, but still researching, figured I would hit you up in case you have seen it before. This is running in Kubernetes and the vNet address space is 10.0.0.0/8.

How do I specify Vanilla vs. Tshock? All I am doing to start up is set the mount path and specify the WORLD_FILENAME as an environment variable. My thought is, if I can force it to Vanilla and not see the output, then I spend time figuring out what Tshock is doing.... if anything.

Answer 3 · 2021-02-02T16:56:31.000Z

Vanilla is the official terraria server that is managed to run against mono TShock is a project that is almost as old as the game itself. It added a bunch of server administration features. I do not think you will get any insights by comparing vanilla and tshock. They are managed by completely different groups. My advice would be to post something in the tshock discussion group and see what comes back. They are different containers. It just depends on which tag you used to pull the container. The default container is TShock. You can use "vanilla-latest" if you want the base game. Beware though, the vanilla requires a lot more hand holding. IIRC you need to log into the terminal just to save for example, where-as TShock will auto save

…

On Tue, Feb 2, 2021 at 10:22 AM karlrissland ***@***.***> wrote: It appears to be coming from the container, but still researching, figured I would hit you up in case you have seen it before. This is running in Kubernetes and the vNet address space is 10.0.0.0/8. How do I specify Vanilla vs. Tshock? All I am doing to start up is set the mount path and specify the WORLD_FILENAME as an environment variable. My thought is, if I can force it to Vanilla and not see the output, then I spend time figuring out what Tshock is doing.... if anything. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#61 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB46ERY76QLGHDZYC4FLT6DS5ARE5ANCNFSM4W5TAYAA> .