thr3ads.net - samba - [Samba] samba.service is masked (Debian 9) [Jan 2019]

If this information is useful, please help other people find it:
Share via:

Anton Blau

2019-Jan-12 21:04 UTC

[Samba] samba.service is masked (Debian 9)

Hello,

please excuse my bad english. But I am not a native speaker.

I installed samba 4 (DC) like this description 
http://tobs.tips/_doc_/ProxMoxDoc/07samba/ on a new Debian 9 System.

After

* apt-get install samba

* service samba stop

* rm -f /etc/samba/smb.conf

* samba-tool domain provision --use-rfc2307 --use-xattrs=yes --interactive

with no error-massages I try to start samba 4 via "service samba
start".
But now I get the error message

Failed to start samba.service: Unit samba.service is masked.


What should tell me that?


Google finds that:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769714#10

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740942

But I didn´t understand it.


What is to do to run my samba 4 dc Server?


Thank you!


Tony

P. S. My System is a LXC Container based on Proxmox.

Rowland Penny

2019-Jan-12 22:08 UTC

head link

[Samba] samba.service is masked (Debian 9)

On Sat, 12 Jan 2019 22:04:50 +0100
Anton Blau via samba <samba at lists.samba.org> wrote:
> Hello,
> 
> please excuse my bad english. But I am not a native speaker.
> 
> I installed samba 4 (DC) like this description 
> http://tobs.tips/_doc_/ProxMoxDoc/07samba/ on a new Debian 9 System.
> 
> After
> 
> * apt-get install samba
> 
> * service samba stop
> 
> * rm -f /etc/samba/smb.conf
> 
> * samba-tool domain provision --use-rfc2307 --use-xattrs=yes
> --interactive
> 
> with no error-massages I try to start samba 4 via "service samba
> start". But now I get the error message
> 
> Failed to start samba.service: Unit samba.service is masked.
> 
> 
> What should tell me that?
> 
> 
> Google finds that:
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769714#10
> 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740942
> 
> But I didn´t understand it.
> 
> 
> What is to do to run my samba 4 dc Server?
> 
> 
> Thank you!
> 
> 
> Tony
> 
> P. S. My System is a LXC Container based on Proxmox.
> 
> 
Is this all you installed ? :

apt-get install samba

If so try reading this:

https://wiki.samba.org/index.php/Distribution-specific_Package_Installation

Is this basically your smb.conf ? :

[global]
  workgroup = SMBDOMAIN
  realm = SMBDOMAIN.LOCAL.COMASYS.CH
  netbios name = FILE
  server role = active directory domain controller
  dns forwarder = 192.168.0.220
  idmap_ldb:use rfc2307 = yes

  vfs objects = acl_xattr
  map acl inherit = yes
  store dos attributes = yes

  printing = bsd
  load printers = no
  printcap name = /dev/null
  disable spoolss = yes

[homes]
  comment = Home Directories
  browseable = yes
  read only = no
  create mask = 0700
  directory mask = 0700
  valid users = %S

[Daten]
  comment = Daten
  path = /var/lib/samba/MOUNT/Data
  read only = no
  browseable = yes

[netlogon]
  path = /var/lib/samba/sysvol/smbdomain./scripts
  read only = No
  browseable = No

[sysvol]
  path = /var/lib/samba/sysvol
  read only = No
  browseable = No

If it is, make it like this:

[global]
  workgroup = SMBDOMAIN
  realm = SMBDOMAIN.LOCAL.COMASYS.CH
  netbios name = FILE
  server role = active directory domain controller
  dns forwarder = 192.168.0.220
  idmap_ldb:use rfc2307 = yes

  printing = bsd
  load printers = no
  printcap name = /dev/null
  disable spoolss = yes

[home]
  comment = Home Directories
  path = /home/%D/%U
  read only = no

[Daten]
  comment = Daten
  path = /var/lib/samba/MOUNT/Data
  read only = no

[netlogon]
  path = /var/lib/samba/sysvol/smbdomain.local.comasys.ch/scripts
  read only = No

[sysvol]
  path = /var/lib/samba/sysvol
  read only = No

And the answer to your original question is, you have to start
samba-ad-dc not samba, this will start the samba deamon and this will
start the smbd and winbindd deamons. You might have to unmask
samba-ad-dc:

systemctl unmask samba-ad-dc

I would find a better howto, if I were you ;-)

Rowland

