Hello.
spot after completing the plugin configuration, the machines start up, but why are they not connecting within the deadline?
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)