FS#61149 - [samba] smbd fails if winbind is running on default intall

Attached to Project: Arch Linux
Opened by Doron Behar (doronbehar) - Friday, 21 December 2018, 17:30 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 21 December 2018, 18:04 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

A bug introduced in 4.9.x was reported upstream:

https://bugzilla.samba.org/show_bug.cgi?id=13697

It seems according to the comments that this patch fixes it:

https://bugzilla.samba.org/attachment.cgi?id=14752

I think it should be included in Arch's build of samba.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 21 December 2018, 18:04 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Config issue
Comment by Doug Newgard (Scimmia) - Friday, 21 December 2018, 17:38 GMT
Arch does not have it running on a "default install", so this would appear to be a config issue, and hence, not really an issue.
Comment by Doron Behar (doronbehar) - Friday, 21 December 2018, 17:40 GMT
Ok, but still this bug makes smb.service unusable if winbind.service is running meaning they can't run both at the same time.
Comment by Doug Newgard (Scimmia) - Friday, 21 December 2018, 17:53 GMT
Not according to the patch. Is winbind configured correctly before you start it?
Comment by Doron Behar (doronbehar) - Friday, 21 December 2018, 17:57 GMT
Interestingly, starting winbind.service after smb.service is already running doens't cause any problem. I guess that as the bug says, the problem occurs only when trying to start smbd after wingindd is already running. starting smbd first is the workaround.

Anyway I think we should include the patch, or perhaps change the systemd services so that smb.service is started after winbind.service.

Loading...