X2Go Bug report logs - #1166
x2goclient terminates with "WARNING: failed to kill process group '<pid>': No such process

Package: x2goclient; Maintainer for x2goclient is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goclient is src:x2goclient.

Reported by: Seth Galitzer <sgsax@ksu.edu>

Date: Mon, 27 Mar 2017 19:05:01 UTC

Severity: normal

Tags: not-a-bug

Done: Mihai Moldovan <ionic@ionic.de>

Bug is archived. No further changes may be made.

Full log


🔗 View this message in rfc822 format

MIME-Version: 1.0
X-Mailer: MIME-tools 5.507 (Entity 5.507)
X-Loop: owner@bugs.x2go.org
From: owner@bugs.x2go.org (X2Go Bug Tracking System)
Subject: Bug#1166 closed by Mihai Moldovan <ionic@ionic.de> (Re:
 x2goclient terminates with "WARNING: failed to kill process group '<pid>':
 No such process)
Message-ID: <handler.1166.b1166.149070261920962.notifdone@bugs.x2go.org>
References: <ee6a77dd-074a-8ac3-987e-f8a736282218@ionic.de>
X-X2go-PR-Message: they-closed 1166
X-X2go-PR-Package: x2goclient
X-X2go-PR-Source: x2goclient
Date: Tue, 28 Mar 2017 12:05:02 +0000
Content-Type: multipart/mixed; boundary="----------=_1490702702-21252-0"
[Message part 1 (text/plain, inline)]
This is an automatic notification regarding your Bug report
which was filed against the x2goclient package:

#1166: x2goclient terminates with "WARNING: failed to kill process group '<pid>': No such process

It has been closed by Mihai Moldovan <ionic@ionic.de>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Mihai Moldovan <ionic@ionic.de> by
replying to this email.


-- 
1166: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1166
X2Go Bug Tracking System
Contact owner@bugs.x2go.org with problems
[Message part 2 (message/rfc822, inline)]
From: Mihai Moldovan <ionic@ionic.de>
To: Seth Galitzer <sgsax@ksu.edu>, 1166@bugs.x2go.org
Subject: Re: x2goclient terminates with "WARNING: failed to kill process group '<pid>': No such process
Date: Tue, 28 Mar 2017 14:03:11 +0200
[Message part 3 (text/plain, inline)]
Control: close -1
Control: tag -1 not-a-bug

On 27.03.2017 08:58 PM, Seth Galitzer wrote:
> Package: x2goclient
> Version: 4.1.0.0 and 4.1.0.1
> 
> When exiting x2goclient, after a pause of about 2 seconds, the following 
> message is displayed to stderr:
> WARNING: unable to send SIGTERM to process group '<pid>': No such process
> 
> About 10 more seconds later, the following message is displayed to stderr:
> WARNING: failed to kill process group '<pid>': No such process
> 
> In some cases, the first message is not displayed, but the second one 
> always is after about 10-12 seconds. The pid is the same in both message.
> 
> This seems to only affect 4.1.x clients. 4.0.x clients do not seem to 
> have this behavior.

Most of the time, that's perfectly fine and nothing to worry about.

It merely means that x2goclient and its child processes exited cleanly before
the cleanup process could kill them.

If you should ever see stray x2goclient processes left *after* these messages,
then that's something to worry about.



Mihai

[signature.asc (application/pgp-signature, attachment)]
[Message part 5 (message/rfc822, inline)]
From: Seth Galitzer <sgsax@ksu.edu>
To: <submit@bugs.x2go.org>
Subject: x2goclient terminates with "WARNING: failed to kill process group '<pid>': No such process
Date: Mon, 27 Mar 2017 13:58:37 -0500
Package: x2goclient
Version: 4.1.0.0 and 4.1.0.1

When exiting x2goclient, after a pause of about 2 seconds, the following 
message is displayed to stderr:
WARNING: unable to send SIGTERM to process group '<pid>': No such process

About 10 more seconds later, the following message is displayed to stderr:
WARNING: failed to kill process group '<pid>': No such process

In some cases, the first message is not displayed, but the second one 
always is after about 10-12 seconds. The pid is the same in both message.

This seems to only affect 4.1.x clients. 4.0.x clients do not seem to 
have this behavior.

I have confirmed these results on the following platforms and builds:
Ubuntu 16.04 (xenial): x2goclient 4.1.0.0 
(4.1.0.0-0~1536~ubuntu16.04.1), installed from Launchpad PPA
Ubuntu 16.04 (xenial): x2goclient 4.1.0.1, compiled from source
Ubuntu 15.04 (vivid): x2goclient 4.1.0.0 (4.1.0.0-0~1536~ubuntu15.04.1), 
installed from Launchpad PPA
Ubuntu 15.04 (vivid): x2goclient 4.1.0.1, compiled from source
Debian 8.7 (jessie) 64-bit: x2goclient 4.1.0.1, compiled from source
Debian 8.7 (jessie) 32-bit: x2goclient 4.1.0.1, compiled from source

The following builds and platforms do not appear to be affected:
Ubuntu 16.04 (xenial): x2goclient 4.0.5.1 (4.0.5.1-1), installed from 
official Ubuntu repos
Ubuntu 15.04 (vivid): x2goclient 4.0.3.1 (4.0.3.1-4), installed from 
official Ubuntu repos
Debian 8.7 (jessie) 64-bit: x2goclient 4.0.3.1 (4.0.3.1-4), installed 
from official debian repos
Debian 8.7 (jessie) 32-bit: x2goclient 4.0.3.1 (4.0.3.1-4), installed 
from official debian repos

Seth

-- 
Seth Galitzer
Systems Coordinator
Computing and Information Sciences
Kansas State University
http://www.cis.ksu.edu/~sgsax
sgsax@ksu.edu
785-532-7790

Send a report that this bug log contains spam.


X2Go Developers <owner@bugs.x2go.org>. Last modified: Fri Apr 26 00:58:11 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.