search

aws-deadline / deadline-cloud-for-cinema-4d

AWS Deadline Cloud for Cinema 4D
Apache License 2.0
8 stars 10 forks source link

Bug: Some application errors ( C4d / redshift) are not bubbled up to logs making triage hard. #83

Open andymanaws opened 1 week ago

andymanaws commented 1 week ago

Expected Behaviour

If possible, the actual failure from the application should be echoed in the logs if possible, so that the cause of the issue can be determined more quickly.

If this error is reported, by the time escalation happens to IT, the fleet might have been scaled down and the underlying application logs living on the instance lost.

Current Behaviour

Currently we are presented with just an openjd_fail:

openjd_ fail: Error encountered while running adaptor: Cinema4D exited early and did not nder successfully, please check render logs. Exit code XXXXXXX

Reproduction Steps

We suspect this happen with a resource starvation issue - will update once we can reproduce and get the logs off the spot instance before it shuts down.

Code Snippet

N?A

karthikbekalp commented 1 week ago

Hmm, interesting. Ideally the render logs should contain the errors before this line gets printed. For example, in this issue we had a few errors after which openjd_ fail: Error encountered while running adaptor: Cinema4D ... line is printed.

Is it possible to share the worker/session logs to understand the root cause?