greengrass status is active, but component deployment is not working

Question

Hello, I installed greengrass on raspberry pie and am using it.
I've definitely seen custom components created, deployed, and worked properly.
A week later, I went back to Raspberry Pi and redistributed the components. But I found out that the components were not deployed. The deployment is stopped in rollout. I was able to get the following logs.

## greengrass component

```json
Components currently running in Greengrass:
Component Name: TelemetryAgent
    Version: 0.0.0
    State: BROKEN
    Configuration: null
Component Name: FleetStatusService
    Version: 0.0.0
    State: BROKEN
    Configuration: null
```

## greengrass.log
```json
2024-11-11T09:56:39.861Z [ERROR] (FleetStatusService-lifecycle) com.aws.greengrass.lifecyclemanager.UnloadableService: service-broken. service is broken. Deployment is needed. {serviceName=FleetStatusService, currentState=BROKEN}
2024-11-11T09:56:40.086Z [INFO] (pool-3-thread-10) com.aws.greengrass.tes.TokenExchangeService: Started server at port 45273. {serviceName=aws.greengrass.TokenExchangeService, currentState=STARTING}
2024-11-11T09:56:40.092Z [INFO] (aws.greengrass.TokenExchangeService-lifecycle) com.aws.greengrass.tes.TokenExchangeService: service-set-state. {serviceName=aws.greengrass.TokenExchangeService, currentState=STARTING, newState=RUNNING}
2024-11-11T09:58:06.778Z [INFO] (AwsEventLoop 1) software.amazon.awssdk.eventstreamrpc.RpcServer: New connection code [AWS_ERROR_SUCCESS] for [Id 22, Class ServerConnection, Refs 1](2024-11-11T09:58:06.776272122Z) - . {}
2024-11-11T09:58:07.054Z [INFO] (AwsEventLoop 1) software.amazon.awssdk.eventstreamrpc.ServiceOperationMappingContinuationHandler: aws.greengrass#GreengrassCoreIPC authenticated identity: greengrass-cli#user-0. {}
2024-11-11T09:58:07.057Z [INFO] (AwsEventLoop 1) software.amazon.awssdk.eventstreamrpc.ServiceOperationMappingContinuationHandler: Connection accepted for greengrass-cli#user-0. {}
2024-11-11T09:58:07.059Z [INFO] (AwsEventLoop 1) software.amazon.awssdk.eventstreamrpc.ServiceOperationMappingContinuationHandler: Sending connect response for greengrass-cli#user-0. {}
2024-11-11T09:58:07.481Z [INFO] (AwsEventLoop 1) software.amazon.awssdk.eventstreamrpc.RpcServer: Server connection closed code [socket is closed.]: [Id 22, Class ServerConnection, Refs 1](2024-11-11T09:58:06.776272122Z) - . {}
2024-11-11T09:59:00.988Z [INFO] (AwsEventLoop 1) software.amazon.awssdk.eventstreamrpc.RpcServer: New connection code [AWS_ERROR_SUCCESS] for [Id 24, Class ServerConnection, Refs 1](2024-11-11T09:59:00.984357997Z) - . {}
2024-11-11T09:59:01.202Z [INFO] (AwsEventLoop 1) software.amazon.awssdk.eventstreamrpc.ServiceOperationMappingContinuationHandler: aws.greengrass#GreengrassCoreIPC authenticated identity: greengrass-cli#user-0. {}
2024-11-11T09:59:01.203Z [INFO] (AwsEventLoop 1) software.amazon.awssdk.eventstreamrpc.ServiceOperationMappingContinuationHandler: Connection accepted for greengrass-cli#user-0. {}
2024-11-11T09:59:01.204Z [INFO] (AwsEventLoop 1) software.amazon.awssdk.eventstreamrpc.ServiceOperationMappingContinuationHandler: Sending connect response for greengrass-cli#user-0. {}
2024-11-11T09:59:01.499Z [INFO] (AwsEventLoop 1) software.amazon.awssdk.eventstreamrpc.RpcServer: Server connection closed code [socket is closed.]: [Id 24, Class ServerConnection, Refs 1](2024-11-11T09:59:00.984357997Z) - . {}
```

What should I do? Please help me.

re:Post Agent · Answer

Based on the information provided, it appears that your AWS IoT Greengrass core device is experiencing issues with component deployment and some services are in a BROKEN state. Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. Restart the AWS IoT Greengrass daemon:
   First, try restarting the Greengrass daemon. On your Raspberry Pi, run the following commands:
   ```
   cd /greengrass/v2/core/
   sudo ./greengrassd stop
   sudo ./greengrassd start
   ```

2. Check the device connectivity:
   Ensure that your Raspberry Pi has a stable internet connection and can reach the AWS IoT Greengrass service endpoints.

3. Verify the device configuration:
   Double-check that your device's configuration, including certificates and permissions, is correct and up-to-date.

4. Review the full logs:
   Examine the complete Greengrass log file for more detailed error messages or indications of what might be causing the deployment to stop. You can view the logs using the following command:
   ```
   sudo tail -f /greengrass/v2/logs/greengrass.log
   ```

5. Check for component conflicts:
   If you have multiple versions of components or conflicting dependencies, it could cause deployment issues. Review your component configurations and ensure there are no conflicts.

6. Attempt a manual deployment:
   Try creating a new deployment from the AWS IoT Greengrass console or using the AWS CLI to see if it resolves the issue.

7. Reset the Greengrass installation:
   If none of the above steps work, you may need to consider resetting your Greengrass installation. This should be done as a last resort, as it will remove all existing components and configurations.

If the issue persists after trying these steps, you may need to contact AWS support for further assistance, as there could be underlying issues with your specific setup or AWS account configuration.  
**Sources**  
[Test AWS IoT Greengrass components with local deployments - AWS IoT Greengrass](https://docs.aws.amazon.com/greengrass/v2/developerguide/test-components.html)  
[Troubleshooting AWS IoT Greengrass - AWS IoT Greengrass](https://docs.aws.amazon.com/greengrass/v1/developerguide/gg-troubleshooting.html)

greengrass status is active, but component deployment is not working

greengrass component

greengrass.log

Relevant content