Machinaris worker Offline problem

[Johan01]

Hello everyone!

While checking the apps status on my TrueNAS Scale server yesterday I discovered that Machinaris is no longer available in the Official Catalog. So that means I have to replace the pod by creating one from scratch. I managed to get it up and running except that the worker's ping fails: connection refused. In the pod's environment variables I specified the worker's IP address to the server's IP address. All ports that have to be forwarded are above 9000. While looking for the root cause I discovered that when the old pod is running (without plots) the failure is gone. It looks like the new pod is pinging the old pod. But both are running on the same host IP: 192.168.1.113. Anyone who could help me on solving this problem? Any leads?

Cheers,
Johan.

 

[sretalla]

If you want pods to communicate, you need to use the internal DNS...

Linking Apps Internally

truecharts.org

 

[Johan01]

If you want pods to communicate, you need to use the internal DNS...

Linking Apps Internally

truecharts.org

I don't want pods to communicate. I want to replace the old official supported Machinaris app with a new one made from scratch because Machinaris is not available anymore. The original app works fine, no connection refused error. But my new one is not. What do I miss or overlook? Why do ports be moved to above 9000 anyway. All what is below is reserved?

 

[sretalla]

Why do ports be moved to above 9000 anyway. All what is below is reserved?

Kubernetes.

TrueCharts has implemented ways to work around that in their apps, iX has not yet done that.

In the pod's environment variables I specified the worker's IP address to the server's IP address.

I don't know the app, so I was feeling like this implied you're trying to get 2 pods to talk to each other... is the pod providing a worker function to a server on another platform somewhere?

Can that be specified with IP and port? (or is that where the problem is... it only looks for the IP and assumes a known port number?)

 

[Johan01]

Kubernetes.

TrueCharts has implemented ways to work around that in their apps, iX has not yet done that.


I don't know the app, so I was feeling like this implied you're trying to get 2 pods to talk to each other... is the pod providing a worker function to a server on another platform somewhere?

Can that be specified with IP and port? (or is that where the problem is... it only looks for the IP and assumes a known port number?)

Machinaris has been an Officially Supported app on TrueNAS Scale but now it has been removed from the catalog. That forces me to create a pod from the Docker image at Github to continue using it on TN Scale. Kris Moore has been working on a Chia app and also introduced the Machinaris app an TN Scale. There should be more knowledge about this how it works at iX to help solve this problem I hope.

 

[Johan01]

Hi!

I am happy to share that I solved the problem. In the edit listing of the container, in the Networking section there is an option "Provide access to node namespace for the workload". When I enabled this option the Port Forwarding section is disabled. After saving, the container became active. I could then access Machinaris' WebUI on its standard port, 8926, so not on port 9003 as needed for the original app. The other 3 ports are now also accessible. There is no more "connection refused" for the worker. All is running fine now.
I don't know if this solution is the same as how the original app works but at least I have a working situation back now. Thanks for you guys for helping me pushing into a good direction.

Cheers,
Johan.