Anton Blau

2019-Jan-13 07:09 UTC

head link

[Samba] winbind failed to reset devices.list was: samba.service is masked (Debian 9)

Am 12.01.2019 um 23:08 schrieb Rowland Penny via samba:> On Sat, 12 Jan 2019 22:04:50 +0100
> Anton Blau via samba <samba at lists.samba.org> wrote:
>
> Is this all you installed ? :
> apt-get install samba
>
> If so try reading this:
>
> https://wiki.samba.org/index.php/Distribution-specific_Package_Installation
>
>Hello Rowland,


thank you for your help. I took a few steps further.

* I installed the additional needed packages like

https://wiki.samba.org/index.php/Distribution-specific_Package_Installation

apt-get install samba attr winbind krb5-config krb5-user

Default Kerberos version 5 realm: DUCK.LOCALLAN
Kerberos servers for your realm: fileserver localhost
Administrative server for your Kerberos realm: fileserver

But now the Installation of winbind crashes:


apt-get install -f winbind
Reading package lists... Done
Building dependency tree
Reading state information... Done
winbind is already the newest version (2:4.5.12+dfsg-2+deb9u4).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n]
Setting up winbind (2:4.5.12+dfsg-2+deb9u4) ...
Job for winbind.service failed because the control process exited with error
code.
See "systemctl status winbind.service" and "journalctl -xe"
for details.
invoke-rc.d: initscript winbind, action "start" failed.
* winbind.service - Samba Winbind Daemon
    Loaded: loaded (/lib/systemd/system/winbind.service; enabled; vendor preset:
enabled)
    Active: failed (Result: exit-code) since Sun 2019-01-13 07:01:45 UTC; 5ms
ago
      Docs: man:winbindd(8)
            man:samba(7)
            man:smb.conf(5)
   Process: 341 ExecStart=/usr/sbin/winbindd $WINBINDOPTIONS (code=exited,
status=1/FAILURE)
  Main PID: 341 (code=exited, status=1/FAILURE)

Jan 13 07:01:45 fileserver systemd[1]: Starting Samba Winbind Daemon...
Jan 13 07:01:45 fileserver systemd[1]: winbind.service: Main process exited,
code=exited, status=…AILURE
Jan 13 07:01:45 fileserver systemd[1]: Failed to start Samba Winbind Daemon.
Jan 13 07:01:45 fileserver systemd[1]: winbind.service: Unit entered failed
state.
Jan 13 07:01:45 fileserver systemd[1]: winbind.service: Failed with result
'exit-code'.
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package winbind (--configure):
  subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Errors were encountered while processing:
  winbind
E: Sub-process /usr/bin/dpkg returned an error code (1)

journalctl -xe

