Samba broken on fresh MX18

zimbodel · 03-10-2019, 11:03 PM

I guess this is for the package manager or person who packages MX.

On a default clean MX18 install, Samba fails to start.
Both through apt installation and the MX-PackageManager.

Here is the error output.

Do you want to continue? [Y/n] y
Setting up samba (2:4.5.16+dfsg-1) ...
Failed to preset unit: Unit file /etc/systemd/system/samba-ad-dc.service is masked.
/usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory
Job for smbd.service failed because the control process exited with error code.
See "systemctl status smbd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript smbd, action "start" failed.
● smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2019-03-10 23:58:07 EDT; 12ms ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Process: 28698 ExecStart=/usr/sbin/smbd $SMBDOPTIONS (code=exited, status=1/FAILURE)
Main PID: 28698 (code=exited, status=1/FAILURE)

Mar 10 23:58:07 Tango systemd[1]: Starting Samba SMB Daemon...
Mar 10 23:58:07 Tango systemd[1]: smbd.service: Main process exited, code=exited, status=1/FAILURE
Mar 10 23:58:07 Tango systemd[1]: Failed to start Samba SMB Daemon.
Mar 10 23:58:07 Tango systemd[1]: smbd.service: Unit entered failed state.
Mar 10 23:58:07 Tango systemd[1]: smbd.service: Failed with result 'exit-code'.
dpkg: error processing package samba (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Errors were encountered while processing:
samba
E: Sub-process /usr/bin/dpkg returned an error code (1)

sidzen · 03-11-2019, 07:37 AM

Here's a hint:
https://forum.mxlinux.org/viewtopic.php?t=45667
Best wishesfor a good linux experience!

zimbodel · 03-13-2019, 01:37 PM

Thank you, yes you are correct, it is systemd. What a bunch of irresponsible crap.

I will have to migrate all my servers to systemd-free options.

For anyone having systemd battles and problems with Debian and such, here is a good article to help you switch to something that wont byte you as bad as Debian and its derivatives such as MX18 currently does.

https://www.makeuseof.com/tag/debian...ystemd-devuan/

Quote:

Originally Posted by sidzen

Here's a hint:
https://forum.mxlinux.org/viewtopic.php?t=45667
Best wishesfor a good linux experience!

dolphin_oracle · 03-13-2019, 08:42 PM

also, a fresh install of MX comes with samba installed already, and runs just fine under sysVinit (the default startup).

Code:

┌─[dolphin@mx]─[09:42:02 pm]─────────────────────────────────────────────────────────────────────[~]
└─> sudo dpkg-reconfigure samba
[ ok ] Stopping Samba AD DC daemon: samba.
[ ok ] Stopping NetBIOS name server: nmbd.
[ ok ] Stopping SMB/CIFS daemon: smbd.
Failed to preset unit, unit /etc/systemd/system/samba-ad-dc.service is masked.
/usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory
[ ok ] Starting SMB/CIFS daemon: smbd.
[ ok ] Starting NetBIOS name server: nmbd.

┌─[dolphin@mx]─[09:42:21 pm]─────────────────────────────────────────────────────────────────────[~]
└─>

the systemd message doesn't matter because I'm not using systemd. however samaba is running just fine (smbd)

Code:

┌─[dolphin@mx]─[09:43:28 pm]─────────────────────────────────────────────────────────────────────[~]
└─> ps -aux |grep smbd
root     18573  0.0  0.1 353460 15000 ?        Ss   21:42   0:00 /usr/sbin/smbd -D
root     18575  0.0  0.0 345356  5696 ?        S    21:42   0:00 /usr/sbin/smbd -D
root     18577  0.0  0.0 345348  4432 ?        S    21:42   0:00 /usr/sbin/smbd -D
root     18595  0.0  0.0 353468  6508 ?        S    21:42   0:00 /usr/sbin/smbd -D
dolphin  18779  0.0  0.0  48060   972 pts/1    S+   21:43   0:00 grep smbd

zimbodel · 03-13-2019, 11:47 PM

I did
dpkg --purge samba
and an
apt remove samba

When I install again it fails as I reported.
This is a fresh MX install, I did not change to systemd, but somehow installing other software seems to start activating it as they depend on it and dont tell you that systemd is started.

When you try to uninstall systemd, then you see all the culprits needing it.
Go figure even mx-installer mx-repo-manager.

And even more hillarious,
"The following NEW packages will be installed:
sysvinit-core"

Clearfly MX18 is not out of the box sysv, although they swear by it.

# apt remove systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
brasero-common gazelle-installer-data-mx gir1.2-polkit-1.0 grub-efi-ia32-bin libbrasero-media3-1
libcolorhug2 libcrack2 libpwquality-common libpwquality1 pptp-linux
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
sysvinit-core
The following packages will be REMOVED:
brasero colord fskbsetting gnome-disk-utility gufw gvfs gvfs-backends gvfs-daemons gvfs-fuse k3b
libpam-systemd mx-installer mx-repo-manager nautilus network-manager network-manager-gnome
network-manager-openconnect network-manager-pptp network-manager-vpnc policykit-1
policykit-1-gnome rtkit synaptic systemd systemd-sysv systemd-ui udisks2
The following NEW packages will be installed:
sysvinit-core
0 upgraded, 1 newly installed, 27 to remove and 0 not upgraded.
Need to get 135 kB of archives.
After this operation, 61.3 MB disk space will be freed.
Do you want to continue? [Y/n]

dolphin_oracle · 03-14-2019, 05:31 AM

well yeah, if you uninstall systemd you will find issues. MX does not purport to be systemd-free (you might be thinking of antiX which does).

but I thought this thread was about samba on a fresh install. both sysVinit and systemd are installed by default on MX. systemd-shim is utilized. this lets us do things like still use the logind dameon, systemd-udev, libpam-systemd and other things from the debian repos, which many other items do require, including samba.

I utilized your procedure for samba removal. the systemd warnings do not apply on a default install of MX since systemd is not used as the default init. Note there are also sysVinit success messages.

Code:

┌─[dolphin@mx]─[06:18:32 am]─────────────────────────────────────────────────────────────────────[~]
└─> sudo apt-get purge samba
[sudo] password for dolphin: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libuser1 python-dnspython python-libuser python-smbc
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  samba* system-config-samba*
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
After this operation, 20.7 MB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 366978 files and directories currently installed.)
Removing system-config-samba (1.2.63-1mx17+1) ...
Removing samba (2:4.5.16+dfsg-1) ...
[ ok ] Stopping Samba AD DC daemon: samba.
[ ok ] Stopping NetBIOS name server: nmbd.
[ ok ] Stopping SMB/CIFS daemon: smbd.
Processing triggers for mime-support (3.60) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for gnome-menus (3.13.3-9) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...
(Reading database ... 365594 files and directories currently installed.)
Purging configuration files for samba (2:4.5.16+dfsg-1) ...
Processing triggers for ufw (0.35-4) ...
Processing triggers for systemd (232-25+deb9u9) ...

