Hi, folks,
Especially Johnny - could you possibly push this fix through as soon as
upstream puts it out? It's a real issue for us - we've had a number of
servers whether gssproxy keeps SEGVing, which hits NFS and samba.
Thanks in advance.
mark
---------------------------- Original Message ----------------------------
Subject: [Bug 1699331] gssproxy segmentation fault
From: bugzilla at redhat.com
Date: Wed, May 1, 2019 13:19
To: m.roth at 5-cent.us
--------------------------------------------------------------------------
https://bugzilla.redhat.com/show_bug.cgi?id=1699331
Robbie Harwood <rharwood at redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Fixed In Version|gssproxy-0.7.0-25.el7 |gssproxy-0.7.0-26.el7
--
You are receiving this mail because:
You are on the CC list for the bug.
Johnny Hughes
2019-May-08 12:49 UTC
[CentOS] [Fwd: [Bug 1699331] gssproxy segmentation fault]
On 5/2/19 9:15 AM, mark wrote:> Hi, folks, > > Especially Johnny - could you possibly push this fix through as soon as > upstream puts it out? It's a real issue for us - we've had a number of > servers whether gssproxy keeps SEGVing, which hits NFS and samba. >Mark, See if this fixes your issues .. if do, let me know and we can get it released into the fasttrack repo: https://buildlogs.centos.org/c7-fasttrack.x86_64/gssproxy/ Note: This packages are unsigned and if it fixes your issue, I'll sign and release them into fasttrack repo Note2: Here is some info on our new fasttrack repo: https://wiki.centos.org/AdditionalResources/Repositories (see CentOS-Fasttrack) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: OpenPGP digital signature URL: <http://lists.centos.org/pipermail/centos/attachments/20190508/93aeaa20/attachment-0002.sig>
Hi, Johnny, Johnny Hughes wrote:> On 5/2/19 9:15 AM, mark wrote: >> >> Especially Johnny - could you possibly push this fix through as soon as >> upstream puts it out? It's a real issue for us - we've had a number of >> servers whether gssproxy keeps SEGVing, which hits NFS and samba. > > See if this fixes your issues .. if do, let me know and we can get it > released into the fasttrack repo: > > https://buildlogs.centos.org/c7-fasttrack.x86_64/gssproxy/ > > > Note: This packages are unsigned and if it fixes your issue, I'll sign > and release them into fasttrack repo > > Note2: Here is some info on our new fasttrack repo: > > > https://wiki.centos.org/AdditionalResources/Repositories > (see CentOS-Fasttrack) >Thank you very much. I've d/l the x86_64 rpm, and yum upgraded to it on one server, so it's soaking now, and we'll see what happens. One question: the email I got from RH bugzilla referred to the package as gssproxy-0.7.0-25, not 21, while I see you've got it as 21.el7.0.1. Will there be a name change, or will it be 21.whatever? mark
Hi, Johnny, Johnny Hughes wrote:> On 5/2/19 9:15 AM, mark wrote: >> >> Especially Johnny - could you possibly push this fix through as soon as >> upstream puts it out? It's a real issue for us - we've had a number of >> servers whether gssproxy keeps SEGVing, which hits NFS and samba. > > See if this fixes your issues .. if do, let me know and we can get it > released into the fasttrack repo: > > https://buildlogs.centos.org/c7-fasttrack.x86_64/gssproxy/ > > Note: This packages are unsigned and if it fixes your issue, I'll sign > and release them into fasttrack repo > > Note2: Here is some info on our new fasttrack repo: > > https://wiki.centos.org/AdditionalResources/Repositories > (see CentOS-Fasttrack)Huh. Well, I don't see it SEGVing, but it suddenly started throwing May 8 12:21:21 <servername> kernel: gssproxy: server localhost not responding, timed out errors. That's the other thing we've been seeing, and I thought the two were related, but perhaps not.... mark