Isaac Sim (2021.1.1) Wont Launch (Omniverse 1.3.4)

When I click “Launch” in Omniverse for Isaac sim it 1/2 opens a window and then crashes immediately. (I am assuming it crashes, there is no error displayed it just doesn’t open anything.)

Details about my installation:

I have installed Omniverse (1.3.4) and set up a local Nucleus Service (2021.2.5). I used the Omniverse Echange to install Isaac Sim (2021.1.1).

I am using the Ubuntu 18.04 NVIDIA RTX image on EC2 with the g4dn.xlarge instance. I have installed a vnc server to support the GUI. It is set up with 500 extra GB of storage.

I was looking at this thread but running ./isaac-sim.sh -v also results in an error.

2021-11-15 19:56:55 [5,229ms] [Info] [omni.client.plugin]  Tick: provider_nucleus: Connected to localhost:3009
2021-11-15 19:56:55 [5,230ms] [Warning] [carb.python] default server omniverse://localhost does not have /Isaac folder
2021-11-15 19:56:55 [5,230ms] [Warning] [carb.python] /isaac/nucleus/default not specified in json config or via --/isaac/nucleus/default="omniverse://my-nucleus-server" command line
2021-11-15 19:56:55 [5,231ms] [Warning] [carb.python] Attempting to locate server from previously saved servers...
2021-11-15 19:56:55 [5,231ms] [Info] [carb.settings.python] ISettings.get(...) was called on element that has no value (from python). Use set_default(...) before to set default value. (path = '/persistent/app/omniverse/savedServers')
2021-11-15 19:56:55 [5,231ms] [Warning] [carb.python] /persistent/app/omniverse/savedServers setting not found
2021-11-15 19:56:55 [5,231ms] [Warning] [carb.python] /persistent/app/omniverse/mountedDrives setting not found
2021-11-15 19:56:55 [5,231ms] [Warning] [carb.python] No saved servers
2021-11-15 19:56:55 [5,231ms] [Error] [carb.python] Could not find nucleus server with /Isaac folder
.
.
.
2021-11-15 19:56:56 [6,499ms] [Fatal] [carb.crashreporter-breakpad.plugin] libpthread.so.0!funlockfile
2021-11-15 19:56:56 [6,503ms] [Fatal] [carb.crashreporter-breakpad.plugin] libomni.kit.renderer.plugin.so!void std::vector<unsigned long, std::allocator<unsigned long> >::_M_realloc_insert<unsigned long const&>(__gnu_cxx::__normal_iterator<unsigned long*, std::vector<unsigned long, std::allocator<unsigned long> > >, unsigned long const&)
2021-11-15 19:56:56 [6,506ms] [Fatal] [carb.crashreporter-breakpad.plugin] libomni.kit.renderer.plugin.so!carbOnPluginRegisterEx
2021-11-15 19:56:56 [6,510ms] [Fatal] [carb.crashreporter-breakpad.plugin] libomni.kit.renderer.plugin.so!std::__future_base::_State_baseV2::_M_is_deferred_future() const
2021-11-15 19:56:56 [6,515ms] [Fatal] [carb.crashreporter-breakpad.plugin] libcarb.events.plugin.so!void std::this_thread::sleep_for<long, std::ratio<1l, 1000000l> >(std::chrono::duration<long, std::ratio<1l, 1000000l> > const&)
2021-11-15 19:56:56 [6,520ms] [Fatal] [carb.crashreporter-breakpad.plugin] libomni.kit.loop-default.plugin.so!std::thread::_State_impl<std::thread::_Invoker<std::tuple<omni::kit::RunLoopThread::run()::{lambda()#1}> > >::~_State_impl()
2021-11-15 19:56:56 [6,525ms] [Fatal] [carb.crashreporter-breakpad.plugin] libomni.kit.app.plugin.so!_init
2021-11-15 19:56:56 [6,530ms] [Fatal] [carb.crashreporter-breakpad.plugin] libomni.kit.app.plugin.so!carbOnPluginPostShutdown
2021-11-15 19:56:56 [6,531ms] [Fatal] [carb.crashreporter-breakpad.plugin] kit!_init
2021-11-15 19:56:56 [6,536ms] [Fatal] [carb.crashreporter-breakpad.plugin] libc.so.6!__libc_start_main
2021-11-15 19:56:56 [6,536ms] [Fatal] [carb.crashreporter-breakpad.plugin] kit!_init
Floating point exception (core dumped)

Is there a way to create this missing Isaac folder manually?

Hi, here are the instructions to add the /Isaac folder.
https://docs.omniverse.nvidia.com/app_isaacsim/app_isaacsim/setup.html#adding-sample-assets

Does Create or other Omniverse apps works?

Unfortunately I cannot run Isaac Sim at all so I cant follow the instructions you linked. I have not tried to run a different app. I will install and try Create now.

Thank you for your swift reply!

The issue is not specific to Isaac Sim. When I hit launch on Create it also does nothing. I am assuming this is a crash

Yes, Vulkan is not supported over VNC without a physical display. The recommended way to run on an EC2 instance is with Isaac Sim headless mode and livestream using WebSocket.

1 Like

Should Isaac Sim (Headless WebSocket) be installed using the Omniverse launcher? I do not see it pop up in the Exchange tab when I search for Isaac.

It seems like it is supposed to be selected in this Launcher window, but the window never loads and crashes immediately.

When you run Isaac Sim for the first time, an Isaac Sim App Launcher should pop up and you can select Websocket mode. This may or may not work.

It is recommended to run Isaac Sim using containers on EC2. See Native Workstation Deployment — Omniverse Robotics documentation

1 Like

I have restarted my install process following these instructions from NVIDIA..

The EC2 instance is using this community AMI as suggested in the above documentation: IsaacSim-Ubuntu-18.04-GPU-2021-05-25

This has the same hardware setup as the original.

Unfortunately when I try to install & run the docker image it hangs. Here is the command that it fails on:

sudo docker run --gpus all -e “ACCEPT_EULA=Y” --rm --network=host -v ~/docker/isaac-sim/documents:/root/Documents:rw -v ~/docker/isaac-sim/cache:/root/.cache/ov:rw -v ~/docker/isaac-sim/logs:/root/.nvidia-omniverse/logs:rw -v ~/docker/isaac-sim/data:/root/.local/share/ov/data:rw nvcr.io/nvidia/isaac-sim:2021.1.1

Hang Location:

2021-11-16 20:39:24 [101,365ms] [Info] [carb.python] Handle changed 2 prims for layer anon:0xd093630:World0.usd.
2021-11-16 20:39:24 [101,366ms] [Info] [carb.python] Load prim spec tree rooted from /World
2021-11-16 20:39:24 [101,366ms] [Info] [carb.python] Handle changed prims for layer anon:0xd093630:World0.usd done.
2021-11-16 20:39:24 [101,366ms] [Info] [carb.python] Handle changed 4 prims for layer aIsaac Sim Headless Websocket App is loaded.
Checking for Isaac Sim assets on nucleus server

Should I have installed anything else on the instance before the Isaac container? There is nothing else currently on it.

Looks like the app is loaded but may hang when looking for the assets on Nucleus.

You can install Nucleus on the EC2 instance. Native Workstation Deployment — Omniverse Robotics documentation

I have followed these directions. I have uploaded the nucleus .zip file via scp and then tried to install via the
setup/nucleus-setup -i step in the instructions. It failed the first time with the error so I re-ran it and (I think) it succeeded.

ubuntu@ip:~/nucleus_installer$ setup/nucleus-setup -i
install
Error: Could not find file '/home/ubuntu/.nvidia-omniverse/config/omniverse.toml'.
AppPath /home/ubuntu/nucleus_installer/setup
ConfigPath /home/ubuntu/nucleus_installer/setup/configs
RootPath /home/ubuntu/nucleus_installer
System Monitor not found
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/Discovery Service
Killing Process - omni-discovery-service
Copying  - /home/ubuntu/nucleus_installer/setup/configs/Discovery Service/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/Discovery Service/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/Discovery Service
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/Thumbnail
Killing Process - omni-thumbnails-service
Copying  - /home/ubuntu/nucleus_installer/setup/configs/Thumbnail/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/Thumbnail/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/Thumbnail
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/Search Service
Killing Process - omni-search-service
Copying  - /home/ubuntu/nucleus_installer/setup/configs/Search Service/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/Search Service/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/Search Service
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/Snapshot
Killing Process - omni-snapshot-service
Copying  - /home/ubuntu/nucleus_installer/setup/configs/Snapshot/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/Snapshot/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/Snapshot
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/Auth
Killing Process - omni-auth-service
Copying  - /home/ubuntu/nucleus_installer/setup/configs/Auth/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/Auth/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/Auth
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/Web
Killing Process - omni-web-service
Copying  - /home/ubuntu/nucleus_installer/setup/configs/Web/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/Web/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/Web
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/System Monitor
Killing Process - omni-system-monitor
Copying  - /home/ubuntu/nucleus_installer/setup/configs/System Monitor/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/System Monitor/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/System Monitor
config.toml found, copying to /home/ubuntu/.nvidia-omniverse/config/System Monitor/config.toml
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/Nucleus
Killing Process - omni.server.app
Copying  - /home/ubuntu/nucleus_installer/setup/configs/Nucleus/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/Nucleus/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/Nucleus
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/Tagging Service
Killing Process - omni-tagging-service
Copying  - /home/ubuntu/nucleus_installer/setup/configs/Tagging Service/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/Tagging Service/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/Tagging Service
Starting System Monitor: /home/ubuntu/nucleus_installer/System Monitor/omni-system-monitor

When the nucleus install succeeded it produced this result:

ubuntu@ip:~/nucleus_installer$ setup/nucleus-setup -i
install
AppPath /home/ubuntu/nucleus_installer/setup
ConfigPath /home/ubuntu/nucleus_installer/setup/configs
RootPath /home/ubuntu/nucleus_installer
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/Discovery Service
Killing Process - omni-discovery-service
Deleting existing - /home/ubuntu/.nvidia-omniverse/config/Discovery Service/Omniverse.toml
Copying  - /home/ubuntu/nucleus_installer/setup/configs/Discovery Service/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/Discovery Service/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/Discovery Service
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/Thumbnail
Killing Process - omni-thumbnails-service
Deleting existing - /home/ubuntu/.nvidia-omniverse/config/Thumbnail/Omniverse.toml
Copying  - /home/ubuntu/nucleus_installer/setup/configs/Thumbnail/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/Thumbnail/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/Thumbnail
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/Search Service
Killing Process - omni-search-service
Deleting existing - /home/ubuntu/.nvidia-omniverse/config/Search Service/Omniverse.toml
Copying  - /home/ubuntu/nucleus_installer/setup/configs/Search Service/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/Search Service/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/Search Service
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/Snapshot
Killing Process - omni-snapshot-service
Deleting existing - /home/ubuntu/.nvidia-omniverse/config/Snapshot/Omniverse.toml
Copying  - /home/ubuntu/nucleus_installer/setup/configs/Snapshot/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/Snapshot/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/Snapshot
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/Auth
Killing Process - omni-auth-service
Deleting existing - /home/ubuntu/.nvidia-omniverse/config/Auth/Omniverse.toml
Copying  - /home/ubuntu/nucleus_installer/setup/configs/Auth/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/Auth/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/Auth
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/Web
Killing Process - omni-web-service
Deleting existing - /home/ubuntu/.nvidia-omniverse/config/Web/Omniverse.toml
Copying  - /home/ubuntu/nucleus_installer/setup/configs/Web/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/Web/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/Web
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/System Monitor
Killing Process - omni-system-monitor
Deleting existing - /home/ubuntu/.nvidia-omniverse/config/System Monitor/Omniverse.toml
Copying  - /home/ubuntu/nucleus_installer/setup/configs/System Monitor/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/System Monitor/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/System Monitor
config.toml found, copying to /home/ubuntu/.nvidia-omniverse/config/System Monitor/config.toml
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/Nucleus
Killing Process - omni.server.app
Deleting existing - /home/ubuntu/.nvidia-omniverse/config/Nucleus/Omniverse.toml
Copying  - /home/ubuntu/nucleus_installer/setup/configs/Nucleus/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/Nucleus/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/Nucleus
UpdateComponentToml - /home/ubuntu/nucleus_installer/setup/configs/Tagging Service
Killing Process - omni-tagging-service
Deleting existing - /home/ubuntu/.nvidia-omniverse/config/Tagging Service/Omniverse.toml
Copying  - /home/ubuntu/nucleus_installer/setup/configs/Tagging Service/Omniverse.toml to /home/ubuntu/.nvidia-omniverse/config/Tagging Service/Omniverse.toml
Setting InstallDir - /home/ubuntu/nucleus_installer/Tagging Service
Starting System Monitor: /home/ubuntu/nucleus_installer/System Monitor/omni-system-monitor

Unfortunately, when I run the original Headless Isaac installation docker command I get this error now:

ubuntu@ip:~$ sudo docker login nvcr.io
Authenticating with existing credentials...
WARNING! Your password will be stored unencrypted in /home/ubuntu/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store

Login Succeeded
ubuntu@:~$ sudo docker run --gpus all -e "ACCEPT_EULA=Y" --rm --network=host -v ~/docker/isaac-sim/documents:/root/Documents:rw -v ~/docker/isaac-sim/cache:/root/.cache/ov:rw -v ~/docker/isaac-sim/logs:/root/.nvidia-omniverse/logs:rw -v ~/docker/isaac-sim/data:/root/.local/share/ov/data:rw nvcr.io/nvidia/isaac-sim:2021.1.1
docker: Error response from daemon: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: Running hook #0:: error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization error: nvml error: driver not loaded: unknown.
ubuntu@ip:~$ sudo docker ps
CONTAINER ID   IMAGE     COMMAND   CREATED   STATUS    PORTS     NAMES

Next I thoroughly deleted the half built docker image and container just to run it again and get the same error:

a2016a6ce947: Pull complete                                                                                                                                                                                                    0e566ff3e71c: Pull complete                                                                                                                                                                                                    Digest: sha256:1d4bc215354ca1e47223bad3d4323b8d19f3867d9a18abb332d37f838ab367f2
Status: Downloaded newer image for nvcr.io/nvidia/isaac-sim:2021.1.1
docker: Error response from daemon: OCI runtime create failed: container_linux.go:367: starting container process caused: process_linux.go:495: container init caused: Running hook #0:: error running hook: exit status 1, stdout: , stderr: nvidia-container-cli: initialization error: nvml error: driver not loaded: unknown.

There may be an issue with the drivers. This may happen after an update. Please try running nvidia-smi to check if the drivers are working.
You can reinstall the drivers if nvidia-smi failes. Download the .run drivers via wget.

For others who run into this issue:
I started from scratch and discovered that before running setup/nucleus-setup -i there are nvidia drivers and no issues. After running that command there nvidia-smi doesnt work because it cant find nvidia.

ubuntu@ip-10-85-153-189:~/nucleus_installer$ sudo nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.

So then I ran sudo apt install nvidia-driver-460 since that is what the instance had originally. Then I re-ran the docker command. Now it is sitting on a new line:

2021-11-18 15:50:20 [129,782ms] [Info] [carb.python] [py stdout]: Checking for Isaac Sim assets on nucleus server

2021-11-18 15:50:20 [129,795ms] [Warning] [carb.python] default server omniverse://localhost does not have /Isaac folder
2021-11-18 15:50:20 [129,795ms] [Warning] [carb.python] /isaac/nucleus/default not specified in json config or via --/isaac/nucleus/default="omniverse://my-nucleus-server" command line
2021-11-18 15:50:20 [129,795ms] [Warning] [carb.python] Attempting to locate server from previously saved servers...
2021-11-18 15:50:20 [129,795ms] [Info] [carb.settings.python] ISettings.get(...) was called on element that has no value (from python). Use set_default(...) before to set default value. (path = '/persistent/app/omniverse/savedServers')
2021-11-18 15:50:20 [129,795ms] [Warning] [carb.python] /persistent/app/omniverse/savedServers setting not found
2021-11-18 15:50:20 [129,795ms] [Info] [carb.python] Testing omniverse://localhost Server for /Isaac folder
2021-11-18 15:50:20 [129,795ms] [Warning] [carb.python] Server omniverse://localhost does not have /Isaac folder
2

Was I supposed to pre-configure nucleus somehow?

Hi @altimm doesn’t seem that the instance is crashing anymore right?
You should be able to access it now via one of the Livestream Clients. If you followed the default instructions you are likely using the Websocket

The logs also indicate that you have not added the Isaac asset folder. Did you do that after you install Nucleus? Check instructions here Adding Sample Assets to Headless Nucleus

I had not followed those instructions when I made original post. Since then, I did find and follow those instructions but I get an error. Unfortunately I did not take a screenshot.

Was this nucleus issue solved in Isaac 2021.2.0? I noticed that it listed these services as coming pre-installed.

I ran the new 2021.2.0 docker file using this command:

sudo docker run --gpus all -e "ACCEPT_EULA=Y" --rm --network=host -v ~/docker/isaac-sim/documents:/root/Documents:rw -v ~/docker/isaac-sim/cache:/root/.cache/ov:rw -v ~/docker/isaac-sim/logs:/root/.nvidia-omniverse/logs:rw -v ~/docker/isaac-sim/data:/root/.local/share/ov/data:rw nvcr.io/nvidia/isaac-sim:2021.2.0

It has stopped on this output:

A few errors and warnings occurred before this so I am unsure if this is an intended outcome or something is broken. Trying to connect to the websocket in my local browser does not work but I expect that since this is an EC2 instance I have some networking/permissions issues to work out before that works.

In conclusion: Is Omniverse System Monitor with Nucleus and Cache started a success state or an intermediate step?

Hi, that output looks correct. Isaac Sim should start after that line. I would recommend following the steps here: 3. Advanced Installation — Omniverse Robotics documentation

See 6. Setup FAQ — Omniverse Robotics documentation if you have issues with starting Nucleus.

@altimm you can check if your Nucleus and Cache are running by going to http://<ip_address_of_instance>:8080 (Nucleus) or http://<ip_address_of_instance>:3080 (see all services that are running, including Cache)

After Nucleus is setup you can proceed to run Isaac SIM:

./isaac-sim.headless.websocket.sh --allow-root

It should startup in headless mode. Once it is ready it will output something like “Isaac Sim Headless Websocket App is loaded.”

After this step, you can connect via browser on http://<ip_address_of_instance>:8211/streaming/client