GNU bug report logs - #27358
Timeout command was get failed to kill soffice.bin processes

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 27358 in the body.
You can then email your comments to 27358 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Ken Walker <kenwalker833 <at> gmail.com>
To: bug-coreutils <at> gnu.org
Subject: Timeout command was get failed to kill soffice.bin processes
Date: Wed, 14 Jun 2017 15:58:19 +0530

[Message part 1 (text/plain, inline)]

Hello,

We are converting xls to csv file using unoconv command, unoconv command
start soffice.bin proccess for convert file and it working fine to kill
that unoconv + soffice.bin process by timeout command  if taken more than
time which define with timeout command, But sometime it was not killed
soffice.bin process  so any idea why this happen?, Which case can occur
this issue, Can you please look at this and guide me proper regarding this,
As i have mention command + installed pages in my system so that will be
help to assist this thing, Let me know if require any further info
regarding this


*Installed packages :------------------------*
Os CentOS-6.4
unoconv 0.5
LibreOffice 4.2.8.2
Libreoffice-headless 4.2.8.2
Python 2.6.6
timeout (GNU coreutils) 8.4


*Command :------------*
exec('timeout 300 unoconv -T 10 -vvvvv -f csv -o "destination.xls"
"destination.csv" 2>&1', $arrOp, $return_value);

Thanks in advance!

Regards,
- Ken

[Message part 2 (text/html, inline)]

Message #8 received at 27358 <at> debbugs.gnu.org (full text, mbox):

From: Assaf Gordon <assafgordon <at> gmail.com>
To: Ken Walker <kenwalker833 <at> gmail.com>
Cc: 27358 <at> debbugs.gnu.org
Subject: Re: bug#27358: Timeout command was get failed to kill soffice.bin
 processes
Date: Wed, 14 Jun 2017 16:01:45 +0000

Hello Ken,

On Wed, Jun 14, 2017 at 03:58:19PM +0530, Ken Walker wrote:

>[...] unoconv command
>start soffice.bin proccess for convert file and it working fine to kill
>that unoconv + soffice.bin process by timeout command  if taken more than
>time which define with timeout command, But sometime it was not killed
>soffice.bin process  so any idea why this happen?

[...]

>exec('timeout 300 unoconv -T 10 -vvvvv -f csv -o "destination.xls"
>"destination.csv" 2>&1', $arrOp, $return_value);

Few observation (though not a clear solution):

1. As you've mentioned, the unoconv program does not do the conversion
  by itself, it needs a running openoffice program to do so (the
  'soffice' binary). 

2. If it doesn't find a running 'soffice' binary, it starts one.
  But if there is already a running 'soffice' binary (which already
  acts as a listener on 127.0.0.1:2002) - then it does NOT
  start a new binary.

3. This means that the 'soffice' binary is not a child-process
  of 'unoconv', and 'timeout' won't kill it.

you can observe the difference in the debug messages:

===
 $ unoconv -vvvv -f csv -o 1.xls 1.csv 
 Verbosity set to level 4
 Using office base path: /usr/lib/libreoffice
 Using office binary path: /usr/lib/libreoffice/program
 DEBUG: Connection type: socket,host=127.0.0.1,port=2002;urp;StarOffice.ComponentContext
 DEBUG: Existing listener not found.
 DEBUG: Launching our own listener using /usr/lib/libreoffice/program/soffice.bin.
 LibreOffice listener successfully started. (pid=30564)
===

versus (when there's already an OpenOffice program running):

===
 $ unoconv -vvvv -f csv -o 1.xls 1.csv 
 Verbosity set to level 4
 Using office base path: /usr/lib/libreoffice
 Using office binary path: /usr/lib/libreoffice/program
 DEBUG: Connection type: socket,host=127.0.0.1,port=2002;urp;StarOffice.ComponentContext
===

Without further details I can't tell if this is indeed the culprit
for the behaviour you're experiencing, but this would be one direction
to investigate.



As a side-note,
Since unoconv's operation model is based on a running OpenOffice
listener/server, it would be more efficient (IMHO)
to start one listener in the background, and then each 'unoconv'
invocation won't need to start a new OpenOffice instance (which is a
very slow process).

The unoconv program supports this operation mode with
the '--listener' and '--no-launch' parameters (see 'unoconv -h').
It would likely be useful to use a non-default port, to ensure
the listener does not conflict with other (non-listener) open-office
instances.

HTH,
- assaf

Message #11 received at 27358 <at> debbugs.gnu.org (full text, mbox):

From: Assaf Gordon <assafgordon <at> gmail.com>
To: 27358 <at> debbugs.gnu.org
Subject: Re: bug#27358: Timeout command was get failed to kill soffice.bin
 processes
Date: Sun, 28 Oct 2018 21:22:27 -0600

tags 27358 notabug
close 27358
stop

(triaging old bugs)

On 2017-06-14 10:01 a.m., Assaf Gordon wrote:
> 
> Without further details I can't tell if this is indeed the culprit
> for the behaviour you're experiencing, but this would be one direction
> to investigate.
> 

With no further comments in more than a year, I'm closing this bug.
Discussion can continue by replying to this thread.

-assaf

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.