┌─[dolphin@mx]─[06:18:50 am]─────────────────────────────────────────────────────────────────────[~]
└─> sudo apt-get install samba
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libuser1 python-libuser python-smbc
Use 'sudo apt autoremove' to remove them.
Suggested packages:
  bind9 bind9utils ctdb ldb-tools smbldap-tools winbind
Recommended packages:
  attr samba-dsdb-modules samba-vfs-modules
The following NEW packages will be installed:
  samba
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/934 kB of archives.
After this operation, 11.2 MB of additional disk space will be used.
Selecting previously unselected package samba.
(Reading database ... 365584 files and directories currently installed.)
Preparing to unpack .../samba_2%3a4.5.16+dfsg-1_amd64.deb ...
Unpacking samba (2:4.5.16+dfsg-1) ...
Processing triggers for ufw (0.35-4) ...
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Processing triggers for systemd (232-25+deb9u9) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up samba (2:4.5.16+dfsg-1) ...
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.
Created symlink /etc/systemd/system/multi-user.target.wants/nmbd.service → /lib/systemd/system/nmbd.service.
Failed to preset unit, unit /etc/systemd/system/samba-ad-dc.service is masked.
/usr/bin/deb-systemd-helper: error: systemctl preset failed on samba-ad-dc.service: No such file or directory
Created symlink /etc/systemd/system/multi-user.target.wants/smbd.service → /lib/systemd/system/smbd.service.
[ ok ] Starting SMB/CIFS daemon: smbd.
[ ok ] Starting NetBIOS name server: nmbd.
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Processing triggers for systemd (232-25+deb9u9) ...
Processing triggers for ufw (0.35-4) ...

