Unable to start docker compose of Enterprise Nucleus Server

Omniverse Platform Nucleus
1

I can’t start docker compose of Enterprise Nucleus Server.
How can I start it?

I followed the Quick Start Tips.
https://docs.omniverse.nvidia.com/nucleus/latest/enterprise/installation/quick_start_tips.html

But I saw loop as below and it didn’t seem to progress further.
e[32;1mnucleus-log-processor_1 |e[0m Deleting /omni/log/api/Access_OLD.log
e[32;1mnucleus-log-processor_1 |e[0m Deleting debug copy /omni/log/api/debug/Access.log.2023-09-17-05-59-53
e[32;1mnucleus-log-processor_1 |e[0m Processing LFT Server logs
e[32;1mnucleus-log-processor_1 |e[0m /omni/log/lft/access.log is not there: nothing to process, skipping
e[33mtagging-logrotate_1 |e[0m crond: USER root pid 14 cmd /usr/sbin/logrotate /etc/logrotate.conf
e[36mnucleus-api_1 |e[0m [MON] Checking blacklist
e[36mnucleus-api_1 |e[0m [MON] > blacklist not found
e[32;1mnucleus-log-processor_1 |e[0m Processing API Server logs
e[32;1mnucleus-log-processor_1 |e[0m Detaching log /omni/log/api/Access.log…
e[32;1mnucleus-log-processor_1 |e[0m > /omni/log/api/Access_OLD.log
e[32;1mnucleus-log-processor_1 |e[0m Launching API detach log command
e[32;1mnucleus-log-processor_1 |e[0m /usr/bin/python3.10 /omni/log_processor/detach_api_log.py -s nucleus-api -p 3006
e[32;1mnucleus-log-processor_1 |e[0m > attempting to connect to ws://nucleus-api:3006
e[32;1mnucleus-log-processor_1 |e[0m > detaching API log
e[32;1mnucleus-log-processor_1 |e[0m > log detached, sleeping 1 second
e[32;1mnucleus-log-processor_1 |e[0m > done
e[32;1mnucleus-log-processor_1 |e[0m > copying /omni/log/api/Access_OLD.log to have it in event of a crash
e[32;1mnucleus-log-processor_1 |e[0m > dest: /omni/log/api/debug/Access.log.2023-09-17-06-00-23
e[32;1mnucleus-log-processor_1 |e[0m > processing records from: /omni/log/api/Access_OLD.log
e[32;1mnucleus-log-processor_1 |e[0m > writing to : /omni/log/api/Access.log.current
e[32;1mnucleus-log-processor_1 |e[0m > processed 17 lines
e[32;1mnucleus-log-processor_1 |e[0m Deleting /omni/log/api/Access_OLD.log
e[32;1mnucleus-log-processor_1 |e[0m Deleting debug copy /omni/log/api/debug/Access.log.2023-09-17-06-00-23
e[32;1mnucleus-log-processor_1 |e[0m Processing LFT Server logs
e[32;1mnucleus-log-processor_1 |e[0m /omni/log/lft/access.log is not there: nothing to process, skipping
e[32;1mnucleus-log-processor_1 |e[0m Processing API Server logs
e[32;1mnucleus-log-processor_1 |e[0m Detaching log /omni/log/api/Access.log…
e[32;1mnucleus-log-processor_1 |e[0m > /omni/log/api/Access_OLD.log
e[32;1mnucleus-log-processor_1 |e[0m Launching API detach log command
e[32;1mnucleus-log-processor_1 |e[0m /usr/bin/python3.10 /omni/log_processor/detach_api_log.py -s nucleus-api -p 3006
e[32;1mnucleus-log-processor_1 |e[0m > attempting to connect to ws://nucleus-api:3006
e[32;1mnucleus-log-processor_1 |e[0m > detaching API log
e[32;1mnucleus-log-processor_1 |e[0m > log detached, sleeping 1 second
e[32;1mnucleus-log-processor_1 |e[0m > done
e[32;1mnucleus-log-processor_1 |e[0m > copying /omni/log/api/Access_OLD.log to have it in event of a crash
e[32;1mnucleus-log-processor_1 |e[0m > dest: /omni/log/api/debug/Access.log.2023-09-17-06-00-53
e[32;1mnucleus-log-processor_1 |e[0m > processing records from: /omni/log/api/Access_OLD.log
e[32;1mnucleus-log-processor_1 |e[0m > writing to : /omni/log/api/Access.log.current
e[32;1mnucleus-log-processor_1 |e[0m > processed 17 lines
e[32;1mnucleus-log-processor_1 |e[0m Deleting /omni/log/api/Access_OLD.log
e[32;1mnucleus-log-processor_1 |e[0m Deleting debug copy /omni/log/api/debug/Access.log.2023-09-17-06-00-53
…

I attached the full log of docker compose up command.

I found same phenomenon in multiple environments.
The information of environment I have now is below.
OS: Ubuntu 22.04
Driver Version: 525.125.06
Docker Version: 24.0.6
Docker Compose Version: 1.29.2
Python3 Version:3.10.12
GPU: Geforce RTX4090

Best regards,
ove_log.txt (30.2 MB)

2

@masaki_yamagishi i am just another OV user, but i believe users of enterprise version of OV should have access to the enterprise tech support in addition to the public forum (should you need it) - Omniverse Enterprise Technical Support | NVIDIA.

3

Hi @masaki_yamagishi. You may have a misconfiguration within your nucleus-stack.env configuration file. Can you please PM me with your information and I will reach out to you directly?

Hi @Simplychenable - You are mostly correct - Registered customers do have access to Enterprise Support, however there are some customers that have access to the Enterprise version of the software but are in trials or other programs that do not qualify for Enterprise Support.

4

@dcomo ah, thanks for the clarification and correction, Drew! i’ll keep that in mind for future reference.

5

No worries at all @Simplychenable. It can definitely get confusing for sure!

6

Thank you for your replying, @Simplychenable @dcomo .

@dcomo , I sent a message describes my env file.
I’d appreciate it if you could check and correct it.

Best regards,