Project

General

Profile

Anomalie #11611

Occupation CPU > 99% processus soffice.bin

Added by Ines MKACHER over 2 years ago. Updated 12 months ago.

Status:
Rejeté
Priority:
1-Majeur
Target version:
Backlogs Produits - Inscription Backlog
Start date:
08/29/2019
Due date:
Tags Courrier:

History

#2 Updated by Laurent GIOVANNONI over 2 years ago

  • Target version changed from 20.03 (Support restreint) to 19.04 (Support sécurité)

Il faut ajouter la commande timeout devant le lancement d'unoconv

ex contextuel au lancement d'unoconv dans le compte maarch :

export HOME=/tmp && timeout 10 /usr/bin/unoconv -f pdf Documents/100-Documents\ TESTS/convert/test_cloudooo.odt

Il serait également intéressant d'intégrer un mécanisme de retry de la conversion comme indiqué sur le github d'unoconv :

https://github.com/unoconv/unoconv#problems-running-unoconv-from-nginxapachephp

Problems running unoconv from Nginx/Apache/PHP

Some people have had difficulties using unoconv through webservices. Here is a list of probable causes and recommendations:

Use the latest version of unoconv (or GitHub master branch)

Use the most recent stable release of LibreOffice (less memory, more stable, fewer crashes)

Use the native LibreOffice python binary to run unoconv

Hardcode this native python path in the unoconv script shebang (or ensure PATH is set)

Ensure that the user running unoconv has write access to its HOME directory (ensure HOME is set)

Test with SELinux in permissive mode

It is recomended to open the unoconv script and modify the very first line to point directly to your installed LibreOffice python binary, so replace this:

#!/usr/bin/env python

with something like this:

#!/opt/libreoffice4.4/program/python

Conversion problems

If you encounter problems converting files, it often helps to try again. If you are using a listener, restarting the listener may help as well.

The reason for conversion failures are unclear, and they are not deterministic. unoconv is not the only project to have noticed problems with import and export filters using PyUNO. We assume these are related to internal state or timing issues that under certain conditions fail to correctly work.

If you can reproduce the problem on a specific file, please take the time to open the file in LibreOffice directly and export it to the desired format. If this fails, it needs to be reported to the LibreOffice project directly. If that works, we need to know !

We are looking into this with the LibreOffice developers to:

Collaborate closer to find, report and fix unexpected failures

Allow end-users to increase debugging and improve reporting to the project

#3 Updated by Emmanuel DILLARD over 2 years ago

  • Status changed from A traiter to En cours d'écriture PO

#5 Updated by Emmanuel DILLARD over 2 years ago

  • Related to Anomalie #11544: Problème d'accès à la base de données lié à soffice.bin added

#6 Updated by Emmanuel DILLARD over 2 years ago

  • Status changed from En cours d'écriture PO to Prêt à développer

#7 Updated by Florian AZIZIAN over 2 years ago

  • Project changed from Backlog to CURRENT SPRINT
  • Status changed from Prêt à développer to En cours de dev (S)
  • Target version changed from 19.04 (Support sécurité) to 20.03 (Support restreint)
  • Tags Courrier 19.04.8 added

#8 Updated by Emmanuel DILLARD over 2 years ago

  • Related to deleted (Anomalie #11544: Problème d'accès à la base de données lié à soffice.bin)

#10 Updated by Emmanuel DILLARD over 2 years ago

  • Status changed from En cours de dev (S) to Développé / Analysé (S)

#11 Updated by Emmanuel DILLARD over 2 years ago

  • Project changed from CURRENT SPRINT to Backlog

#12 Updated by Emmanuel DILLARD over 2 years ago

  • Status changed from Développé / Analysé (S) to Prêt à développer
  • Priority changed from 0-Bloquant to 1-Majeur
  • Tags Courrier 18.10.11 added

Pour prise en compte 18.10

#13 Updated by Emmanuel DILLARD over 2 years ago

  • Status changed from Prêt à développer to A étudier

Attente retours sur les derniers correctifs (19.04) pour poursuivre sur cette voie. (Pour prise en compte 18.10

#14 Updated by Emmanuel DILLARD over 2 years ago

  • Status changed from A étudier to 17

#15 Updated by Florian AZIZIAN over 2 years ago

RETEX LGI:

une astuce pour débloquer les process libreoffice qui bloquent toutes les autres conversions et monopolisent le cpu à 100% :
rajouter dans la crontab de root :
" /5 8-20 * 1-5 killall soffice.bin"

Analyse par LGI :

il y a une solution avec unoconv pour faire du multithread, c'est la même que celle que l'on utilise dans le jnlp si on veut utiliser LO alors qu'il est déjà lancé sur le poste.
il faut lancer LO avec un répertoire utilisateur différent.
ils l'ont implémenté dans la dernière version d'unoconv :

commit 788170020bf67ebbae993e0776608e378bc07de3
Author: Miklos Vajna vmiklos@vmiklos.hu
Date: Fri Aug 10 21:30:44 2018 +0200
Allow using a custom user profile (#451)
This is useful when converting large documents on a machine with many
CPU cores/threads. Using a single unoconv server means in fact a single
document is converted at a time, given LibreOffice uses a single global
lock for remote method invocations.
Starting multiple unoconv servers is not possible by default, as the
second one will complain that the user profile is locked. Using a custom
user profile is a solution to this.
il faut lancer unoconv avec le paramètre --user-profile
et mettre une valo aléatoire du type /tmp/timestamp (modifié)
le souci c'est que c'est dans la branche master
pas encore dans une branche stable...

#16 Updated by Emmanuel DILLARD over 2 years ago

  • Status changed from 17 to A étudier
  • Assignee changed from EDI PO to Maarch Courrier DEV TEAM
  • Target version changed from 20.03 (Support restreint) to Inscription Backlog Courrier
  • Tags Courrier deleted (18.10.11, 19.04.8)

Contournement indiqué dans la demande.

En attente des versions stables d'unoconv.

#17 Updated by Emmanuel DILLARD over 2 years ago

  • Status changed from A étudier to 17

#21 Updated by Emmanuel DILLARD over 2 years ago

  • Status changed from 17 to Rejeté PO

#22 Updated by Emmanuel DILLARD about 1 year ago

  • Status changed from Rejeté PO to Rejeté

#23 Updated by Emmanuel DILLARD 12 months ago

  • Project changed from Backlog to Backlog Courrier
  • Target version changed from Inscription Backlog Courrier to Inscription Backlog

Also available in: Atom PDF