[7:30:02 AM] - Action confirmed. Preparing to execute action.
[7:30:02 AM] - Deploying data flow component.
[7:30:02 AM] - [Step 1/4] Retrieving configuration to get current settings.
[7:30:02 AM] - [Step 1/4] Parsing configuration to extract deployment parameters.
[7:30:02 AM] - [Step 3/4] Adding new data flow component to configuration.
[7:30:02 AM] - [Step 3/4] Data flow component saved. Starting health check.
[7:30:02 AM] - [Step 4/4] Waiting for data flow component to be healthy.
[7:30:02 AM] - [Step 4/4] Initialized health check for data flow component.
[7:30:06 AM] - [Step 4/4] Waiting for data flow component to become healthy. (Current status: initializing)
[7:30:06 AM] - [Step 4/4] Waiting for data flow component to become healthy. (Current status: initializing, Last event: Deployment not found: The data flow component is scheduled for deployment, but the deployment was not yet created. This is normal during initialization or when updating the data flow component.)
[7:30:07 AM] - [Step 4/4] Waiting for data flow component to become healthy. (Current status: initializing, Last event: Pod is pending: Pod dfc-16dbfea1-7183-425e-adf3-97777a02fe78-lab-ifm-6fbf4797c6fl8g is pending, this is normal during initialization or when updating the data flow component.)
[7:30:07 AM] - [Step 4/4] Waiting for data flow component to become healthy. (Current status: initializing, Last event: Pod is pending: Pod dfc-16dbfea1-7183-425e-adf3-97777a02fe78-lab-ifm-6fbf4797c6fl8g is pending, this is normal during initialization or when updating the data flow component.)
[7:30:10 AM] - [Step 4/4] Waiting for data flow component to become healthy. (Current status: initializing, Last event: Pod is pending: Pod dfc-16dbfea1-7183-425e-adf3-97777a02fe78-lab-ifm-6fbf4797c6fl8g is pending, this is normal during initialization or when updating the data flow component.)
[7:30:10 AM] - Error: failed to execute action: [Step 4/4] Data flow component had an error. Last status: error, Last event: Container not ready: Pod dfc-16dbfea1-7183-425e-adf3-97777a02fe78-lab-ifm-6fbf4797c6fl8g is running, but log contains errors: level=info msg="IODD API: https://management.umh.app/iodd" @service=benthos label="" path=root.input
level=error msg="Failed to connect to device at 192.168.100.32:443: Post \"http://192.168.100.32:443\": EOF" @service=benthos label="" path=root.input
level=error msg="Failed to connect to sensorconnect: Post \"http://192.168.100.32:443\": EOF" @service=benthos label="" path=root.input
level=info msg="Connecting to device at 192.168.100.32:443" @service=benthos label="" path=root.input
level=info msg="IODD API: https://management.umh.app/iodd" @service=benthos label="" path=root.input
level=error msg="Failed to connect to device at 192.168.100.32:443: Post \"http://192.168.100.32:443\": EOF" @service=benthos label="" path=root.input
level=error msg="Failed to connect to sensorconnect: Post \"http://192.168.100.32:443\": EOF" @service=benthos label="" path=root.input
level=info msg="Connecting to device at 192.168.100.32:443" @service=benthos label="" path=root.input
level=info msg="IODD API: https://management.umh.app/iodd" @service=benthos label="" path=root.input
level=error msg="Failed to connect to device at 192.168.100.32:443: Post \"http://192.168.100.32:443\": EOF" @service=benthos label="" path=root.input
level=error msg="Failed to connect to sensorconnect: Post \"http://192.168.100.32:443\": EOF" @service=benthos label="" path=root.input