[Bug 1776576] Re: Ubuntu 18.04 uograde: samba fails to run

[C. Jeffery Small]

Sorry for the delay in responding.  Everything is finally resolved.
Here is what I found.

The Ubuntu OS was upgraded for a week and the system was rebooted
multiple times before I noticed the samba problem.  At that point, in
addition to trying to start the samba-ad-dc service, I also had tried
manually to start smbd and nmbd multiple times and received similar
error messages with a failure of either starting.  Since the services
were not running there was no output in the /var/log/samba log files.
Running testparm was showing no problems other than the unimportant
warnings:

    rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
    WARNING: The "syslog" option is deprecated

neither of which should cause any problem. I do not believe that I
changed anything significant, yet upon another system reboot both smbd
and nmbd services started automatically and they continue to run
properly upon subsequent reboots.  I'm afraid I cannot explain why this
is the case.  Things like this are usually user error, but I cannot
identify what may have been the problem.

Now, the Ubuntu system could see the samba and external Windows shares.
However, the Windows 10 machines could not see the samba server!  This
turned out to be due to a recent push of Windows 10 version 1803 which
changed smb behavior by disabling the SMBv1 protocol, supporting only v2
and v3 by default.  Now, why samba could not negotiate using these
protocols is unclear, but the workaround was to re-enable SMBv1 on the
Windows 10 machines, at which point they could negotiate with samba once
again.  A second difficulty was that it was impossible to connect to the
samba server using the normal username and password that had worked in
the past.  The only solution I was able to discover was that the
connection had to be established with hostname\username rather than
username alone.  Then everything was back to normal.

Someone may want to take a look at Windows 10 v1803 to see how it is
interacting with the standard samba configuration.  In the future
Microsoft may eliminate support for SMBv1 altogether.

Sorry I don't have anything more definitive as to why smbd/nmbd were not
running, but I really appreciate the feedback and support.  Let me know
if I can provide any additional useful information.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1776576

Title:
  Ubuntu 18.04 uograde: samba fails to run

Status in samba package in Ubuntu:
  Incomplete

Bug description:
  Samba has been running properly in all previous version of Xubuntu up
  through 17.10 with server role = standalone.

  After the 18.04 upgrade, all samba services fail to start as noted
  below.  numerous changes were made, including advice from the net to
  add "client max protocol = NT1" to smb.conf, all with no success.

  A last-ditch attempt to reinstall the samba 2:4.7.6+dfsg~ubuntu-
  0ubuntu2 from synaptic fails with the pop-up error message:

  E: samba: installed samba package post-installation script subprocess
  returned error exit status 1

  The log output is attached.

  An attempt to start the samba service:

  # service  samba-ad-dc start
  Job for samba-ad-dc.service failed because the control process exited with error code.
  See "systemctl status samba-ad-dc.service" and "journalctl -xe" for details.

  # systemctl status samba-ad-dc.service
  ● samba-ad-dc.service
     Loaded: masked (/dev/null; bad)
     Active: failed (Result: exit-code) since Tue 2018-06-12 15:34:02 PDT; 17min ago
   Main PID: 27780 (code=exited, status=1/FAILURE)
     Status: "daemon failed to start: Samba detected misconfigured 'server role' and exited. Check logs for details"

  Jun 12 15:34:02 dymaxion.cjsa2.com systemd[1]: Starting Samba AD Daemon...
  Jun 12 15:34:02 dymaxion.cjsa2.com samba[27780]: handle_name_resolve_order: WARNING: Ignoring invalid list value '
  Jun 12 15:34:02 dymaxion.cjsa2.com systemd[1]: samba-ad-dc.service: Main process exited, code=exited, status=1/FAI
  Jun 12 15:34:02 dymaxion.cjsa2.com systemd[1]: samba-ad-dc.service: Failed with result 'exit-code'.
  Jun 12 15:34:02 dymaxion.cjsa2.com systemd[1]: Failed to start Samba AD Daemon.

  # A second (and subsequent) attempt to start samba:

  # service samba-ad-dc start
  Failed to start samba-ad-dc.service: Unit samba-ad-dc.service is masked.

  I tried a number of options to unmask and start the samba services
  with no success.

  Many people seem to be having great difficulty with samba now, but I
  located no clear instructions for addressing the problem which seems
  might be related to the active directory component.

  I would expect an upgrade to a properly configured system to continue
  to run.  I'm guessing that there is a fundamental configuration
  problem here, but possibly a deeper level bug.  I will also attach the
  smb.conf. file to this report.  Guidance is appreciated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1776576/+subscriptions