Ok, folks,
I brought this up some time ago, and got no replies. We have a good
number of systems - > 100 - and we use sssd. On the C 7 boxen, which is
most of them, gssproxy *frequently* (like once a day or so) dies with a
SEGV. It restarts fine. Dies again eventually.
ARE other people seeing this? If so, I guess we get to file a bug
report with upstream. Speaking as an old C programmer, dying with a
SEGV? Really? In production?
mark
On 1/25/19 10:27 AM, mark wrote:> Ok, folks, > > I brought this up some time ago, and got no replies. We have a good > number of systems - > 100 - and we use sssd. On the C 7 boxen, which is > most of them, gssproxy *frequently* (like once a day or so) dies with a > SEGV. It restarts fine. Dies again eventually. > > ARE other people seeing this? If so, I guess we get to file a bug > report with upstream. Speaking as an old C programmer, dying with a > SEGV? Really? In production? > > markI myself have never heard or seen of this. I wonder if it's something to do with the ssd's themselves?...maybe you got a bad batch? or maybe there's a configuration setting that's not tweaked just right? Because if this happens continually? then its a recurring issues which means its something that the OS can't correct on it's own. Maybe pull those drives one at a time (assuming you have spare drives to "cover" as stand-in replacements until you suss it out? Just my two cents on the matter. EGO II
On Mon, 2019-01-28 at 00:04 -0500, Eddie G. O'Connor Jr. wrote:> On 1/25/19 10:27 AM, mark wrote: > > Ok, folks, > > > > I brought this up some time ago, and got no replies. We have a good > > number of systems - > 100 - and we use sssd. On the C 7 boxen, which is > > most of them, gssproxy *frequently* (like once a day or so) dies with a > > SEGV. It restarts fine. Dies again eventually. > > > > ARE other people seeing this? If so, I guess we get to file a bug > > report with upstream. Speaking as an old C programmer, dying with a > > SEGV? Really? In production? > > > > mark > > I myself have never heard or seen of this. I wonder if it's something to > do with the ssd's themselves?...maybe you got a bad batch? or maybe > there's a configuration setting that's not tweaked just right? Because > if this happens continually? then its a recurring issues which means its > something that the OS can't correct on it's own. Maybe pull those drives > one at a time (assuming you have spare drives to "cover" as stand-in > replacements until you suss it out? Just my two cents on the matter. >not SSD as in disk, SSSD as in "System Security Services Daemon". P.