Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
(In reply to Andreas Schneider from comment #4)
> Is this a Samba File Server running with sssd?
It's a samba file server. But sssd service doesn't start.
Comment 6Andreas Schneider
2018-07-02 10:29:31 UTC
(In reply to Andreas Schneider from comment #7)
> If this is only a file server, then you need to setup a fileserver. If you
> want to have an AD member set it up correctly. See the documentation above.
Do you mean MS file server? I didn't use MS file server here. And I also didn't want to have an AD member. In RHEL-7.5, this config in the Description works fine. And it needs "security = ads" even if doesn't use MS file server.
Comment 10Andreas Schneider
2018-07-04 15:29:56 UTC
Comment 14Andreas Schneider
2018-07-05 15:55:47 UTC
From the Samba release notes of 4.8.0:
Domain member setups require winbindd
-------------------------------------
Setups with "security = domain" or "security = ads" require a
running 'winbindd' now. The fallback that smbd directly contacts
domain controllers is gone.
The configuration from the initial description is incorrect anyway, it won't work.
Thanks Andreas and Amit. In this case, the winbind or sssd service aren't started. And the same smb.conf can work on samba-4.7.1-6.el7. From the comment 14, I know this is a configuration issue after update to samba-4.8. So I will close this bug as NOTABUG.
Description of problem: When I start smb service, it's failed(server and client are linux). 7月 01 23:05:24 ibm-x3650m4-01-vm-11.lab.eng.bos.redhat.com systemd[1]: Starting Samba SMB Daemon... 7月 01 23:05:24 ibm-x3650m4-01-vm-11.lab.eng.bos.redhat.com smbd[2616]: [2018/07/01 23:05:24.292551, 0] ../source3/auth/auth_util.c:1372(make_new_session_info_guest) 7月 01 23:05:24 ibm-x3650m4-01-vm-11.lab.eng.bos.redhat.com smbd[2616]: create_local_token failed: NT_STATUS_NO_MEMORY 7月 01 23:05:24 ibm-x3650m4-01-vm-11.lab.eng.bos.redhat.com systemd[1]: smb.service: main process exited, code=exited, status=255/n/a 7月 01 23:05:24 ibm-x3650m4-01-vm-11.lab.eng.bos.redhat.com systemd[1]: Failed to start Samba SMB Daemon. 7月 01 23:05:24 ibm-x3650m4-01-vm-11.lab.eng.bos.redhat.com systemd[1]: Unit smb.service entered failed state. 7月 01 23:05:24 ibm-x3650m4-01-vm-11.lab.eng.bos.redhat.com systemd[1]: smb.service failed. smb.conf: [root@ibm-x3650m4-01-vm-11 ~]# cat /etc/samba/smb.conf [global] workgroup = RHTS realm = RHQE.COM security = ads server signing = auto kerberos method = system keytab [cifs] path = /mnt/testarea/server writeable = yes But if remove "security = ads", the smb service can be started. Version-Release number of selected component (if applicable): samba-4.8.2-1.el7.x86_64 samba-client-4.8.2-1.el7.x86_64 3.10.0-915.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. setup the smb.conf like Description 2. start smb service 3. Actual results: start smb service failed Expected results: start smb service successfully Additional info: