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

[Andreas Hasenack]

Thanks for getting back to us.

I suspect at some point you thought that the right service to start was
samba-ad-dc, and you configured it like that, and forgot it. I also find
this confusing and hope someday we can have the "switch" between
services be automatic, depending on whether you want an AD server or
not.

Regarding your smb1 issues, it's not that samba won't negotiate using
smb2 or 3. It will. The problem is the network browsing, which relies on
smb1. Without smb1, you won't see the other windows/smb machines in the
network. But if you try to access them directly via their ips or
hostnames, the connection will work and smb2 or smb3 will be spoken just
fine. See https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1767454
for some details.

I'll leave this bug open as "incomplete". If it happens again, or if you
gather more details, then feel free to post them here. Otherwise, the
bug will auto-close in about 60 days.

Thanks!

-- 
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