Bug 2054351 - Rrestart of ptp4l/phc2sys on change of PTPConfig generates more than one times, socket error in event frame work
Summary: Rrestart of ptp4l/phc2sys on change of PTPConfig generates more than one ti...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.11.0
Assignee: Aneesh Puttur
QA Contact: obochan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-14 18:58 UTC by Aneesh Puttur
Modified: 2022-08-10 10:50 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-10 10:49:41 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift linuxptp-daemon pull 72 0 None open Bug 2054351:Fix restart process that was holding lock on asynchronous call, avoid multiple socket error 2022-02-15 13:24:12 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:50:11 UTC

Description Aneesh Puttur 2022-02-14 18:58:47 UTC
Description of problem:
LinuxPTP daemon has the functionality to restart when the process dies.
But the process also force killed while there is a change in ptpconfig.
This was create multiple time socket errors when the event framework is used.



Version-Release number of selected component (if applicable):


Step to reproduce 
modify ptpconfig and reapply and monitor fast event logs(cloud-event-proxy)
The cloud event proxy recovers from this error but cause to delay in reading logs from the socket

time="2022-01-31T20:21:45Z" level=error msg="error reading socket input"




Actual results:
Shown twice
time="2022-01-31T20:21:45Z" level=error msg="error reading socket input"
time="2022-01-31T20:21:45Z" level=error msg="error reading socket input"


Expected results:
time="2022-01-31T20:21:45Z" level=error msg="error reading socket input"
You should see with zero times or not more than once

Additional info:

Comment 2 obochan 2022-03-02 07:41:20 UTC
The issue isn't solved, i see this error multiple time. when i changed the ptpconfig i see it twice. you can see below.

time="2022-03-02T07:29:53Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:29:54Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:29:55Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:29:56Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:29:57Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:29:58Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:29:59Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:00Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:01Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:02Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:03Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:04Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:05Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:06Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:07Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:08Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:09Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:10Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:11Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:12Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:13Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:14Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:15Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:16Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:17Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:30:20Z" level=error msg="restored from extract metrics and events: runtime error: invalid memory address or nil pointer dereference"
time="2022-03-02T07:30:20Z" level=error msg="failed to extract ptp4l[1261.361]: [ptp4l.0.config] port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES"
time="2022-03-02T07:30:21Z" level=error msg="ptp4l failed to parse output ptp4l.0.config  updating UTC offset to 37: unexpected number of fields"
time="2022-03-02T07:31:17Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:31:17Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:38:51Z" level=error msg="ptp4l failed to parse output ptp4l.0.config  updating UTC offset to 37: unexpected number of fields"
time="2022-03-02T07:38:51Z" level=error msg="metrics found for empty interface ptp4l 1772.349    ptp4l.0.config  rms   19 max   19 freq   -850 +/-   2 delay   362 +/-   0"
time="2022-03-02T07:39:18Z" level=error msg="error reading socket input, retrying"
time="2022-03-02T07:39:18Z" level=error msg="error reading socket input, retrying"
[obochan@obochan ptp_goLang]$

Comment 4 obochan 2022-04-07 14:03:49 UTC
Validate the issue according the PR , should remove the number of errors, will reopen in case when v4.11 will be deployed and it reoccur

Comment 6 errata-xmlrpc 2022-08-10 10:49:41 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5069


Note You need to log in before you can comment on or make changes to this bug.