perfsonar-user - Re: [perfsonar-user] Docker issues
Subject: perfSONAR User Q&A and Other Discussion
List archive
- From: Ignacio Peluaga Lozada <>
- To: Mark Feit <>, "" <>
- Subject: Re: [perfsonar-user] Docker issues
- Date: Thu, 23 Sep 2021 08:38:15 +0200
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass (sender ip is 188.184.36.16) smtp.rcpttodomain=internet2.edu smtp.mailfrom=cern.ch; dmarc=bestguesspass action=none header.from=cern.ch; dkim=none (message not signed); arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=sHvHGnDDMHE0bIIlimptmVBqOGl0yzMuIVYludxHF/4=; b=n8mlqT/nyiWyEnYNdF6bjeheZwXixMk/5jbiI08SUQlLYaCQq+A6I+c0X6mOUkj9CG8fa8QMKD/YtiVj2SwpcmfbQ+4h3XZ0JX8BpJDGA+tXXY/MTMvX79hY07x7nvPxMj8SxZsHkl1fdWS0cRn73AOPJvXRTc59aXPMeVE00vIOUys4deySUJHBcCHzoxvGGZCkHHXWBP62RxqFGCsfGB/DFmUJXoiMtApQnsEl4+mXBUjGEDmC5MxGhprG/db13glPe01InHBp02j/tbDVSTfJirlAlHJw09Wf4Mh+SjmgRkhML/kte4Y2f+72/JLSfW0sLICe4GEtpsWj0ZsmwQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=hhW4+KbYPepGQ0/nIG3Oqs6TgdaSKjmYiMd2Hy4y8xPrMKk7ZAy0O0SuZl0GOb5NgaY+PYdORci7ss0Ft2qmsxpBrY6iJ1ynxQ3G76GNzz/kpwubm7KDgFG3MR51ILn3p4sUX+gOMr3GYagqO8dIcVpGfYgIpebm3KgpdOZjNz+6APR6WrLDLyd7QVyxlvjFLUjIUK0p7chkeHPEllcft5PrnDaMeXvBB36VLxquRnfOmmGMl6hScfbkidA7+rEEb5721DbMMEs4NtAtM8C+Ky9rY1FjLkwkmrGhkT9Ho6/hPko06VMvYNHXLGNeaUH3UyjpcqeqeaFwZZO95MtXzQ==
- Importance: Normal
On 22/09/2021 23:57 Mark Feit <> wrote:
Ignacio Peluaga Lozada writes:
I have been experiencing issues with the testpoint image lately. I created a container using the latest image (4.4.1) and always got "Run did not complete: Missed" on pscheduler's CLI, regardless of the task or target node. On the same host I had the Docker container I installed the toolkit v4.4.1 and everything worked. Besides, I tried some other Docker image versions:
-perfsonar/testpoint:v4.4.0: same issues as with v4.4.1.
-perfsonar/testpoint:v4.3.4: worked fine.
-perfsonar/testpoint:systemd: worked fine.
Therefore I believe the problem is with perfSONAR's supervisord based v4.4.x testpoint images. Is anyone else experiencing this?
This is a known problem in the 4.4.x container that has to do with supervisord’s inability to properly start the service that runs the tasks after they’ve been scheduled. If you can run one of the other containers in the mean time, we’ll get it fixed.
--Mark
- [perfsonar-user] Docker issues, Ignacio Peluaga Lozada, 09/21/2021
- Re: [perfsonar-user] Docker issues, Mark Feit, 09/22/2021
- Re: [perfsonar-user] Docker issues, Ignacio Peluaga Lozada, 09/23/2021
- Re: [perfsonar-user] Docker issues, Mark Feit, 09/22/2021
Archive powered by MHonArc 2.6.24.