Pipeline needs to be restarted after every Raspberry Pi reboot

[MaD-DSD]

Apache StreamPipes version

None

Affected StreamPipes components

Processing Elements

What happened?

I am using Streampipes on a Raspberry Pi. The data source is an HTTP server adapter that captures data and forwards it via a REST Publisher (Data Sink) to a Flask endpoint running in the background on the Raspberry Pi.
Problem:
After a reboot of the Raspberry Pi, data no longer arrives at the Flask endpoint. However, if the pipeline is manually stopped and restarted, the data transmission works correctly again.

How to reproduce?

1. Reboot the Raspberry Pi.
2. Data does not arrive at the Flask endpoint.
3. Stop and restart the pipeline.
4. Data transmission works again after restarting the pipeline.

Expected behavior

The pipeline should continue functioning correctly after a Raspberry Pi reboot, without the need for a manual restart of the pipeline.

Additional technical information

No response

Are you willing to submit a PR?

None

[dominikriemer]

Hi @MaD-DSD do you use the standard docker-compose file where the dependsOndependencies are declared between backend and extensions?
For a normal reboot where StreamPipes receives a SIGTERM event, pipelines should be gracefully stopped.
If not (e.g., when the plug is removed from the Pi), usually Health checks should ensure that pipelines which where not properly shutdown are restarted. Is this the case in your setup? Health checks run by default every 60 seconds.

[cdeom]

Hi @dominikriemer,

Thank you for your feedback!

We are using this baseline with minor modifications:
https://github.com/apache/streampipes/blob/dev/docker-compose.yml.

I didn’t notice any depends_on related to the backend service in the extensions section of your file, but we will add it to test the setup.
In the backend service, the only depends_on we see is for CouchDB.