Jobst Schmalenbach
2019-May-24 12:53 UTC
[Samba] Upgraded from CentOS 6.X to 7.X, samba not working
Hi Previous: CentOS 6.X, samba4.x86_64 4.2.10-15.el6 Now: CentOS 7.6.1810, samba 4.8.3-4.el7 When I start smb, nmb or winbind I get no errors at all. This is all I get: May 24 22:44:04 HOST systemd[1]: Starting Samba SMB Daemon... May 24 22:44:05 HOST systemd[1]: smb.service: main process exited, code=exited, status=1/FAILURE May 24 22:44:05 HOST systemd[1]: Failed to start Samba SMB Daemon. May 24 22:44:05 HOST systemd[1]: Unit smb.service entered failed state. May 24 22:44:05 HOST systemd[1]: smb.service failed. Looking at the samba logs, they are all empty. The journal has not much info either. What the hell am I doing wrong? Are there massive changes between 4.2 and 4.8 that its not working? Help please, I have till Monday morning to get this sorted (weekend). jobst
L.P.H. van Belle
2019-May-24 13:45 UTC
[Samba] Upgraded from CentOS 6.X to 7.X, samba not working
You should have looked before upgrading. ...
If its an AD-DC.
The change to samba AD DC with systemd is:
systemctl stop smbd nmbd winbind samba
systemctl disable smbd nmbd winbind samba
systemctl mask smbd nmbd winbind samba
systemctl unmask samba-ad-dc
systemctl enable samba-ad-dc
systemctl start samba-ad-dc
You should not start nmbd smbd winbind for the AD-DC, the needed things are
started by samba-ad-dc
A member needs smbd winbind and optional nmbd.
Now this is on a debian system, but i think these above are the same on centos.
Then, You could/should have looked at.
https://wiki.samba.org/index.php/Updating_Samba
But first, fix you smb.conf, thats most important here.
These are all the changes.
smb.conf changes
===============https://www.samba.org/samba/history/samba-4.10.0.html, please
read the full changelog.
It contains much more info, the change to samba 4.10 is not a small change.
4.9.x => 4.10.0 : smb.conf changes
Parameter Name Description Default
-------------- ----------- -------
prefork backoff increment Delay added to process restart 10 (seconds)
between attempts.
prefork maximum backoff Maximum delay for process between 120 (seconds)
process restart attempts
smbd search ask sharemode Name changed, old name was "smbd:search ask
sharemode"
smbd async dosmode Name changed, old name was "smbd:async
dosmode"
smbd max async dosmode Name changed, old name was "smbd:max async
dosmode"
smbd getinfo ask sharemode New: similar to "smbd search ask yes
sharemode" but for SMB getinfo
https://www.samba.org/samba/history/samba-4.9.0.html
4.8.x => 4.9.0 : smb.conf changes
As the most popular Samba install platforms (Linux and FreeBSD) both
support extended attributes by default, the parameters "map readonly",
"store dos attributes" and "ea support" have had their
defaults changed
to allow better Windows fileserver compatibility in a default install.
Parameter Name Description Default
-------------- ----------- -------
map readonly Default changed no
store dos attributes Default changed yes
ea support Default changed yes
full_audit:success Default changed none
full_audit:failure Default changed none
https://www.samba.org/samba/history/samba-4.8.0.html
4.7.x => 4.8.0 : smb.conf changes
===============smb.conf changes
=============== Parameter Name Description
Default
-------------- ----------- -------
apply group policies New no
auth methods Removed
binddns dir New
client schannel Default changed/ yes
Deprecated
gpo update command New
ldap ssl ads Deprecated
map untrusted to domain Removed
oplock contention limit Removed
prefork children New 1
mdns name New netbios
fruit:time machine New false
profile acls Removed
use spnego Removed
server schannel Default changed/ yes
Deprecated
unicode Deprecated
winbind scan trusted domains New yes
winbind trusted domains only Removed
! DO READ THE 4.8.x changelogs complete, on the samba site its needed!
https://www.samba.org/samba/history/samba-4.7.0.html
4.6.x => 4.7.0 : smb.conf changes
=============== Parameter Name Description
Default
-------------- ----------- -------
allow unsafe cluster upgrade New parameter no
auth event notification New parameter no
auth methods Deprecated
client max protocol Effective SMB3_11
default changed
map untrusted to domain New value/ auto
Default changed/
Deprecated
mit kdc command New parameter
profile acls Deprecated
rpc server dynamic port range New parameter 49152-65535
strict sync Default changed yes
password hash userPassword schemes New parameter
ntlm auth New values ntlmv2-only
----------------------
! DO READ THE 4.6.x changelogs complete, on the samba site its needed!
4.5.x => 4.6.0 : smb.conf changes
https://www.samba.org/samba/history/samba-4.6.0.html
=============== Parameter Name Description Default
-------------- ----------- -------
kerberos encryption types New all
inherit owner New option
fruit:resource Spelling correction
lsa over netlogon New (deprecated) no
rpc server port New 0
4.4.1 => 4.5.0 : smb.conf changes
https://www.samba.org/samba/history/samba-4.5.0.html
=============== Parameter Name Description Default
-------------- ----------- -------
kccsrv:samba_kcc Changed default yes
ntlm auth Changed default no
only user Removed
password hash gpg key ids New
shadow:snapprefix New
shadow:delimiter New _GMT
smb2 leases Changed default yes
username Removed
4.4.0 => 4.4.1 !! YOU MUST READ THIS ONE !! ( lots changed here )
https://www.samba.org/samba/history/samba-4.4.1.html
smb.conf new settings
----------------
Parameter Name + default setting.
-------------
allow dcerpc auth level connect = no
client ipc signing = default
client ipc max protocol = default
client ipc min protocol = default
ldap server require strong auth = yes
raw NTLMv2 auth = no
tls verify peer = as_strict_as_possible
tls priority = NORMAL:-VERS-SSL3.0
4.3.0 => 4.4.0 : smb.conf changes
https://www.samba.org/samba/history/samba-4.4.0.html
smb.conf changes
----------------
Parameter Name Description Default
-------------- ----------- ------
aio max threads New 100
ldap page size Changed default 1000
server multi channel support New No
interfaces Extended syntax
4.2.0 => 4.3.0 : smb.conf changes
https://www.samba.org/samba/history/samba-4.3.0.html
smb.conf changes
----------------
Parameter Name Description Default
-------------- ----------- -------
logging New (empty)
msdfs shuffle referrals New no
smbd profiling level New off
spotlight New no
tls priority New NORMAL:-VERS-SSL3.0
use ntdb Removed
change notify Changed to [global]
kernel change notify Changed to [global]
client max protocol Changed default SMB3_11
server max protocol Changed default SMB3_11
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
> Jobst Schmalenbach via samba
> Verzonden: vrijdag 24 mei 2019 14:54
> Aan: samba at lists.samba.org
> Onderwerp: [Samba] Upgraded from CentOS 6.X to 7.X, samba not working
>
> Hi
>
> Previous: CentOS 6.X, samba4.x86_64 4.2.10-15.el6
> Now: CentOS 7.6.1810, samba 4.8.3-4.el7
>
> When I start smb, nmb or winbind I get no errors at all.
> This is all I get:
>
> May 24 22:44:04 HOST systemd[1]: Starting Samba SMB Daemon...
> May 24 22:44:05 HOST systemd[1]: smb.service: main process
> exited, code=exited, status=1/FAILURE
> May 24 22:44:05 HOST systemd[1]: Failed to start Samba SMB Daemon.
> May 24 22:44:05 HOST systemd[1]: Unit smb.service entered
> failed state.
> May 24 22:44:05 HOST systemd[1]: smb.service failed.
>
> Looking at the samba logs, they are all empty.
> The journal has not much info either.
>
> What the hell am I doing wrong?
> Are there massive changes between 4.2 and 4.8 that its not working?
>
> Help please, I have till Monday morning to get this sorted (weekend).
>
> jobst
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
>
>
Rowland penny
2019-May-24 13:48 UTC
[Samba] Upgraded from CentOS 6.X to 7.X, samba not working
On 24/05/2019 13:53, Jobst Schmalenbach via samba wrote:> Hi > > Previous: CentOS 6.X, samba4.x86_64 4.2.10-15.el6 > Now: CentOS 7.6.1810, samba 4.8.3-4.el7 > > When I start smb, nmb or winbind I get no errors at all. > This is all I get: > > May 24 22:44:04 HOST systemd[1]: Starting Samba SMB Daemon... > May 24 22:44:05 HOST systemd[1]: smb.service: main process exited, code=exited, status=1/FAILURE > May 24 22:44:05 HOST systemd[1]: Failed to start Samba SMB Daemon. > May 24 22:44:05 HOST systemd[1]: Unit smb.service entered failed state. > May 24 22:44:05 HOST systemd[1]: smb.service failed. > > Looking at the samba logs, they are all empty. > The journal has not much info either.Try turning up the logs, set 'log level =3' in smb.conf> > What the hell am I doing wrong?No idea, mainly because 'it worked with Samba 4.2 'isn't enough info, Can you post your smb.conf> Are there massive changes between 4.2 and 4.8 that its not working?There have been numerous changes, but whether that's the problem is unknown at this point ;-) Rowland
Jobst Schmalenbach
2019-May-24 21:07 UTC
[Samba] Upgraded from CentOS 6.X to 7.X, samba not working
On Fri, May 24, 2019 at 03:45:31PM +0200, L.P.H. van Belle via samba (samba at lists.samba.org) wrote:> You should have looked before upgrading. ... > If its an AD-DC. > instructions: https://lists.samba.org/mailman/options/sambaYes, very true! I really have "upgrading fatigue", this is my tenths bloody odd machine I am moving from 6.x to 7.x (all of those quite complicated servers) - but it is my first samba server. All the samba servers are internal servers unreachable from the outside, so loosing the updates of the OS was my least concern. I briefly researched samba a while back and did not expect a few minor version number changes make such a big difference. I also "expected" to have a variety of choices of Samba (as this had been the case for so many years) - e.g. older versions. One of the biggest issues I have faced doing my upgrades is not only the OS upgrade but nearly EVERY software package the OLD servers were using were upgraded, too, even if the package numbers did not differ that much - this was a major, major hassle especially making them stick with systemd and the libraries required to run it. I am so over this. It would have been nice to have an OLD version of Samba for CentOS 7.X - then to change this in a 1/2 year time once I upgraded the rest of the servers - JUST saying! thanks for the elaborate reading suggestions!!!!! Jobst -- Do Lipton Tea employees take coffee breaks? | |0| | Jobst Schmalenbach | | |0| |0|0|0| +61 3 9533 0000, POBox 277, Caulfield South, 3162, Australia
Jobst Schmalenbach
2019-May-27 00:26 UTC
[Samba] Upgraded from CentOS 6.X to 7.X, samba not working
On Fri, May 24, 2019 at 03:45:31PM +0200, L.P.H. van Belle via samba (samba at lists.samba.org) wrote:> You should have looked before upgrading. ...I actually did, I remember now (after I read your suggestions). On this page (https://wiki.samba.org/index.php/Updating_Samba) it actually says: If you update to Samba 4 and later, you do not have to migrate to Active Directory. That was enough for me at that time. I KNOW I have to update at some stage but in the moment I am getting conflicting messages. On the webpage it still says I can use old type NT domains. So is this still possible to runb NT style domains on the latest samba? My reasoning: I want to get all upgrades out of the way, then update samba ... Jobst -- Student to Teacher: Sir, what's an oxymoron? .... Teacher to Student: Microsoft security. | |0| | Jobst Schmalenbach, General Manager | | |0| Barrett & Sales Essentials |0|0|0| +61 3 9533 0000, POBox 277, Caulfield South, 3162, Australia
Seemingly Similar Threads
- Problem with mdadm, raid1 and automatically adds any disk to raid
- What files to edit when changing the sdX of hard drives?
- What files to edit when changing the sdX of hard drives?
- After reboot of web-server accessing website shows "Forbidden", restarting httpd all is fine
- Upgraded from CentOS 6.X to 7.X, samba not working