Flower: Persistent options seems not working

[vahdani]

Although I'm using --persistent option and the flower.db file is created but when i restart flower nothing is saved and everything is just like the first run.
I just can't see any difference. What data is flower supposed to persist in database?

[mher]

@vahdani please try the master version (fixed by #203) or use "--persistent --db=flower" (without extension)

[vahdani]

I tried the --persistent --db=flower option and still the same. I'll test the master version and let you know.

[gidantribal]

I tried the master version. Now the tasks are correctly kept in memory!
I don't know if it's an expected behaviour but the _monitoring_ page is cleared when page refresh is performed (a.k.a.: losing statistics if the page is left or F5 is pressed).

[mher]

The monitoring page is not persistent. There is a feature request about it #27.

[orporat]

Hi,

I use supervisor to daemonize flower, and had the same problem.
If anyone else is using supervisor and comes across this problem, for me the solution was to set stopsignal=TERM instead of stopsignal=QUIT in my supervisor [program:] config.

I guess stopsignal=QUIT means that supervisor "cold-kills" the flower process, preventing the persistency (which happens at "warm" termination) from happening.