[Bug 2042363] Comment bridged from LTC Bugzilla

2024-04-24 Thread bugproxy
--- Comment From david_pa...@uk.ibm.com 2024-04-24 02:47 EDT--- Hi, We have had a reply from the AIX support team (see below) explaining the RENEW requests. Do you have any further questions for the AIX support team or can we supply any further diagnostic information to progress this

[Bug 2042363] Comment bridged from LTC Bugzilla

2024-04-18 Thread bugproxy
--- Comment From david_pa...@uk.ibm.com 2024-04-18 11:00 EDT--- Hi, Thanks for looking at the logs. I agree that both syslogs (AIX 7.2 and 7.3) contain multiple "TCP recvfrom got EAGAIN" entries. To clarify the information in the attachments, I have updated the comment for the

[Bug 2042363] Comment bridged from LTC Bugzilla

2024-04-17 Thread bugproxy
--- Comment From david_pa...@uk.ibm.com 2024-04-17 13:11 EDT--- Here are the details of the IP addresses for the tcpdump files AIX 7.3 9.20.120.112name = amaliada.v6.hursley.ibm.com -- Primary 9.20.120.153 name = adamsongrunter.v6.hursley.ibm.com ? Partner AIX 7.2

[Bug 2042363] Comment bridged from LTC Bugzilla

2024-04-17 Thread bugproxy
--- Comment From david_pa...@uk.ibm.com 2024-04-17 05:37 EDT--- Hi, I have run the same MQ HA test on a working(AIX 7.2) and non working(AIX 7.3) pair of machines with the same Linux NVSv4 Ubuntu 20.04 (kernel updated to 5.4.0-176-generic). I used the same RPC debug trace options as

[Bug 2042363] Comment bridged from LTC Bugzilla

2024-03-19 Thread bugproxy
--- Comment From david_pa...@uk.ibm.com 2024-03-19 13:53 EDT--- Is there an update from Canonical please? Can we provide any further information or trace to help diagnose this issue ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 2042363] Comment bridged from LTC Bugzilla

2024-03-11 Thread bugproxy
--- Comment From david_pa...@uk.ibm.com 2024-03-11 03:51 EDT--- Has there been any further progress on this issue from the Linux NFS development team ? The AIX NFS development team will not progress the problem from their side until they understand why the BAD_SEQID errors has been