Bug 1444028

Summary:	[SAMBA-RHEL6]Unable to start smbd in RHEL6 as /run/smbd.pid does not exist
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Vivek Das <vdas>
Component:	samba	Assignee:	Michael Adam <madam>
Status:	CLOSED ERRATA	QA Contact:	Vivek Das <vdas>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.3	CC:	amukherj, gdeschner, rcyriac, rhs-smb
Target Milestone:	---	Keywords:	Regression
Target Release:	RHGS 3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	samba-4.6.3-0.el6rhs	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-21 04:46:03 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:	1417151

Description Vivek Das 2017-04-20 12:57:48 UTC

Description of problem:
Unable to start smbd as there is no directory /run in RHEL6 and smbd.pid is redirected to that directory.

Version-Release number of selected component (if applicable):
samba-client-4.6.2-0.el6rhs.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Update samba to 3.3.0 packages
2.Try starting smbd
3.

Actual results:
Fails

Expected results:
Should start smoothly

Additional info:
Apr 20 18:08:09 dhcp43-15 smbd[10696]:   ERROR: can't open /run/smbd.pid: Error was No such file or directory
Apr 20 18:08:30 dhcp43-15 smbd[10726]: [2017/04/20 12:38:30.094635,  0] ../lib/util/pidfile.c:111(pidfile_create)
Apr 20 18:08:30 dhcp43-15 smbd[10726]:   ERROR: can't open /run/smbd.pid: Error was No such file or directory

Comment 15 Vivek Das 2017-05-03 03:43:40 UTC

Irrespective of the bug https://bugzilla.redhat.com/show_bug.cgi?id=1446325
i am able to start smbd over RHEL6 with the latest Rebase and was able to do a mount on windows machine. So marking this as verified.

Comment 19 errata-xmlrpc 2017-09-21 04:46:03 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-2017:2778