-- Unit winbind.service has begun starting up.
Jan 13 07:07:24 fileserver systemd[1]: init.scope: Failed to reset devices.list:
Operation not permitted
Jan 13 07:07:24 fileserver systemd[1]: user.slice: Failed to reset devices.list:
Operation not permitted
Jan 13 07:07:24 fileserver systemd[1]: system-getty.slice: Failed to reset
devices.list: Operation not p
Jan 13 07:07:24 fileserver systemd[1]: networking.service: Failed to reset
devices.list: Operation not p
Jan 13 07:07:24 fileserver systemd[1]: dev-.lxc-sys.mount: Failed to reset
devices.list: Operation not p
Jan 13 07:07:24 fileserver systemd[1]: systemd-remount-fs.service: Failed to
reset devices.list: Operati
Jan 13 07:07:24 fileserver systemd[1]: system-postfix.slice: Failed to reset
devices.list: Operation not
Jan 13 07:07:24 fileserver systemd[1]: dev-ptmx.mount: Failed to reset
devices.list: Operation not permi
Jan 13 07:07:24 fileserver systemd[1]: proc-stat.mount: Failed to reset
devices.list: Operation not perm
Jan 13 07:07:24 fileserver systemd[1]: systemd-update-utmp.service: Failed to
reset devices.list: Operat
Jan 13 07:07:24 fileserver systemd[1]: dev-tty2.mount: Failed to reset
devices.list: Operation not permi
Jan 13 07:07:24 fileserver systemd[1]: sys-fs-fuse-connections.mount: Failed to
reset devices.list: Oper
Jan 13 07:07:24 fileserver systemd[1]: proc-diskstats.mount: Failed to reset
devices.list: Operation not
Jan 13 07:07:24 fileserver systemd[1]: dev-tty1.mount: Failed to reset
devices.list: Operation not permi
Jan 13 07:07:24 fileserver systemd[1]: systemd-sysctl.service: Failed to reset
devices.list: Operation n
Jan 13 07:07:24 fileserver systemd[1]: ssh.service: Failed to reset
devices.list: Operation not permitte
Jan 13 07:07:24 fileserver systemd[1]: systemd-tmpfiles-setup.service: Failed to
reset devices.list: Ope
Jan 13 07:07:24 fileserver systemd[1]: systemd-logind.service: Failed to reset
devices.list: Operation n
Jan 13 07:07:24 fileserver systemd[1]: dev-.lxc-proc.mount: Failed to reset
devices.list: Operation not
Jan 13 07:07:24 fileserver systemd[1]: systemd-journal-flush.service: Failed to
reset devices.list: Oper
Jan 13 07:07:24 fileserver systemd[1]: systemd-user-sessions.service: Failed to
reset devices.list: Oper
Jan 13 07:07:24 fileserver systemd[1]: cron.service: Failed to reset
devices.list: Operation not permitt
Jan 13 07:07:24 fileserver systemd[1]: proc-meminfo.mount: Failed to reset
devices.list: Operation not p
Jan 13 07:07:24 fileserver systemd[1]: systemd-journald.service: Failed to reset
devices.list: Operation
Jan 13 07:07:24 fileserver systemd[1]: dev-mqueue.mount: Failed to reset
devices.list: Operation not per
Jan 13 07:07:24 fileserver systemd[1]: system-container\x2dgetty.slice: Failed
to reset devices.list: Op
Jan 13 07:07:24 fileserver systemd[1]: proc-cpuinfo.mount: Failed to reset
devices.list: Operation not p
Jan 13 07:07:24 fileserver systemd[1]: -.mount: Failed to reset devices.list:
Operation not permitted
Jan 13 07:07:24 fileserver systemd[1]: proc-sysrq\x2dtrigger.mount: Failed to
reset devices.list: Operat
Jan 13 07:07:24 fileserver systemd[1]: proc-uptime.mount: Failed to reset
devices.list: Operation not pe
Jan 13 07:07:24 fileserver systemd[1]: sys-devices-virtual-net.mount: Failed to
reset devices.list: Oper
Jan 13 07:07:24 fileserver systemd[1]: dev-hugepages.mount: Failed to reset
devices.list: Operation not
Jan 13 07:07:24 fileserver systemd[1]: proc-sys-net.mount: Failed to reset
devices.list: Operation not p
Jan 13 07:07:24 fileserver systemd[1]: dbus.service: Failed to reset
devices.list: Operation not permitt
Jan 13 07:07:24 fileserver systemd[1]: dev-fuse.mount: Failed to reset
devices.list: Operation not permi
Jan 13 07:07:24 fileserver systemd[1]: postfix.service: Failed to reset
devices.list: Operation not perm
Jan 13 07:07:24 fileserver systemd[1]: proc-swaps.mount: Failed to reset
devices.list: Operation not per
Jan 13 07:07:24 fileserver systemd[1]: rsyslog.service: Failed to reset
devices.list: Operation not perm
Jan 13 07:07:24 fileserver systemd[1]: console-getty.service: Failed to reset
devices.list: Operation no
Jan 13 07:07:24 fileserver systemd[1]: winbind.service: Main process exited,
code=exited, status=1/FAILU
Jan 13 07:07:24 fileserver systemd[1]: Failed to start Samba Winbind Daemon.
-- Subject: Unit winbind.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- Unit winbind.service has failed.
--
-- The result is failed.
Jan 13 07:07:24 fileserver systemd[1]: winbind.service: Unit entered failed
state.
Jan 13 07:07:24 fileserver systemd[1]: winbind.service: Failed with result
'exit-code'.



How can I get a solution for this problem?

My System is a LXC Container based on Proxmox.



Thank you!


Tony

L.P.H. van Belle

2019-Jan-14 08:17 UTC

head link

[Samba] samba.service is masked (Debian 9)

Hai, 

I suggest you read some of my howtos/tips. 

https://github.com/thctlo/samba4/tree/master/howtos 

https://downloads.van-belle.nl/samba4/Upgrade-info.txt 	<< a must read in
my opinion.
This tells you also why service samba start is not working. (3.) 


