Bug 1532618

Summary:	Kept getting "smbd[process-id]: PANIC (pid <process-id>): internal error"
Product:	Red Hat Enterprise Linux 7	Reporter:	Ming Davies <minyu>
Component:	samba	Assignee:	Andreas Schneider <asn>
Status:	CLOSED ERRATA	QA Contact:	Robin Hack <rhack>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	7.4	CC:	asn, gdeschner, gparente, jarrpa, rhack, tscherf
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	samba-4.8.0-1.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1581373 (view as bug list)		Environment:
Last Closed:	2018-10-30 07:59:53 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1581373

Description Ming Davies 2018-01-09 13:04:49 UTC

Description of problem:
Customer kept getting the  "smbd[process-id]:  PANIC (pid <process-id>): internal error" in their /var/log/messages file. 

Nothing has been changed. The customer said:"samba service re-establishes itself after the panic, which means the service stays available."

The customer said:"I have not found yet any way to easily reproduce the error or panics."

We have core files from the customer.

Version-Release number of selected component (if applicable):
samba-4.6.2-11.el7_4.x86_64                                 

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 7 Andreas Schneider 2018-03-07 13:30:24 UTC

Ping!

Comment 9 Robin Hack 2018-04-03 13:03:00 UTC

QA_ACK+ sanity only.

Comment 14 errata-xmlrpc 2018-10-30 07:59:53 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, 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-2018:3056