Logs
Numerous logs are available that are useful for troubleshooting.
Viewing Logs using the CLI
OpCenter compiles logs of events related to its operation as well as logs that are specific to a particular job or a particular host (worker node).
To see the logs that pertain to the operation of the OpCenter, enter the following:
$ float log ls
+---------------------------------------------+----------+----------------------+
| LOG NAME | SIZE | LAST UPDATE TIME |
+---------------------------------------------+----------+----------------------+
| mmcon-0.log | 190 | 2025-06-21T16:24:20Z |
| opcenter.access_log | 273087 | 2025-07-11T15:51:11Z |
| opcenter.log | 4484104 | 2025-07-11T15:24:37Z |
| rsc_cleanup.log | 7886 | 2025-07-10T16:25:37Z |
| upgrade.log | 2368 | 2025-06-21T16:24:24Z |
| messages | 765566 | 2025-07-11T15:39:03Z |
+---------------------------------------------+----------+----------------------+
The log called opcenter.logcaptures all job-related events, for example, selecting an instance, starting an instance, loading the container image, and so on. This log also captures interactions between the OpCenter and the license portal.
To view the content of a log, enter float log cat <log_name>. Combine with linux commands to view a section at a time or to direct the output to a file, for example:
To see the logs that pertain to a particular job, enter the following:
Example:
$ float log ls -j TQ9PUJhoY0XLtL58KcU1M
+--------------------------+-------+----------------------+
| LOG NAME | SIZE | LAST UPDATE TIME |
+--------------------------+-------+----------------------+
| environments | 330 | 2023-02-02T02:21:04Z |
| job.events | 3009 | 2023-02-02T02:27:02Z |
| metrics-a1e1970a868a.txt | 12232 | 2023-02-02T02:46:35Z |
| output | 25963 | 2023-02-02T02:46:40Z |
| stderr.autosave | 0 | 2023-02-02T02:21:27Z |
| stdout.autosave | 0 | 2023-02-02T02:21:27Z |
+--------------------------+-------+----------------------+
The job script used to submit this job redirects stderr and stdout to a file called output (that is why stderr.autosave and stdout.autosave have zero size). The log called job.events is useful for troubleshooting.
To see the logs that pertain to a particular host, enter the following:
Example:
$ float log ls -i i-0e40db7d105cb6793
+-------------------+--------+----------------------+
| LOG NAME | SIZE | LAST UPDATE TIME |
+-------------------+--------+----------------------+
| fagent.access_log | 8494 | 2023-02-02T17:10:10Z |
| fagent.log | 11735 | 2023-02-02T17:08:00Z |
| fagent_init.log | 639 | 2023-02-02T17:06:34Z |
| internal_output | 1116 | 2023-02-02T17:07:59Z |
| messages | 154889 | 2023-02-02T17:10:01Z |
+-------------------+--------+----------------------+
The log called messages is useful for troubleshooting. The log called fagent.log records interactions between the worker node and the OpCenter.
Viewing Logs using the Web Interface
To use the OpCenter web interface, open a browser and go to the public (if you are outside the VPC) or private (if you are inside the VPC) IP address associated with the OpCenter. Enter your credentials at the login screen.
To view OpCenter logs, complete the following steps.
- From any screen, click the OpCenter icon at the top, right-hand side.
- Select the Logs tab.
- To download a log, click the Download icon.
- To view a log, click the Preview icon.
To view logs associated with a particular job, complete the following steps.
- From the left-hand panel, click Jobs.
- On the Jobs screen, click the ID of the job whose logs you want to view.
- Click the Attachments tab to display the available logs.
To download a log bundle associated with a particular job, complete the following steps.
- From the left-hand panel, click Jobs.
- On the Jobs screen, click the ID of the job of interest.
- On the right-hand side of job screen, click the Download Log Bundle.
- In the pop-up window, check the boxes next to the logs to include in the bundle.
- Click Download.