Greetz, 

Louis

> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Rowland Penny via samba
> Verzonden: zaterdag 12 januari 2019 23:08
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] samba.service is masked (Debian 9)
> 
> On Sat, 12 Jan 2019 22:04:50 +0100
> Anton Blau via samba <samba at lists.samba.org> wrote:
> 
> > Hello,
> > 
> > please excuse my bad english. But I am not a native speaker.
> > 
> > I installed samba 4 (DC) like this description 
> > http://tobs.tips/_doc_/ProxMoxDoc/07samba/ on a new Debian 9 System.
> > 
> > After
> > 
> > * apt-get install samba
> > 
> > * service samba stop
> > 
> > * rm -f /etc/samba/smb.conf
> > 
> > * samba-tool domain provision --use-rfc2307 --use-xattrs=yes
> > --interactive
> > 
> > with no error-massages I try to start samba 4 via "service samba
> > start". But now I get the error message
> > 
> > Failed to start samba.service: Unit samba.service is masked.
> > 
> > 
> > What should tell me that?
> > 
> > 
> > Google finds that:
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769714#10
> > 
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740942
> > 
> > But I didn´t understand it.
> > 
> > 
> > What is to do to run my samba 4 dc Server?
> > 
> > 
> > Thank you!
> > 
> > 
> > Tony
> > 
> > P. S. My System is a LXC Container based on Proxmox.
> > 
> > 
> 
> Is this all you installed ? :
> 
> apt-get install samba
> 
> If so try reading this:
> 
> https://wiki.samba.org/index.php/Distribution-specific_Package
> _Installation
> 
> Is this basically your smb.conf ? :
> 
> [global]
>   workgroup = SMBDOMAIN
>   realm = SMBDOMAIN.LOCAL.COMASYS.CH
>   netbios name = FILE
>   server role = active directory domain controller
>   dns forwarder = 192.168.0.220
>   idmap_ldb:use rfc2307 = yes
> 
>   vfs objects = acl_xattr
>   map acl inherit = yes
>   store dos attributes = yes
> 
>   printing = bsd
>   load printers = no
>   printcap name = /dev/null
>   disable spoolss = yes
> 
> [homes]
>   comment = Home Directories
>   browseable = yes
>   read only = no
>   create mask = 0700
>   directory mask = 0700
>   valid users = %S
> 
> [Daten]
>   comment = Daten
>   path = /var/lib/samba/MOUNT/Data
>   read only = no
>   browseable = yes
> 
> [netlogon]
>   path = /var/lib/samba/sysvol/smbdomain./scripts
>   read only = No
>   browseable = No
> 
> [sysvol]
>   path = /var/lib/samba/sysvol
>   read only = No
>   browseable = No
> 
> If it is, make it like this:
> 
> [global]
>   workgroup = SMBDOMAIN
>   realm = SMBDOMAIN.LOCAL.COMASYS.CH
>   netbios name = FILE
>   server role = active directory domain controller
>   dns forwarder = 192.168.0.220
>   idmap_ldb:use rfc2307 = yes
> 
>   printing = bsd
>   load printers = no
>   printcap name = /dev/null
>   disable spoolss = yes
> 
> [home]
>   comment = Home Directories
>   path = /home/%D/%U
>   read only = no
> 
> [Daten]
>   comment = Daten
>   path = /var/lib/samba/MOUNT/Data
>   read only = no
> 
> [netlogon]
>   path = /var/lib/samba/sysvol/smbdomain.local.comasys.ch/scripts
>   read only = No
> 
> [sysvol]
>   path = /var/lib/samba/sysvol
>   read only = No
> 
> And the answer to your original question is, you have to start
> samba-ad-dc not samba, this will start the samba deamon and this will
> start the smbd and winbindd deamons. You might have to unmask
> samba-ad-dc:
> 
> systemctl unmask samba-ad-dc
> 
> I would find a better howto, if I were you ;-)
> 
> Rowland
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
>

Maybe Matching Threads

Search for more maybe matching threads

samba - Jan 2019 - samba.service is masked (Debian 9)

[Samba] samba.service is masked (Debian 9)

[Samba] samba.service is masked (Debian 9)

[Samba] winbind failed to reset devices.list was: samba.service is masked (Debian 9)

[Samba] samba.service is masked (Debian 9)

Maybe Matching Threads