Hello friends, today I am configuring the spot event plugin, but I am stuck in the launch template. Why can’t I create a template here?
I created a template in the AWS section but I’m still stuck here.
That should work - if you look in the Monitor’s log are there any errors in there? Maybe the config utility isn’t logging into AWS properly.
The logs will be on the machine in one of these locations and named deadlinemonitor:
Windows: C:\ProgramData\Thinkbox\Deadline10\logs
Linux: /var/log/Thinkbox/Deadline10
Mac OS X: /Library/Logs/Thinkbox/Deadline10
I looked into it but I didn’t understand what the problem was.
2024-02-23 19:48:35: BEGIN - EC2AMAZ-ODAJ6B0\Administrator
2024-02-23 19:48:35: Operating System: Windows Server 2016 Datacenter
2024-02-23 19:48:35: CPU Architecture: x64
2024-02-23 19:48:35: CPUs: 4
2024-02-23 19:48:35: Video Card: Microsoft Basic Display Adapter
2024-02-23 19:48:35: Deadline Monitor 10.3 [v10.3.1.3 Release (2807fcb2a)]
2024-02-23 19:48:35: Time to initialize: 94.000 ms
2024-02-23 19:48:39: Auto Configuration: No auto configuration for Repository Path could be detected, using local configuration
2024-02-23 19:48:40: Auto Configuration: Picking configuration based on: EC2AMAZ-ODAJ6B0 / 1.1.1.1
2024-02-23 19:48:40: Auto Configuration: No auto configuration could be detected, using local configuration
2024-02-23 19:48:40: Time to connect to Repository: 1.094 s
2024-02-23 19:48:40: Time to check user account: 0.000 s
2024-02-23 19:48:40: Time to purge old logs and temp files: 0.000 s
2024-02-23 19:48:40: Time to synchronize plugin icons: 94.000 ms
2024-02-23 19:48:41: WARNING: Current user does not have permission to spawn a ‘DashListWidget’ panel.
2024-02-23 19:48:41: Time to initialize main window: 719.000 ms
2024-02-23 19:48:41: Main Window shown
2024-02-23 19:48:41: Python 3.10.13 | packaged by Thinkbox Software | (main, Nov 23 2023, 08:14:16) [MSC v.1933 64 bit (AMD64)]
2024-02-23 19:48:41: Time to show main window: 78.000 ms
2024-02-23 19:48:41: AWS Resource Status: All AWS Fleets are in a healthy state.
2024-02-23 19:49:46: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-02-23 19:50:00: Running script SpotEventConfigurationUtil (C:\DeadlineRepository10\scripts\General\SpotEventConfigurationUtil.py)
2024-02-23 19:53:42: PYTHON: None
2024-02-23 19:53:44: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-02-23 19:54:39: PYTHON: No Launch Templates selected.
2024-02-23 19:56:09: Fetched bucket region us-east-1
2024-02-23 19:57:21: Fetched bucket region us-east-1
2024-02-23 19:58:40: Starting Deadline AWS Resource Tracker
2024-02-23 19:58:40: Deadline AWS Resource Tracker Stack Already Exists.
2024-02-23 19:58:40: Updating the Deadline AWS Resource Tracker
2024-02-23 19:58:40: The Deadline AWS Resource Tracker Stack is already at the given version.
2024-02-23 19:58:44: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-02-23 19:59:00: Using the official ReverseDash.template
2024-02-23 19:59:01: Using the official ReverseDash.template
2024-02-23 20:01:43: Using the official PrivateSubnet.template
2024-02-23 20:01:43: Using the official PrivateSubnet.template
2024-02-23 20:01:43: Using the official PrivateSubnet.template
2024-02-23 20:01:44: Using the official PrivateSubnet.template
2024-02-23 20:01:44: Using the official PrivateSubnet.template
2024-02-23 20:01:44: Using the official PrivateSubnet.template
2024-02-23 20:01:45: The specified log group already exists
2024-02-23 20:01:45: The specified log group already exists
2024-02-23 20:01:45: The specified log group already exists
2024-02-23 20:05:00: Running script SpotEventConfigurationUtil (C:\DeadlineRepository10\scripts\General\SpotEventConfigurationUtil.py)
2024-02-23 20:06:03: PYTHON: No Launch Templates selected.
Silly Question! @naeim_akbari
Are you logged into the same region where the Launch template exists? In the Monitor logs it says PYTHON: No Launch Templates selected. which makes me think may be you have a different region where it lives?
Yes, as you said, it didn’t work because I created a template in another region, but now spot fleet machines are not starting automatic as we specified.
Where could the problem be?
deadline monitor logs
2024-03-03 00:05:59: BEGIN - EC2AMAZ-ODAJ6B0\Administrator
2024-03-03 00:05:59: Operating System: Windows Server 2016 Datacenter
2024-03-03 00:05:59: CPU Architecture: x64
2024-03-03 00:05:59: CPUs: 4
2024-03-03 00:05:59: Video Card: Microsoft Basic Display Adapter
2024-03-03 00:05:59: Deadline Monitor 10.3 [v10.3.1.3 Release (2807fcb2a)]
2024-03-03 00:05:59: Time to initialize: 93.000 ms
2024-03-03 00:06:08: Auto Configuration: No auto configuration for Repository Path could be detected, using local configuration
2024-03-03 00:06:09: Auto Configuration: Picking configuration based on: EC2AMAZ-ODAJ6B0 /
2024-03-03 00:06:09: Auto Configuration: No auto configuration could be detected, using local configuration
2024-03-03 00:06:09: Time to connect to Repository: 1.109 s
2024-03-03 00:06:09: Time to check user account: 0.000 s
2024-03-03 00:06:09: Time to purge old logs and temp files: 0.000 s
2024-03-03 00:06:10: Time to synchronize plugin icons: 672.000 ms
2024-03-03 00:06:10: WARNING: Current user does not have permission to spawn a ‘DashListWidget’ panel.
2024-03-03 00:06:11: Time to initialize main window: 687.000 ms
2024-03-03 00:06:11: Main Window shown
2024-03-03 00:06:11: Python 3.10.13 | packaged by Thinkbox Software | (main, Nov 23 2023, 08:14:16) [MSC v.1933 64 bit (AMD64)]
2024-03-03 00:06:11: Time to show main window: 62.000 ms
2024-03-03 00:11:12: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 00:16:12: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 00:17:41: AWS Resource Status: All AWS Fleets are in a healthy state.
2024-03-03 00:26:13: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 00:33:28: AWS Resource Status: The following AWS Fleets have been observed to be in an unhealthy state:
2024-03-03 00:33:28: Region us-east-1:
2024-03-03 00:33:28: Spot Fleet ID: sfr-e8072945-14b1-4df9-ba56-ee6107c407d8
2024-03-03 00:36:13: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 00:43:43: AWS Resource Status: The following AWS Fleets have been observed to be in an unhealthy state:
2024-03-03 00:43:43: Region us-east-1:
2024-03-03 00:43:43: Spot Fleet ID: sfr-659214a6-d5ba-4c5f-a73f-5623e61d1a0f
2024-03-03 00:43:43: Spot Fleet ID: sfr-e8072945-14b1-4df9-ba56-ee6107c407d8
2024-03-03 00:46:13: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 14:01:21: Fleet Health Publisher: Published fleet health data for region us-east-1
2024-03-03 14:01:21: The unhealthy AWS Fleets have been successfully cleared from the US East (N. Virginia) (us-east-1) region. You can now create new fleets or increase fleet capacity like normal.
2024-03-03 14:08:06: AWS Resource Status: All AWS Fleets are in a healthy state.
2024-03-03 14:34:56: Running script SpotEventConfigurationUtil (C:\DeadlineRepository10\scripts\General\SpotEventConfigurationUtil.py)
2024-03-03 14:36:05: Fetched bucket region us-east-1
2024-03-03 14:36:16: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 14:36:19: Starting Deadline AWS Resource Tracker
2024-03-03 14:36:19: Deadline AWS Resource Tracker Stack Already Exists.
2024-03-03 14:36:19: Updating the Deadline AWS Resource Tracker
2024-03-03 14:36:19: The Deadline AWS Resource Tracker Stack is already at the given version.
2024-03-03 14:36:39: Using the official ReverseDash.template
2024-03-03 14:36:40: Using the official ReverseDash.template
2024-03-03 14:39:06: Using the official PrivateSubnet.template
2024-03-03 14:39:06: Using the official PrivateSubnet.template
2024-03-03 14:39:06: Using the official PrivateSubnet.template
2024-03-03 14:39:07: Using the official PrivateSubnet.template
2024-03-03 14:39:07: Using the official PrivateSubnet.template
2024-03-03 14:39:07: Using the official PrivateSubnet.template
2024-03-03 14:39:08: The specified log group already exists
2024-03-03 14:39:08: The specified log group already exists
2024-03-03 14:39:08: The specified log group already exists
2024-03-03 14:41:16: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 14:41:21: Running script SpotEventConfigurationUtil (C:\DeadlineRepository10\scripts\General\SpotEventConfigurationUtil.py)
2024-03-03 14:42:38: Running script SpotEventConfigurationUtil (C:\DeadlineRepository10\scripts\General\SpotEventConfigurationUtil.py)
2024-03-03 14:49:30: Running script SpotEventConfigurationUtil (C:\DeadlineRepository10\scripts\General\SpotEventConfigurationUtil.py)
2024-03-03 14:51:17: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 14:52:09: Running script SpotEventConfigurationUtil (C:\DeadlineRepository10\scripts\General\SpotEventConfigurationUtil.py)
2024-03-03 14:54:34: Running script SpotEventConfigurationUtil (C:\DeadlineRepository10\scripts\General\SpotEventConfigurationUtil.py)
2024-03-03 14:56:17: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 14:58:23: Running script SpotEventConfigurationUtil (C:\DeadlineRepository10\scripts\General\SpotEventConfigurationUtil.py)
Yes, as you said, it didn’t work because I created a template in another region, but now spot fleet machines are not starting automatic as we specified.
Where could the problem be?
But when I open it manually, it connects fine.
deadline monitor logs
2024-03-03 00:05:59: BEGIN - EC2AMAZ-ODAJ6B0\Administrator
2024-03-03 00:05:59: Operating System: Windows Server 2016 Datacenter
2024-03-03 00:05:59: CPU Architecture: x64
2024-03-03 00:05:59: CPUs: 4
2024-03-03 00:05:59: Video Card: Microsoft Basic Display Adapter
2024-03-03 00:05:59: Deadline Monitor 10.3 [v10.3.1.3 Release (2807fcb2a)]
2024-03-03 00:05:59: Time to initialize: 93.000 ms
2024-03-03 00:06:08: Auto Configuration: No auto configuration for Repository Path could be detected, using local configuration
2024-03-03 00:06:09: Auto Configuration: Picking configuration based on: EC2AMAZ-ODAJ6B0 /
2024-03-03 00:06:09: Auto Configuration: No auto configuration could be detected, using local configuration
2024-03-03 00:06:09: Time to connect to Repository: 1.109 s
2024-03-03 00:06:09: Time to check user account: 0.000 s
2024-03-03 00:06:09: Time to purge old logs and temp files: 0.000 s
2024-03-03 00:06:10: Time to synchronize plugin icons: 672.000 ms
2024-03-03 00:06:10: WARNING: Current user does not have permission to spawn a ‘DashListWidget’ panel.
2024-03-03 00:06:11: Time to initialize main window: 687.000 ms
2024-03-03 00:06:11: Main Window shown
2024-03-03 00:06:11: Python 3.10.13 | packaged by Thinkbox Software | (main, Nov 23 2023, 08:14:16) [MSC v.1933 64 bit (AMD64)]
2024-03-03 00:06:11: Time to show main window: 62.000 ms
2024-03-03 00:11:12: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 00:16:12: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 00:17:41: AWS Resource Status: All AWS Fleets are in a healthy state.
2024-03-03 00:26:13: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 00:33:28: AWS Resource Status: The following AWS Fleets have been observed to be in an unhealthy state:
2024-03-03 00:33:28: Region us-east-1:
2024-03-03 00:33:28: Spot Fleet ID: sfr-e8072945-14b1-4df9-ba56-ee6107c407d8
2024-03-03 00:36:13: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 00:43:43: AWS Resource Status: The following AWS Fleets have been observed to be in an unhealthy state:
2024-03-03 00:43:43: Region us-east-1:
2024-03-03 00:43:43: Spot Fleet ID: sfr-659214a6-d5ba-4c5f-a73f-5623e61d1a0f
2024-03-03 00:43:43: Spot Fleet ID: sfr-e8072945-14b1-4df9-ba56-ee6107c407d8
2024-03-03 00:46:13: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 14:01:21: Fleet Health Publisher: Published fleet health data for region us-east-1
2024-03-03 14:01:21: The unhealthy AWS Fleets have been successfully cleared from the US East (N. Virginia) (us-east-1) region. You can now create new fleets or increase fleet capacity like normal.
2024-03-03 14:08:06: AWS Resource Status: All AWS Fleets are in a healthy state.
2024-03-03 14:34:56: Running script SpotEventConfigurationUtil (C:\DeadlineRepository10\scripts\General\SpotEventConfigurationUtil.py)
2024-03-03 14:36:05: Fetched bucket region us-east-1
2024-03-03 14:36:16: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 14:36:19: Starting Deadline AWS Resource Tracker
2024-03-03 14:36:19: Deadline AWS Resource Tracker Stack Already Exists.
2024-03-03 14:36:19: Updating the Deadline AWS Resource Tracker
2024-03-03 14:36:19: The Deadline AWS Resource Tracker Stack is already at the given version.
2024-03-03 14:36:39: Using the official ReverseDash.template
2024-03-03 14:36:40: Using the official ReverseDash.template
2024-03-03 14:39:06: Using the official PrivateSubnet.template
2024-03-03 14:39:06: Using the official PrivateSubnet.template
2024-03-03 14:39:06: Using the official PrivateSubnet.template
2024-03-03 14:39:07: Using the official PrivateSubnet.template
2024-03-03 14:39:07: Using the official PrivateSubnet.template
2024-03-03 14:39:07: Using the official PrivateSubnet.template
2024-03-03 14:39:08: The specified log group already exists
2024-03-03 14:39:08: The specified log group already exists
2024-03-03 14:39:08: The specified log group already exists
2024-03-03 14:41:16: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 14:41:21: Running script SpotEventConfigurationUtil (C:\DeadlineRepository10\scripts\General\SpotEventConfigurationUtil.py)
2024-03-03 14:42:38: Running script SpotEventConfigurationUtil (C:\DeadlineRepository10\scripts\General\SpotEventConfigurationUtil.py)
2024-03-03 14:49:30: Running script SpotEventConfigurationUtil (C:\DeadlineRepository10\scripts\General\SpotEventConfigurationUtil.py)
2024-03-03 14:51:17: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 14:52:09: Running script SpotEventConfigurationUtil (C:\DeadlineRepository10\scripts\General\SpotEventConfigurationUtil.py)
2024-03-03 14:54:34: Running script SpotEventConfigurationUtil (C:\DeadlineRepository10\scripts\General\SpotEventConfigurationUtil.py)
2024-03-03 14:56:17: Detected modifications to event plugin Spot in the Repository, it will now be re-initialized
2024-03-03 14:58:23: Running script SpotEventConfigurationUtil (C:\DeadlineRepository10\scripts\General\SpotEventConfigurationUtil.py)