┌─[dolphin@mx]─[06:19:02 am]─────────────────────────────────────────────────────────────────────[~]
└─> ps -aux |grep samba
dolphin   5295  0.0  0.0  48060  1020 pts/0    S+   06:19   0:00 grep samba

┌─[dolphin@mx]─[06:19:13 am]─────────────────────────────────────────────────────────────────────[~]
└─> ps -aux |grep smbd
root      4943  0.0  0.1 353460 15300 ?        Ss   06:19   0:00 /usr/sbin/smbd -D
root      4945  0.0  0.0 345356  5752 ?        S    06:19   0:00 /usr/sbin/smbd -D
root      4947  0.0  0.0 345348  4516 ?        S    06:19   0:00 /usr/sbin/smbd -D
root      4960  0.0  0.0 353468  6620 ?        S    06:19   0:00 /usr/sbin/smbd -D
dolphin   5322  0.0  0.0  48060   956 pts/0    S+   06:19   0:00 grep smbd

┌─[dolphin@mx]─[06:19:17 am]─────────────────────────────────────────────────────────────────────[~]
└─>

and of course, as to whether sysVinit is installed by default...

Code:

┌─[dolphin@mx]─[06:19:17 am]─────────────────────────────────────────────────────────────────────[~]
└─> apt-cache policy sysvinit-core
sysvinit-core:
  Installed: 2.88dsf-59.9
  Candidate: 2.88dsf-59.9
  Version table:
 *** 2.88dsf-59.9 500
        500 http://ftp.us.debian.org/debian stretch/main amd64 Packages
        100 /var/lib/dpkg/status

┌─[dolphin@mx]─[06:26:44 am]─────────────────────────────────────────────────────────────────────[~]
└─> apt-cache policy systemd-shim
systemd-shim:
  Installed: 10-3
  Candidate: 10-3
  Version table:
 *** 10-3 500
        500 http://ftp.us.debian.org/debian stretch/main amd64 Packages
        100 /var/lib/dpkg/status

┌─[dolphin@mx]─[06:26:50 am]─────────────────────────────────────────────────────────────────────[~]
└─> apt-cache policy systemd
systemd:
  Installed: 232-25+deb9u9
  Candidate: 232-25+deb9u9
  Version table:
 *** 232-25+deb9u9 500
        500 http://security.debian.org stretch/updates/main amd64 Packages
        100 /var/lib/dpkg/status
     232-25+deb9u8 500
        500 http://ftp.us.debian.org/debian stretch/main amd64 Packages

┌─[dolphin@mx]─[06:26:55 am]─────────────────────────────────────────────────────────────────────[~]
└─>

zimbodel · 03-14-2019, 11:51 AM

Thank you for confirming this.
If as you say MX18 cannot really function properly without systemd then it is the end of the road for me with the distro as it will not help with what I need.
Regarding your samba comment: Systemd is at the heart of the samba problems, so that is why it is in the same thread.

Good info thanks.

[QUOTE=dolphin_oracle;5973729]well yeah, if you uninstall systemd you will find issues. MX does not purport to be systemd-free (you might be thinking of antiX which does).

but I thought this thread was about samba on a fresh install. both sysVinit and systemd are installed by default on MX. systemd-shim is utilized. this lets us do things like still use the logind dameon, systemd-udev, libpam-systemd and other things from the debian repos, which many other items do require, including samba.
[QUOTE]