Disconnect from Nucleus Server

Omniverse Core Platform
1

Dear all:

I have setup a Nucleus Server with public IP.
When I installed a aodt worker (aodt_sim) on that machine,
it works fine and the log is like:

root@28655c40220c:/aodt/aodt_sim/build# ./aodt_sim --nucleus omniverse://public_ip --broadcast broadcast --log debug
[INFO] OVLOG:[Info] Initializing Version 2.38.2-hotfix.5050+tc.742a8f8d
[INFO] Attempting to connect to nucleus url: omniverse://public_ip /broadcast
[INFO] OVLOG:[Info] Initialized Nucleus API v11.20-2ef23c40
[INFO] join request id is 1
[DEBUG] Connection Status: Attempting to connect [omniverse://public_ip]
[INFO] OVLOG:[Info] libcurl error (7): Couldn’t connect to server for https://public_ip/omni/auth/api/device/authorize
[INFO] OVLOG:[Info] Using username/password from environment variables for omniverse://public_ip
[INFO] OVLOG:[Info] Auth: Retrieved token for user “omniverse”
[INFO] OVLOG:[Info] Server is running version 1.14.37+tag-1.14.37.gitlab.12309863.0959a9e9
[INFO] OVLOG:[Info] Server omniverse://public_ip supports atomic checkpoints
[INFO] OVLOG:[Info] Server omniverse://public_ip supports omni-objects and it is enabled
[INFO] OVLOG:[Info] Server omniverse://public_ip supports checkpoints and it is enabled
[INFO] OVLOG:[Info] Connected to omniverse://public_ip
[DEBUG] Connection Status: Successfully connected [omniverse://public_ip]
[DEBUG] Join Channel Callback called
Result: 0
User Data Ptr: 0x58aa2022f460
From:
Event: Join
[DEBUG] event type Join is not Message

However, if I try to start another container on Cloud (H100 server),
the connection will be disconneted from Nucleus Server.
The log is like:

junxian@DGX-CN01:/aodt/aodt_sim/build$ ./aodt_sim --nucleus omniverse://public_ip --broadcast broadcast --log debug
[INFO] OVLOG:[Info] Initializing Version 2.38.2-hotfix.5050+tc.742a8f8d
[INFO] Attempting to connect to nucleus url: omniverse://public_ip /broadcast
[INFO] OVLOG:[Info] Initialized Nucleus API v11.20-2ef23c40
[INFO] join request id is 1
[DEBUG] Connection Status: Attempting to connect [omniverse://public_ip]
[INFO] OVLOG:[Info] libcurl error (7): Couldn’t connect to server for https://public_ip/omni/auth/api/device/authorize
[INFO] OVLOG:[Info] Using username/password from environment variables for omniverse://public_ip
[INFO] OVLOG:[Info] Auth: Retrieved token for user “omniverse”
[INFO] OVLOG:[Info] Server is running version 1.14.37+tag-1.14.37.gitlab.12309863.0959a9e9
[INFO] OVLOG:[Info] Server omniverse://public_ip supports atomic checkpoints
[INFO] OVLOG:[Info] Server omniverse://public_ip supports omni-objects and it is enabled
[INFO] OVLOG:[Info] Server omniverse://public_ip supports checkpoints and it is enabled
[INFO] OVLOG:[Info] Connected to omniverse://public_ip
[DEBUG] Connection Status: Successfully connected [omniverse://public_ip ]
[INFO] OVLOG:[Info] Failed omni1ListenChannel(omniverse://public_ip /broadcast): Connection is terminated
[INFO] OVLOG:[Info] Connection to omniverse://public_ip failed: Disconnected
[INFO] OVLOG:[Info] Will not automatically reconnect because a non-restartable JoinChannelRequest request is active
[DEBUG] Join Channel Callback called
Result: 4
User Data Ptr: 0x555556606ec0
From:
Event: Error
[DEBUG] event type Error is not Message
[DEBUG] Connection Status: Disconnected [omniverse://public_ip]

Any idea or comment is welcome!
Thank you.

Best Regards,
JunXian

2

Nucleus cannot go “public” like this. It is for a private corporate network only.

3

Hi @Richard3D,

Thank you for your reply. However, because our computing nodes do not have public IPs and cannot function as a Nucleus server, is there any suitable framework to separate the computing node and Nucleus server?

Thank you for your assistance.

4

I am not sure I follow. Nucleus has to all be on the same internal local network. The only way to get around this would be to have users vpn in. There is no WAN option and no http option.

If you require a WAN solution you need to look at our GDN graphics developer network to host and stream your omniverse apps on the web.

5

@Richard3D Thank you for your reply. We will try the VPN solution first.