Malformed paths of client configuration file (deadline.ini)

The error shows itself as a corruption of the path to the client configuration file directory in Deadline Monitor/Worker logs when the client application is connected through the RCS. The error will look something like below:

2023-08-09 06:32:57:  ERROR: DeadlineLoggerMiddleware caught exception method=POST path=/rcs/v1/assigntask remoteip=10.149.50.219 exception=System.UnauthorizedAccessException: Access to the path '/opt/Thinkbox/Deadline10/bin/:/var/spool/mail:/sbin/nologin/Thinkbox/Deadline10' is denied.

This also can cause Workers to fail to connect to the RCS and can cause job submissions to fail.

This is caused by failures to read the client configuration location when attempting to create a new file hence the wrong path is used. As a temporary workaround, you can use environment variables to define the configuration file location. Define the environment variables (DEADLINE_CONFIG_FILE, DEADLINE_LOCAL_USER_PATH ) on the RCS machine by following below:

1. Stop the RCS:
1. Open a terminal/cmd and stop the launcher or kill the RCS process
2. systemctl stop deadline10launcher << when Launcher is running as a daemon
3. pkill -9 deadlinercs do this when Launcher is not running as a daemon
2. Define the environment variables:
1. export DEADLINE_CONFIG_FILE=<path_to_deadline.ini_file>
2. export DEADLINE_LOCAL_USER_PATH=< see here for the value >

3. Start the RCS:
1. systemctl start deadline10launcher << when Launcher is running as a daemon
2. $DEADLINE_PATH/deadlinercs << when Launcher is not running as a daemon