Samba is proving to be a problem for me as well. I was hoping to hit the forums and find a ton of people complaining about it, but I don't see the flood I was expecting, which means it may be something more specific to my setup (ntfs external drive). I've tried purging and reinstalling samba, but it's not having any effect. The install seems to have gone okay, but the configuration step failed with not a lot of detail given.
Checking on the status gets me this:
Code: Select all
�� smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled)
Active: failed (Result: core-dump) since Sat 2017-08-19 14:26:01 EDT; 34s ago
Main PID: 3232 (code=dumped, signal=SEGV)
Aug 19 14:26:01 RPHS systemd: smbd.service: main process exited, code=du...GV
Aug 19 14:26:01 RPHS systemd: Failed to start Samba SMB Daemon.
Aug 19 14:26:01 RPHS systemd: Unit smbd.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.
During the install, I saw these lines:
Code: Select all
Samba is not being run as an AD Domain Controller, masking samba-ad-dc-service.
Please ignore the following error about deb-systemd-helper not finding samba-ad-dc-service.
Job for smbd.service failed. See 'systemctl status smbd.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript smbd, action "start" failed.
dpkg: error processing package samba (--configure):
subprocess installed post-installation script returned error exit status 1
I'm inclined to think that the dpkg error is the result of samba-ad-dc-service not being found, since it comes immediately after the line telling me not to worry about the following error, but since it causes dpkg to fail during configuration, it's kind of a problem for me.
Is anyone else seeing this behavior?