SCIENTIFIC-LINUX-USERS Archives

April 2016

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"~Stack~" <[log in to unmask]>
Reply To:
~Stack~
Date:
Wed, 13 Apr 2016 16:45:42 -0500
Content-Type:
multipart/signed
Parts/Attachments:
text/plain (2340 bytes) , signature.asc (834 bytes)
Greetings,

I am running SL6 on my Samba servers. I am in an environment where I am
required to apply security patches daily. Yum auto updates nearly all
security patches for me every morning (only a few things like the kernel
are excluded).

This morning we went from 3.6.23-25 to 3.6.23-30. Every thing broke. Not
a single server works.

Short recap that proves it is the update.
$ # restore everything from backup server
$ service nmb start; service smb start
$ # everything works.
$ service nmb stop; service smb stop
$ yum update -y --security --exclude=kernel*
# updates just 5 packages: samba, samba-client,
# samba-common, samba-winbind, and samba-winbind-clients
$ service nmb start; service smb start
# Nothing works.
$ service nmb stop; service smb stop
$ yum history undo $lastversion
$ service nmb start; service smb start
# Everything works again.

There is really not much in the logs at all from smb/nmb as to what is
going wrong. The client just gets a strange error about permissions
denied. However, in the log file for the client, we see things like
"Domain password server not available". There are occasional messages in
nmb logs about "current master browser = UNKNOWN" and
"find_domain_master_name_query_fail" but they are not easily reproducible.

1) It is amazing how many questions on the samba list don't get responses...

2) The vast majority of the responses I found on line didn't seem to work.

At one point, I scrapped my entire smb.conf file, wiped samba, and
restarted with the smb.conf file the new RPM provided. I still couldn't
get clients to connect.

Here is my smb.conf file that I restored from last night. It has been
working since May of 2014.

[global]
workgroup = MYWORKGROUP
server string = hostname
netbios name = hostname
log file = /var/log/samba/log.%m
max log size = 50
security = domain
password server = my.primary.domain.server
preferred master = no
wins support = no
wins server = my.primary.domain.server
wins proxy = yes
dns proxy = yes
load printers = yes
cups option = raw
restrict anonymous = 1
smb ports = 139
[homes]
comment = Home Directories
browsable = no
writeable = yes
valid users = %S

[ yes I know I am not supposed to use security=domain with password
server, but it works. Modifying either seems to make it not work]

Anyone else have horrific issues with this update??

Thanks!
~Stack~



ATOM RSS1 RSS2