Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Testpoint container for rpi4

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Testpoint container for rpi4


Chronological Thread 
  • From: Luke Whitworth <>
  • To: "" <>
  • Subject: Re: [perfsonar-user] Testpoint container for rpi4
  • Date: Tue, 20 Jun 2023 14:31:19 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cranfield.ac.uk; dmarc=pass action=none header.from=cranfield.ac.uk; dkim=pass header.d=cranfield.ac.uk; 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:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=8ktqFOao+DXt+URHm9N0TjuUL9EXzHlwF17Q5rFw42s=; b=j9A6ZxgcQKaNvFK1Jcui9WRWXdA4T9X/xTqglFtpVWrnZ7WyU0AsEh5K2pjJwTC2VAfnf+KAdQVWia6bATIiCaYzHopqonxxVxwuFfu5byusjfJys7SpAACjRDumLIUb43ENnHXi2eqVePQ14ifnNIXBGSopDXZhFEvRGW/bJBXGVXlJ3ns9MwdjLcqH+GNYvysASJjVtTmxHUYVOPXCqVBcm9LrA0DpxcDsfRO+vpF5pjIXXS/QqBpQME4JwoKRjQg79cQGbk7QXFSbX/UTno3xY/IKiW01vWZ4g8YFrjTRzVxdKJ8krAEWw7vJ4nhKmVNLdJkTXvCAM20z2ran8g==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=D6zeOW9cKvGfbiJiOjjsQdzWDZV7oKOscGqVsj/t8lLm0rcJ8BkqHGIdca2wTYciDq1XldzmBEsdi34H58XTzn0gL+0C9C6dTBAj1Up0u9/Myd+ULhKFKBXkIR3eshY0E5H7dKEq10cXupDjPxZA65XID29mJbU6zVCW2X5+Cv2vlWn6kEVIlScnvNAesGGzT5EZO5epUngQwGhUUMW+ImBWUufZ61NqP5nBvTTQGTHg17HCO+Zo3+8E4lBy3CDkz3F0HqcEhNM76+1zbRzDaYaVHV7tn42rac81fQ9eKtl1zWDFIRjw4jCztzKWd6FHLloaq9pkyHsXnIqoqY+4tg==

Cheers Mark,

 

I hadn’t really approached syslog so that makes sense…..cheers for the pointer.

 

Luke

 

From: Mark Feit <>
Date: Tuesday, 20 June 2023 at 15:29
To: Luke Whitworth <>, <>
Subject: Re: Testpoint container for rpi4

Luke Whitworth writes:

 

Warning:  This is no doubt a huge mess, there’s probably much better ways to do this and running the container throws errors repeatedly such as:

 …

OSError: [Errno 9] Bad file descriptor 

FileNotFoundError: [Errno 2] No such file or directory

 

Those errors are indicative of syslog clients being unable to connect to the log socket.  The entry point script attempts (and fails) to start “rysylog” instead of “rsyslog” and that socket ends up not existing.

 

If I can offer a couple of suggestions:

 

  • Shell scripts should always have the -e switch in effect so they die immediately when something fails.  This error would have torpedoed the container before it got off the ground.  The trade-off is that you have to take explicit steps to make sure the shell doesn’t exit on failures you don’t care about.
  • Consider custom-configuring rsyslog so it sends log message to another server over the network.  That will cut down on disk write activity.

 

--Mark

 

 

 




Archive powered by MHonArc 2.6.24.

Top of Page