On 21/10/13 10:46 +0200, Ralf Peschke wrote: > We also had some unoconv crashes on both, production and development > server. Repeating the task from GUI always resolved the issue. > Because of that we put the loop into the source code like this: > > try: > errcnt = 0 > while True: > proc = subprocess.Popen(cmd, stdout=subprocess.PIPE) > stdoutdata, stderrdata = proc.communicate() > if proc.wait() != 0: > if errcnt < 5: > errcnt += 1 > continue > else: > raise Exception(stderrdata) > return stdoutdata > finally: > os.remove(path) > > in report.py and since 4 months we had no more problems.
It could be interresting to include in trunk with some little rework like using CONFIG['retry'] and using a for-loop. But before that we should understand what kind of error we get, because maybe it can be solved in unoconv directly. For example what is in stderrdata? -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgp0BHBy6n6Ke.pgp
Description: PGP signature
