Getting a AWSPortal error output to console every minute

Deadline
1

Trying to figure out something else, I notice that the console is putting out an error on AWSPortal every minute … which is kind of annoying trying to catch anything else.

Event plugin 'AWSPortal' could not be loaded from the repository because: Error executing event plugin script "\\server-svc01\DeadlineRepository10\events\AWSPortal\AWSPortal.py": ImportError : No module named boto3 (Deadline.Events.DeadlineEventPluginException)

To be honest, I am not even sure what AWSPortal does, why I would need it or which setting to change so it doesn’t want to load that even plugin. FYI setting Tools > Configure Event Plugins > AWSPortal > Options > State to disabled does absolutely nothing.

Anyone happen to have an idea how to get rid if this issue (other than installing boto3 module on the repository server, since I don’t know what AWSPortal does, I’m hesitant to have it running ?)

2

If you do not use AWSPortal, you do not need to worry about it.
It looks like a bug that it tries to load the plugin, when it is disabled.

3

Hello @Beeldenfabriek

This issue can arise if the PYTHONHOME on the machine in question is not set to Deadline’s Python. If you are not using AWS Portal you can safely disable it from Deadline Monitor> Tools> Configure events> AWS Portal> Status: Disabled

4

Thanks @zainali .

I tried that before, and initially it looked like that didn’t do anything.
But I think it takes some time to trickle down changing that setting, because indeed, the error is no longer being printed to console now.

1 Like
5

I have the same error printed into the console and we do use the AWS Portal so I would like to resolve it. The advice above seems to say ‘ignore it if you dont use the AWS Portal’ but there is no advice for people who do use it?

6

If you are using the Portal, which version of Deadline are you running? And are you running the same version of Deadline everywhere?

Running Deadline 10.2.1.1. on both your clients and repository will take care of the issue.

7

Hi Justin,

We are running 10.2.1.1 everywhere.

Thank you

8

Interesting! Which log are you seeing this in? And are you possibly running the application with the -py-ver-2 flag? That’s not something you’d be doing by accident, so if you’re not sure you’re likely not.

The reason being that this warning is coming from not being able to import boto3 (the AWS Python module). Which should fail if you’re running Python 2, or are running a version of Deadline that’s not shipping it.

Given you’re running 10.2.1.1, was this an upgrade to 10.2.1.1 or a fresh install? If an upgrade, do you recall from which version?

And if you go into DeadlineRepository10\pythonsync3\pythonsync3.zip is there a folder for boto3?

9

I am seeing this in the Console inside Monitor.

I have no idea re py-ver-2 so likely not.

10.2.1.1 was installed fresh, I believe.

There is a boto3 folder however the DeadlineRepository10 folder doesnt have the 10 on mine, is that important?

image
image1049×751 43.7 KB

10

The 10 on DeadlineRepository10 is just what the installer uses as a default so that’s what I use in my examples - it’s not important at all.

I wonder if maybe the pythonsync process that should be pulling a copy of that pythonsync3.zip file for local use is failing.

Could I get a Monitor log to look over? That should include a mention of pythonsync for us.

11

Hi Justin,

Would you be able to assist on which log it is you need and how I can go about saving it for you?

Thank you

12

My mistake, I gotta remember to dump those paths in.

The logs will be on the machine in one of these locations:
Windows: C:\ProgramData\Thinkbox\Deadline10\logs
Linux: /var/log/Thinkbox/Deadline10
Mac OS X: /Library/Logs/Thinkbox/Deadline10

And named with deadlinemonitor-[the date]-[the number of times the Monitor has been launched].log.

13

Ah, thank you. Please find today’s monitor logs attached.
logs.zip (6.9 KB)

14

Thanks!

Looks like the local copy of pythonsync is new enough to not need a refresh, but clearly the botocore directory is missing, as that’s the import that’s failing.

We can force Deadline to pull a new copy of pythonsync by deleting what’s stored locally. On your machine that’ll be the contents of C:\Users\Ben\AppData\Local\Thinkbox\Deadline10\pythonAPIs.

Then re-open your Monitor and let me know what you see!

15

Thank you!

I think that might have sorted it.

This is what the console prints now (below).

The boto folders were actually there previously but I noticed that Windows was complaining about permissions when trying to open it. This no longer is the case.

2023-09-05 17:21:12:  Time to initialize: 265.000 ms
2023-09-05 17:21:18:  Auto Configuration: No auto configuration for Repository Path could be detected, using local configuration
2023-09-05 17:21:20:  Connecting to Deadline RCS 10.2 [v10.2.1.1 Release (094cbe890)]
2023-09-05 17:21:38:  'C:\Users\Ben\AppData\Local\Thinkbox\Deadline10\pythonAPIs\Qo2NwgwS4V5oVK3SmUn4lA==' already exists. Skipping extraction of PythonSync.
2023-09-05 17:21:39:  Auto Configuration: Picking configuration based on: ws-56core-01 / 192.168.0.20
2023-09-05 17:21:39:  Auto Configuration: No auto configuration could be detected, using local configuration
2023-09-05 17:21:39:  Time to connect to Repository: 20.484 s
2023-09-05 17:21:39:  Time to check user account: 187.000 ms
2023-09-05 17:21:39:  Time to purge old logs and temp files: 47.000 ms
2023-09-05 17:21:41:  Time to synchronize plugin icons: 1.422 s
2023-09-05 17:21:44:  Time to initialize main window: 3.625 s
2023-09-05 17:21:44:  Main Window shown
2023-09-05 17:21:44:  Python 3.7.16 | packaged by Thinkbox Software | (default, Mar  1 2023, 20:43:00) [MSC v.1933 64 bit (AMD64)]
2023-09-05 17:21:44:  Time to show main window: 110.000 ms
2023-09-05 17:21:52:  AWS Resource Status: All AWS Fleets are in a healthy state.
2023-09-05 17:21:55:  'C:\Users\Ben\AppData\Local\Thinkbox\Deadline10\pythonAPIs\Qo2NwgwS4V5oVK3SmUn4lA==' already exists. Skipping extraction of PythonSync.
1 Like
16

Interesting - the Monitor should be the application making that directory and should therefore own it. If this happens again let us know!

1 Like