Samba4 get stuck after a server reboot, if IPv6 is enabled.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
samba |
Unknown
|
Unknown
|
|||
samba (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Guys,
I'm trying to deploy Samba4 AD DC with IPv6 and I'm facing a hard time (LP #1335502)... First, it didn't worked "as-is", now, after enabling IPv6 in Samba4 AD DC, it does not come up after a server reboot, it get stucked, look:
---
root@ubuntu-ad-1:~# host -t SRV _ldap._
_ldap._
root@ubuntu-ad-1:~# reboot
Broadcast message from administrativo@
(/dev/pts/2) at 22:10 ...
The system is going down for reboot NOW!
root@ubuntu-ad-1:~# Connection to 192.168.15.221 closed by remote host.
Connection to 192.168.15.221 closed.
--
tmartins@zion:~$ ssh administrativo@
administrativo@
Welcome to Ubuntu 14.04 LTS (GNU/Linux 3.13.0-30-generic x86_64)
* Documentation: https:/
Last login: Tue Jul 8 22:09:22 2014 from 192.168.0.104
administrativo@
[sudo] password for administrativo:
root@ubuntu-ad-1:~# host -t SRV _ldap._
Host _ldap._
root@ubuntu-ad-1:~#
---
Then, I tried:
---
root@ubuntu-ad-1:~# pidof samba
675
root@ubuntu-ad-1:~# pidof smbd
791 719
root@ubuntu-ad-1:~# host -t SRV _ldap._
Host _ldap._
---
See it?!
Now I'm doing:
---
root@ubuntu-ad-1:~# ps xfa
....
461 ? S 0:00 avahi-daemon: running [ubuntu-ad-1.local]
462 ? S 0:00 \_ avahi-daemon: chroot helper
675 ? S 0:00 samba -D
719 ? Ss 0:00 \_ /usr/sbin/smbd -D --option=server role check:inhibit=yes --f
791 ? S 0:00 \_ /usr/sbin/smbd -D --option=server role check:inhibit=yes
728 ? Ss 0:00 /usr/sbin/
745 ? S 0:00 upstart-file-bridge --daemon
....
---
So, samba is stucked, I'm not seeing the others "samba" child process as usual, then I tried:
---
root@ubuntu-ad-1:~# service samba-ad-dc stop
stop: Unknown instance:
root@ubuntu-ad-1:~# killall samba smbd
root@ubuntu-ad-1:~#
root@ubuntu-ad-1:~# service samba-ad-dc start
samba-ad-dc start/running, process 1446
root@ubuntu-ad-1:~# host -t SRV _ldap._
_ldap._
---
Back online!!
I believe that there is something wrong with the Samba4 init scripts when we have IPv6 enabled.
Cheers!
Thiago
description: | updated |
BTW, if in an IPv4-Only environment, then "Samba4 AD DC" works okay after rebooting the server. This problem appear only in a Dual-Stacked (not tried it in a IPv6-Only network) env.