Re: SAMBA 4 + AD

2017-08-08 Por tema JAP

El 07/08/17 a las 18:27, Luis Ernesto Garcia Reyes escribió:
Error loading module '/usr/lib/x86_64-linux-gnu/samba/vfs/acl_xattr.so': 
/usr/lib/x86_64-linux-gnu/samba/vfs/acl_xattr.so: cannot open shared 
object file: No such file or directory



Es un "bug" por falta de instalación de dependencias.
JAP

===

https://bugs.launchpad.net/ubuntu/+source/samba4/+bug/1091348


Error loading module 
'/usr/lib/x86_64-linux-gnu/samba//vfs/acl_xattr.so': 
/usr/lib/x86_64-linux-gnu/samba//vfs/acl_xattr.so: cannot open shared 
object file: No such file or directory

Bug #1091348 reported by Bruno Bigras on 2012-12-17
50
This bug affects 10 people
Affects Status  Importance  Assigned to Milestone
​   samba4 (Debian) Fix ReleasedUnknown 
debbugs #696838
​   samba4 (Ubuntu) Confirmed   Undecided   Unassigned  
Also affects project (?) Also affects distribution/package Nominate for 
series

Bug Description

When installing samba 4 on 13.04, I got :

Error loading module 
'/usr/lib/x86_64-linux-gnu/samba//vfs/acl_xattr.so': 
/usr/lib/x86_64-linux-gnu/samba//vfs/acl_xattr.so: cannot open shared 
object file: No such file or directory


ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: samba4 4.0.0+dfsg1-1
ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
Uname: Linux 3.7.0-7-generic x86_64
ApportVersion: 2.7-0ubuntu2
Architecture: amd64
Date: Mon Dec 17 11:58:26 2012
InstallationDate: Installed on 2012-12-17 (0 days ago)
InstallationMedia: Ubuntu-Server 13.04 "Raring Ringtail" - Alpha amd64 
(20121217)

MarkForUpload: True
ProcEnviron:
 LANGUAGE=fr_CA:fr
 TERM=screen
 PATH=(custom, no user)
 LANG=fr_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: samba4
UpgradeStatus: No upgrade log present (probably fresh install)

Tags: amd64 apport-bug raring Edit Tag help
Bruno Bigras (brunoqc) wrote on 2012-12-17: #1
Dependencies.txt Edit (4.6 KiB, text/plain; charset="utf-8")
Bruno Bigras (brunoqc) wrote on 2012-12-17: #2
apt term.log Edit (21.1 KiB, text/plain)
Here's the term.log I got when running :

bbigras@ubuntu-raring:~$ sudo apt-get install samba4
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  bind9 bind9utils ldb-tools libdcerpc-server0 libdcerpc0 libgensec0 
libhdb9-heimdal libkdc2-heimdal libldb1 libndr-standard0 libndr0
  libregistry0 libsamba-credentials0 libsamba-hostconfig0 
libsamba-policy0 libsamba-util0 libsamdb0 libsmbclient-raw0 libtalloc2 
libtdb1
  libtevent0 libwbclient0 python-ldb python-samba python-talloc 
python-tdb samba-common samba-common-bin samba-dsdb-modules 
samba4-common-bin

  tdb-tools
Suggested packages:
  bind9-doc phpldapadmin samba-gtk swat2 ntp
The following NEW packages will be installed:
  bind9 bind9utils ldb-tools libdcerpc-server0 libdcerpc0 libgensec0 
libhdb9-heimdal libkdc2-heimdal libldb1 libndr-standard0 libndr0
  libregistry0 libsamba-credentials0 libsamba-hostconfig0 
libsamba-policy0 libsamba-util0 libsamdb0 libsmbclient-raw0 libtalloc2 
libtdb1
  libtevent0 libwbclient0 python-ldb python-samba python-talloc 
python-tdb samba-common samba-common-bin samba-dsdb-modules samba4

  samba4-common-bin tdb-tools
0 upgraded, 32 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/13.9 MB of archives.
After this operation, 59.1 MB of additional disk space will be used.
Do you want to continue [Y/n]?

Launchpad Janitor (janitor) wrote on 2012-12-20:#3
Status changed to 'Confirmed' because the bug affects multiple users.

Changed in samba4 (Ubuntu):
status: New → Confirmed
Bug Watch Updater (bug-watch-updater) on 2012-12-31
Changed in samba4 (Debian):
status: Unknown → Confirmed
Thomas Hood (jdthood) on 2013-01-24
Changed in samba4 (Ubuntu):
status: Confirmed → Incomplete
status: Incomplete → Confirmed
Thomas Hood (jdthood) wrote on 2013-01-24:  #6
Another log showing these messages: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697105


Nick Semenkovich (semenko) wrote on 2013-01-27: #7
I also had this issue, though only after removing samba4 (aptitude purge 
samba4) and reinstalling, due to bug #1096791


The same error appears 20 or so times during the install, although 
samba4 appears to be running:


Error loading module 
'/usr/lib/x86_64-linux-gnu/samba//vfs/acl_xattr.so': 
/usr/lib/x86_64-linux-gnu/samba//vfs/acl_xattr.so: cannot open shared 
object file: No such file or directory

error probing vfs module 'acl_xattr': NT_STATUS_UNSUCCESSFUL

Bug Watch Updater (bug-watch-updater) on 2013-10-13
Changed in samba4 (Debian):
status: Confirmed → Fix Released
Andy Igoshin (andy-igoshin) wrote on 2013-11-05:#8
Download full text (15.5 KiB)
the same for 13.10

-

# aptitude install samba4
The following NEW packages will be installed:
  attr{a} bind9{a} 

SAMBA 4 + AD

2017-08-07 Por tema Luis Ernesto Garcia Reyes
Saludos me dispongo a Instalar Samba4 como Directorio Activo.

 

Luego de instalar toda la paqueteria y ejecutar

--- samba-tool domain provision

Me mustra los siguietes errores:

 

Error loading module '/usr/lib/x86_64-linux-gnu/samba/vfs/acl_xattr.so': 
/usr/lib/x86_64-linux-gnu/samba/vfs/acl_xattr.so: cannot open shared object 
file: No such file or directory

error probing vfs module 'acl_xattr': NT_STATUS_UNSUCCESSFUL

smbd_vfs_init: vfs_init_custom failed for acl_xattr create_conn_struct: 
smbd_vfs_init failed.

ERROR(runtime): uncaught exception - (-1073741633, 'The network is busy.')

  File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line 175, 
in _run

return self.run(*args, **kwargs)

  File "/usr/lib/python2.7/dist-packages/samba/netcmd/domain.py", line 434, in 
run

nosync=ldap_backend_nosync, ldap_dryrun_mode=ldap_dryrun_mode)

  File "/usr/lib/python2.7/dist-packages/samba/provision/__init__.py", line 
2169, in provision

skip_sysvolacl=skip_sysvolacl)

  File "/usr/lib/python2.7/dist-packages/samba/provision/__init__.py", line 
1803, in provision_fill

names.domaindn, lp, use_ntvfs)

  File "/usr/lib/python2.7/dist-packages/samba/provision/__init__.py", line 
1546, in setsysvolacl

smbd.set_simple_acl(file.name, 0755, gid)

 

 

He tratado de buscar la solucion pero no tengo internet.

Saludos desde CUBA