A process blockage

[Darkluna999]

The Same as #3067
Every once in a while this phenomenon can cause a flow blockage
not only run agent schedule 'every_1m'
but also run agent schedule 'every_2m' run agent schedule 'every_5m'
If it is repeated the same time, it will create a process blockage
This is not caused by any of my processes, even the sample process that has just been deployed will occur after a period of time and will not disappear if it is not reset
Even if I delete the entry directly from the database, it can't be corrected, only by restarting the container

[Darkluna999]

Some additions, even if I use a version 2 years ago, this problem still occurs.
But I found a solution, this problem will not occur if I don't connect to an external postgres database?

[przemo]

I happen to have the same problem. No extremalnie postgres DB.

[RafaelSchridi]

having the same problem, no external DB.

[ww2283]

same problem here, latest docker image:

[dongore]

Same here as well.

[kix2902]

I've got this problem right now, restarting the container fixed it and all the processes finished in a hurry

[yalidabuda]

Yes, restarting the container can fix it, but next time I don't know when it will appear again.

[virtadpt]

Some additions, even if I use a version 2 years ago, this problem still occurs. But I found a solution, this problem will not occur if I don't connect to an external postgres database?

Could it be that Huginn is losing contact with the external database server, and failing to reconnect? Is there anything along those lines in the production.log file?

[dongore]

I'm not using am external database, but in my experience it does happen when the internet connection drops out. So it seems it starts hanging when the connection to an external source fails.

[Darkluna999]

So after all this time, do you guys have any solutions to fix this problem?

[virtadpt]

I think the only solution any of us have really found was to prevent the database connections from dropping, because that seems to cause it. That's easier said than done due to how TCP/IP works.