search

AcademySoftwareFoundation / OpenCue

A render management system you can deploy for visual effects and animation productions.
https://www.opencue.io
Apache License 2.0
832 stars 202 forks source link

No layer logfile on Windows #1258

Open nyqvistatwork opened 1 year ago

nyqvistatwork commented 1 year ago

Describe the bug After submitting a job Cuetopia says "Log file does not exist:" when activating a layer.

To Reproduce Steps to reproduce the behavior:

  1. Send a job on Windows I guess

Expected behavior A logfile should be created even if empty.

Screenshots image

Version Number 5.12.2

Additional context Window 11 environment. All OpenCue components where installed from published release on the local computer. No Docker. Cuebot was started with the following commandline: java -jar c:\opencue\cuebot\cuebot-0.21.13-all.jar --datasource.cue-data-source.jdbc-url=jdbc:postgresql://localhost/cuebot_local --datasource.cue-data-source.username=cuebot --datasource.cue-data-source.password=***** --log.frame-log-root.default_os="c:\opencue\logs"

nyqvistatwork commented 1 year ago

Is this expected behavior when the job is not started? I find it confusing. 😶 I would prefer to have a log file to view when the job is created.

bcipriano commented 1 year ago

Reposting here some info from our email thread for completeness, and maybe it will be helpful to people in the future.

The log file gets created when the frame is launched on RQD. So if the frame was never launched, it's expected for there to be no log file yet.

There are two possible causes here:

  1. Cuebot never scheduled the frame on an RQD host. This can happen because:
    1. Cuebot thinks there's no appropriate RQD host to send the work to -- see Troubleshooting rendering for some possible causes there.
    2. Cuebot is unable to reach the RQD host due to some networking issue. This can happen even if Cuebot/RQD are running on the same machine, if something like Windows firewall is preventing software from sending requests.
  2. The frame WAS scheduled, but RQD encountered some error during frame startup that prevented the frame from launching properly. In this case, RQD logs should show more information about what error occurred.

A good next step here is to look at the RQD logs -- this can help determine which of the above scenarios is occurring in your case. If RQD isn't showing any activity, it's probably (1). If RQD is showing activity/errors, it's probably (2).

Ultimately, you're right that this error is not providing much information and could be improved.

nyqvistatwork commented 1 year ago

I must find the logging of cuebot a little confusing 😶 Where and what are the RQD logs? Is it what Troubleshooting rendering calls "Frame logs"? When RQD is trying to perform an action (outside of layer scope), is this is logged somewhere?

bcipriano commented 1 year ago

Sorry yeah, RQD logs to stdout, so if you're running in a terminal it should print output to that terminal. If you're running in Docker, docker logs <rqd container name> will show them.

The RQD logs are showing you what RQD is doing, outside of any specific render task. These are distinct from the "frame logs", which contain the output from a single frame task.