ch0k0bn
ch0k0bn
Not fixed yet but seems to be an issue with python3/python2 (cf. https://github.com/quarkslab/irma/issues/74#issuecomment-778017254)
Latest version ? cause a fix for similar bug was shipped in 1.5.1 c3e2d3eb
First try with jmeter, i need a better frontend as i just flooded uwsgi. Still trying to reproduce. To be continued.
for reproducing you are scanning multiple times the same files ? (through irma-cli test i guess)
i'm rebasing your PR right now. will test it on 1.3.0.
There is a known problem with FProt and Supervisord, celery dameon launched in commandline are working well but through supervisord fprot process is stuck. Do you launch celery daemon with...
[EDITED] fixed workdir option You could stop probe celery daemon: `sudo supervisorctl stop probe_app` and launch celery daemon manually: `/opt/irma/irma-probe/current/venv/bin/celery worker --app=probe.tasks:app --workdir=/opt/irma/irma-probe/current` For durable workaround, delete supervisord probe_app and...
Did you restart also the celery daemon or not ? Which version of celery are you using ?
Sorry @fmonjalet, didnt had time to test it. To be continued
Hi Florent, I tried this 2 scenarios: - launched a 50 files scan, during the scan stopped rabbitmq-server for 30s then restarted it: after few reconnection attempts both brain celery...