Am Fri, 30 Nov 2012 01:07:37 -0200 schrieb Clodonil Trigo: > Hi, > > I have a problem. After several tests with Samba4, put into production. > With one week working began to fill the files with HD / > usr/local/samba4/var/cores/smb. I went into that directory and deleted > some files to free up space. > > More Samba4 now no longer starts the ldap. When I start giving the > error: > > [root @ new-lost sbin] #. / samba-i-M single-d 1 Samba version > 4.1.0pre1-GIT-05a5974 started. > Copyright Andrew Tridgell and the Samba Team 1992-2012 samba: using > 'single' process model Started with smbd server config file / > usr/local/samba4-migracao/private/smbd.tmp/fileserver.conf Failed to > listen on 0.0.0.0:636 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED ldapsrv > failed to bind to 0.0.0.0:636 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED > task_server_terminate: [Failed to startup ldap server task] > / usr/local/samba4-migracao/sbin/smbd: smbd version > 4.1.0pre1-GIT-05a5974 started. > / usr/local/samba4-migracao/sbin/smbd: Copyright Andrew Tridgell and the > Samba Team 1992-2012 / usr/local/samba4-migracao/sbin/smbd: standard > input is not a socket, assuming-D option > ../source4/dsdb/dns/dns_update.c: 294: Failed DNS update - > NT_STATUS_UNSUCCESSFUL > > Any idea?
I would check with "netstat -nalp | grep 636" which process occupies the port 636. - Thomas -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba