Upgrading repository problem

Deadline
1

We have repository 10.0.24.1 installed and running on CentOS 7.6.1810. x64. I’ve been trying to upgrade it to 10.0.28.4 (Deadline-10.0.28.2-linux-installers) however the repository would remain 10.0.24. I suspect I may be stopping the wrong service which is why it doesn’t get upgraded properly?

ps -ef | grep deadline

result

root      3479  4025 91 13:48 ?        00:00:01 /opt/Thinkbox/Deadline10/bin/mono --runtime=v4.0 --config /opt/Thinkbox/Deadline10/bin/deadline_mono_config /opt/Thinkbox/Deadline10/bin/deadlinecommand.exe -ExecuteScriptNoGui /opt/Thinkbox/AWSPortalLink/GetTunnelParams.py /var/log/Thinkbox/AWSPortalLink/AWSPortalLink-ptaren07-2019-09-20-0000.log
render    3505  3381  0 13:48 pts/0    00:00:00 grep --color=auto deadline
root      4462  4025  3 Sep20 ?        02:23:29 /opt/Thinkbox/Deadline10/bin/mono --runtime=v4.0 --config /opt/Thinkbox/Deadline10/bin/deadline_mono_config /opt/Thinkbox/Deadline10/bin/deadlinercs.exe --port 5846 --incognito --local_only
render    4477     1  2 Sep20 ?        01:34:55 /opt/Thinkbox/Deadline10/bin/mono --runtime=v4.0 --config /opt/Thinkbox/Deadline10/bin/deadline_mono_config /opt/Thinkbox/Deadline10/bin/deadlinelauncher.exe -daemon -nogui

None of those looks like the correct daemon I need to stop? Expecting something about DeadlineDatabase process?

2

ps -ef | grep mongo
if the service has stopped then you shouldnt have a mongod service running.
We also disable all the slaves on the farm , so there are nothing rendering, just to be safe.

If kill the launcher and its sub processes just to be safe.

As long as you install the repository location to that same place that all the workers (slaves) are pointing to then it should just work.
then in <repo path>/settings/repository.ini will have its version flag updated to the new version.

hope that helps.
kym