hi @alefattorini , unfortunately i have troubles with setting up a nethserver-dc instance. I created a ns7 instance with webvirtmanager and updated it. everything worked perfectly. The installation of nethserv-dc-package itself worked also. But when i try to start the DC, the process stucks at “57% adjust-services”. Tried it serveral times. But always the same. 
I never had problems with containers on my VMs.
The screenshot above does not help. You can reset the nsdc state as documented here
http://docs.nethserver.org/projects/nethserver-devel/en/v7b/nethserver-dc.html#factory-reset
Are you allocating a free IP?
yes. I tried it with different ip.
hi @davidep and @alefattorini
sorry, but i give up!! Can’t figure out the problem. In the KVM-VM the DC-installation stucks at “57% adjusting services”. The KVM-VM is much slower than the Virtualboxmachine. I tried it three times and everytime the same. Also I had on both machines (kvm and vbox) the problem to create user. Only if I created the user without password and changed the password afterwards it worked. I think there is somewhere an issue with the authentication of users, because of the LDAP-server has the same ip as the KDC and both are not reachable from the Network, only from the CLI of the vm itself. It’s like the firewall drops traffic to nsdc, but that can’t be because of openfirewal settings and I disabled shorewall at all.
Thanks for listening to my problems and your try to help.
So long. Best regards Ralf
cc: @davidep, @giacomo, @alefattorini
I think I know where is the problem.
After you have installed the Samba AD package, is mandatory to reboot NS 7b1, before begin Samba AD configuration!
How I tested:
Test 1: twice on VirtualBox
Test 2: once on VirtualBox and once on a dedicated server
I cannot continue with tests on the dedicated server till I will not reinstall the NS 7b1 (but for this, I must to go at work and I’m in vacation).
Or, maybe there is a way to pass the errors. What do you think?
Thanks for pointing this out, @GG_jr and @flatspin !
Could you attach (some excerpts from) your log files? It would help investigating the origin of the error!
Apart from /var/log/messages that shows how an event proceeds, here would help also the output of nsdc container journal:
journalctl -M nsdcI did many test installations and the boot isn’t really necessary.
Surely it can solve some kind of situation, but the dc must work out-of-the-box after the installation, and all your tests are very valuable to us in finding all the bugs! 
I found only one issue on the DC: on a VM with a bridged interface, I can’t access the DC from other machines in the network. The same issue doesn’t apply on physical machine, so I would blame something in the network setup of my VMs.
thanks @giacomo this is exactly my problem. I’m working with a bridged interface on a virtualbox-vm. Did you find a workaround?
I still have the problem with epel repo. I have to disable mirrors and enable baseurl with vi editor after new install from iso. Otherwise update doesn’t work. Anyone else has this issue?
From dedicated server:
/var/log/messages: https://drive.google.com/open?id=0B1DQ23OY7TYkbzVYOXEzRDlpZ0k
journalctl -M nsdc: https://drive.google.com/open?id=0B1DQ23OY7TYka0VZM3lsbDV6UlU
If you need more log files, please tell me.
BR,
Gabriel
The “journalctl” link points to an “rpm -qa” output 
Sorry! Fixed!
I know that the reboot isn’t necessary.
After I’ve tried the two variants on VM, on dedicated server I did only Test 2 (without reboot) and look what has happened.
When I’ve tested Samba AD on NS 7a3, I didn’t have this issue.
( NethServer 7.2 alpha 3 - “First Blood” )
BR,
Gabriel
No I didn’t, but also I haven’t try hard 
But I will test it on a VMWare cluster later this week.
– Logs begin at Thu 2016-07-28 10:19:27 CEST, end at Thu 2016-07-28 10:32:35 CEST. –
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd-journal[12]: Runtime journal is using 8.0M (max allowed 91.9M, trying to leave 137.9M free of 911.8M available → current limit 91.9M).
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd-journal[12]: Permanent journal is using 8.0M (max allowed 1.7G, trying to leave 2.6G free of 15.5G available → current limit 1.7G).
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd-journal[12]: Time spent on flushing to /var is 1.133ms for 2 entries.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd-journal[12]: Journal started
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting Flush Journal to Persistent Storage…
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Started Rebuild Journal Catalog.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Started Flush Journal to Persistent Storage.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting Create Volatile Files and Directories…
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Started Create Volatile Files and Directories.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting Update UTMP about System Boot/Shutdown…
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Started Update UTMP about System Boot/Shutdown.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Started Rebuild Hardware Database.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Started udev Coldplug all Devices.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting Update is Completed…
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Started Update is Completed.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Reached target System Initialization.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting System Initialization.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Started Daily Cleanup of Temporary Directories.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting Daily Cleanup of Temporary Directories.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Reached target Timers.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting Timers.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Listening on D-Bus System Message Bus Socket.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting D-Bus System Message Bus Socket.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Reached target Sockets.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting Sockets.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Reached target Basic System.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting Basic System.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting Permit User Sessions…
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting Domain controller provisioning…
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Started D-Bus System Message Bus.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting D-Bus System Message Bus…
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting Network Service…
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting Login Service…
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Started Permit User Sessions.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Started Console Getty.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting Console Getty…
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Started Getty on tty1.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Reached target Login Prompts.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting Login Prompts.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd-networkd[25]: host0 : Cannot configure IPv4 forwarding for interface host0: Read-only file system
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd-networkd[25]: host0 : Cannot configure IPv6 forwarding for interface: Read-only file system
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd-networkd[25]: Enumeration completed
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Started Network Service.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Reached target Network.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Starting Network.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd[1]: Started Login Service.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd-logind[26]: New seat seat0.
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd-networkd[25]: host0 : gained carrier
Jul 28 10:19:27 nsdc-newns7.jeckel.loc systemd-networkd[25]: host0 : link configured
Jul 28 10:19:27 nsdc-newns7.jeckel.loc samba-tool[23]: Looking up IPv4 addresses
Jul 28 10:19:27 nsdc-newns7.jeckel.loc samba-tool[23]: Looking up IPv6 addresses
Jul 28 10:19:27 nsdc-newns7.jeckel.loc samba-tool[23]: No IPv6 address will be assigned
Jul 28 10:19:27 nsdc-newns7.jeckel.loc samba-tool[23]: Setting up share.ldb
Jul 28 10:19:27 nsdc-newns7.jeckel.loc samba-tool[23]: Setting up secrets.ldb
Jul 28 10:19:27 nsdc-newns7.jeckel.loc samba-tool[23]: Setting up the registry
Jul 28 10:19:27 nsdc-newns7.jeckel.loc samba-tool[23]: Setting up the privileges database
Jul 28 10:19:27 nsdc-newns7.jeckel.loc samba-tool[23]: Setting up idmap db
Jul 28 10:19:27 nsdc-newns7.jeckel.loc samba-tool[23]: Setting up SAM db
Jul 28 10:19:27 nsdc-newns7.jeckel.loc samba-tool[23]: Setting up sam.ldb partitions and settings
Jul 28 10:19:27 nsdc-newns7.jeckel.loc samba-tool[23]: Setting up sam.ldb rootDSE
Jul 28 10:19:27 nsdc-newns7.jeckel.loc samba-tool[23]: Pre-loading the Samba 4 and AD schema
Jul 28 10:19:27 nsdc-newns7.jeckel.loc samba-tool[23]: Adding DomainDN: DC=jeckel,DC=loc
Jul 28 10:19:27 nsdc-newns7.jeckel.loc samba-tool[23]: Adding configuration container
Jul 28 10:19:27 nsdc-newns7.jeckel.loc samba-tool[23]: Setting up sam.ldb schema
Jul 28 10:19:29 nsdc-newns7.jeckel.loc samba-tool[23]: Setting up sam.ldb configuration data
Jul 28 10:19:29 nsdc-newns7.jeckel.loc samba-tool[23]: Setting up display specifiers
Jul 28 10:19:30 nsdc-newns7.jeckel.loc samba-tool[23]: Modifying display specifiers
Jul 28 10:19:30 nsdc-newns7.jeckel.loc samba-tool[23]: Adding users container
Jul 28 10:19:30 nsdc-newns7.jeckel.loc samba-tool[23]: Modifying users container
Jul 28 10:19:30 nsdc-newns7.jeckel.loc samba-tool[23]: Adding computers container
Jul 28 10:19:30 nsdc-newns7.jeckel.loc samba-tool[23]: Modifying computers container
Jul 28 10:19:30 nsdc-newns7.jeckel.loc samba-tool[23]: Setting up sam.ldb data
Jul 28 10:19:30 nsdc-newns7.jeckel.loc samba-tool[23]: Setting up well known security principals
Jul 28 10:19:30 nsdc-newns7.jeckel.loc samba-tool[23]: Setting up sam.ldb users and groups
Jul 28 10:19:30 nsdc-newns7.jeckel.loc samba-tool[23]: Setting up self join
Jul 28 10:19:31 nsdc-newns7.jeckel.loc samba-tool[23]: Adding DNS accounts
Jul 28 10:19:31 nsdc-newns7.jeckel.loc samba-tool[23]: Creating CN=MicrosoftDNS,CN=System,DC=jeckel,DC=loc
Jul 28 10:19:31 nsdc-newns7.jeckel.loc samba-tool[23]: Creating DomainDnsZones and ForestDnsZones partitions
Jul 28 10:19:31 nsdc-newns7.jeckel.loc samba-tool[23]: Populating DomainDnsZones and ForestDnsZones partitions
Jul 28 10:19:32 nsdc-newns7.jeckel.loc samba-tool[23]: Setting up sam.ldb rootDSE marking as synchronized
Jul 28 10:19:32 nsdc-newns7.jeckel.loc samba-tool[23]: Fixing provision GUIDs
Jul 28 10:19:32 nsdc-newns7.jeckel.loc samba-tool[23]: A Kerberos configuration suitable for Samba 4 has been generated at /var/lib/samba/private/krb5.conf
Jul 28 10:19:32 nsdc-newns7.jeckel.loc samba-tool[23]: Once the above files are installed, your Samba4 server will be ready to use
Jul 28 10:19:32 nsdc-newns7.jeckel.loc samba-tool[23]: Server Role: active directory domain controller
Jul 28 10:19:32 nsdc-newns7.jeckel.loc samba-tool[23]: Hostname: nsdc-newns7
Jul 28 10:19:32 nsdc-newns7.jeckel.loc samba-tool[23]: NetBIOS Domain: JECKEL
Jul 28 10:19:32 nsdc-newns7.jeckel.loc samba-tool[23]: DNS Domain: jeckel.loc
Jul 28 10:19:32 nsdc-newns7.jeckel.loc samba-tool[23]: DOMAIN SID: S-1-5-21-228168602-692409205-3802379107
Jul 28 10:19:32 nsdc-newns7.jeckel.loc cp[33]: ‘/var/lib/samba/private/krb5.conf’ → ‘/etc/krb5.conf’
Jul 28 10:19:32 nsdc-newns7.jeckel.loc systemd[1]: Started Domain controller provisioning.
Jul 28 10:19:32 nsdc-newns7.jeckel.loc systemd[1]: Started Samba domain controller daemon.
Jul 28 10:19:32 nsdc-newns7.jeckel.loc systemd[1]: Starting Samba domain controller daemon…
Jul 28 10:19:32 nsdc-newns7.jeckel.loc systemd[1]: Reached target Multi-User System.
Jul 28 10:19:32 nsdc-newns7.jeckel.loc systemd[1]: Starting Multi-User System.
Jul 28 10:19:32 nsdc-newns7.jeckel.loc systemd[1]: Reached target Graphical Interface.
Jul 28 10:19:32 nsdc-newns7.jeckel.loc systemd[1]: Starting Graphical Interface.
Jul 28 10:19:32 nsdc-newns7.jeckel.loc systemd[1]: Started Stop Read-Ahead Data Collection 10s After Completed Startup.
Jul 28 10:19:32 nsdc-newns7.jeckel.loc systemd[1]: Starting Update UTMP about System Runlevel Changes…
Jul 28 10:19:32 nsdc-newns7.jeckel.loc systemd[1]: Started Update UTMP about System Runlevel Changes.
Jul 28 10:19:32 nsdc-newns7.jeckel.loc systemd[1]: Startup finished in 5.330s.
Jul 28 10:19:32 nsdc-newns7.jeckel.loc samba[35]: samba version 4.4.5 started.
Jul 28 10:19:32 nsdc-newns7.jeckel.loc samba[35]: Copyright Andrew Tridgell and the Samba Team 1992-2016
Jul 28 10:19:32 nsdc-newns7.jeckel.loc samba[35]: samba: using ‘standard’ process model
Jul 28 10:19:32 nsdc-newns7.jeckel.loc samba[35]: Attempting to autogenerate TLS self-signed keys for https for hostname ‘NSDC-NEWNS7.jeckel.loc’
Jul 28 10:19:32 nsdc-newns7.jeckel.loc winbindd[48]: [2016/07/28 10:19:32.783320, 0] …/source3/winbindd/winbindd_cache.c:3245(initialize_winbindd_cache)
Jul 28 10:19:32 nsdc-newns7.jeckel.loc winbindd[48]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
Jul 28 10:19:32 nsdc-newns7.jeckel.loc winbindd[48]: [2016/07/28 10:19:32.984216, 0] …/lib/util/become_daemon.c:124(daemon_ready)
Jul 28 10:19:32 nsdc-newns7.jeckel.loc winbindd[48]: STATUS=daemon ‘winbindd’ finished starting up and ready to serve connections
Jul 28 10:19:33 nsdc-newns7.jeckel.loc smbd[39]: [2016/07/28 10:19:33.076432, 0] …/lib/util/become_daemon.c:124(daemon_ready)
Jul 28 10:19:33 nsdc-newns7.jeckel.loc smbd[39]: STATUS=daemon ‘smbd’ finished starting up and ready to serve connections
Jul 28 10:19:34 nsdc-newns7.jeckel.loc samba[35]: TLS self-signed keys generated OK
Jul 28 10:19:46 nsdc-newns7.jeckel.loc systemd[1]: Started /usr/bin/samba-tool domain passwordsettings set --min-pwd-age=0 --max-pwd-age=180.
Jul 28 10:19:46 nsdc-newns7.jeckel.loc systemd[1]: Starting /usr/bin/samba-tool domain passwordsettings set --min-pwd-age=0 --max-pwd-age=180…
Jul 28 10:19:46 nsdc-newns7.jeckel.loc systemd[1]: Started /usr/bin/samba-tool domain passwordsettings show.
Jul 28 10:19:46 nsdc-newns7.jeckel.loc systemd[1]: Starting /usr/bin/samba-tool domain passwordsettings show…
Jul 28 10:19:46 nsdc-newns7.jeckel.loc systemd[1]: Started /usr/bin/samba-tool domain passwordsettings show.
Jul 28 10:19:46 nsdc-newns7.jeckel.loc systemd[1]: Starting /usr/bin/samba-tool domain passwordsettings show…
Jul 28 10:19:47 nsdc-newns7.jeckel.loc systemd[1]: Started /usr/bin/samba-tool domain passwordsettings set --complexity=on --history-length=default.
Jul 28 10:19:47 nsdc-newns7.jeckel.loc systemd[1]: Starting /usr/bin/samba-tool domain passwordsettings set --complexity=on --history-length=default…
Jul 28 10:19:58 nsdc-newns7.jeckel.loc systemd[1]: Starting Network Service…
Jul 28 10:19:58 nsdc-newns7.jeckel.loc systemd-networkd[89]: host0 : Cannot configure IPv4 forwarding for interface host0: Read-only file system
Jul 28 10:19:58 nsdc-newns7.jeckel.loc systemd-networkd[89]: host0 : Cannot configure IPv6 forwarding for interface: Read-only file system
Jul 28 10:19:58 nsdc-newns7.jeckel.loc systemd-networkd[89]: Enumeration completed
Jul 28 10:19:58 nsdc-newns7.jeckel.loc systemd-networkd[89]: host0 : link configured
Jul 28 10:19:58 nsdc-newns7.jeckel.loc systemd[1]: Started Network Service.
Jul 28 10:24:43 nsdc-newns7.jeckel.loc systemd[1]: Started /usr/bin/samba-tool user add jeckel --random-password --must-change-at-next-login --login-shell=/bin/bash --unix-home=/var/lib/nethserver/home/jeckel --given-name=Ralf Jeckel --use-username-as-cn.
Jul 28 10:24:43 nsdc-newns7.jeckel.loc systemd[1]: Starting /usr/bin/samba-tool user add jeckel --random-password --must-change-at-next-login --login-shell=/bin/bash --unix-home=/var/lib/nethserver/home/jeckel --given-name=Ralf Jeckel --use-username-as-cn…
Jul 28 10:24:44 nsdc-newns7.jeckel.loc systemd[1]: Started /usr/bin/samba-tool user setexpiry jeckel --noexpiry.
Jul 28 10:24:44 nsdc-newns7.jeckel.loc systemd[1]: Starting /usr/bin/samba-tool user setexpiry jeckel --noexpiry…
Jul 28 10:24:45 nsdc-newns7.jeckel.loc systemd[1]: Started /usr/bin/samba-tool user setpassword jeckel.
Jul 28 10:24:45 nsdc-newns7.jeckel.loc systemd[1]: Starting /usr/bin/samba-tool user setpassword jeckel…
Jul 28 10:24:45 nsdc-newns7.jeckel.loc systemd[1]: Started /usr/bin/samba-tool user enable jeckel.
Jul 28 10:24:45 nsdc-newns7.jeckel.loc systemd[1]: Starting /usr/bin/samba-tool user enable jeckel…
Jul 28 10:28:02 nsdc-newns7.jeckel.loc systemd[1]: Starting Cleanup of Temporary Directories…
Jul 28 10:28:02 nsdc-newns7.jeckel.loc systemd[1]: Started Cleanup of Temporary Directories.
Jul 28 10:32:13 nsdc-newns7.jeckel.loc systemd[1]: Started /usr/bin/pdbedit -w administrator.
Jul 28 10:32:13 nsdc-newns7.jeckel.loc systemd[1]: Starting /usr/bin/pdbedit -w administrator…
Jul 28 10:32:34 nsdc-newns7.jeckel.loc systemd[1]: Started /usr/bin/samba-tool user setpassword administrator.
Jul 28 10:32:34 nsdc-newns7.jeckel.loc systemd[1]: Starting /usr/bin/samba-tool user setpassword administrator…
Jul 28 10:32:35 nsdc-newns7.jeckel.loc systemd[1]: Started /usr/bin/samba-tool user enable administrator.
Jul 28 10:32:35 nsdc-newns7.jeckel.loc systemd[1]: Starting /usr/bin/samba-tool user enable administrator…
I did a complete new install from iso 7.2.1511. Then all updates. reboot. install nsdc. reboot. config ncds.
And this time I can create users with password.
So I think reboots are relevant at the moment.
But don’t ask me why…(It’s to early to g to the next whiskeybar, isn’t it?)
I still can not login with the user I created with ssh, altough I enabled ssh for the user. But this is becouse the LDAP isn’t reachable and so the system doesn’t know the user which was created with the GUI right?
Only the issue with bridged interface on vm is still present. But I’m not experienced enough to solve this. I have to wait until giacomo has the time to it.
BTW: how to make a scroll-window for the long journalctl output? @alefattorini did it once or twice in the past for me. Sorry for the long post.
@giacomo @davidep @alefattorini
I couldn’t give up and I found it. On Virtualbox machine I installed the vbox-guestadditions. To be able to install that, I had to install bzip2, gcc and kernel-devel. After that, I choosed the “Intel Pro/1000 MT Server” interface and set the promiscuous mode to “Allow All”. And suddenly my nsdc was reachable. 
I think it was all about promiscuous mode. I first set it to “Allow VMs”. Don’t know if the guest-additions had any influence.
I retrieved keberos credentials:
I also tried to join my Win 7 machine to the domain and it works also!
You definitively found the solution!
But the only thing requires is to set the network interface in promiscuous mode “Allow All”. It should work fine without guest additions installed: https://www.virtualbox.org/manual/ch06.html#network_performance
Following your suggestion, I can get it work also under vmware:
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004099 (Edit: previous links was wrong).
Still it doesn’t work on KVM, since i have different behaviors on Fedora 24 and 23. 
I found a way to make it work even on KVM:
ifconfig br0 promisc
I will soon add all info to the developer manual.
Added to the admin manual:
http://docs.nethserver.org/en/v7b/accounts.html#installing-on-a-virtual-machine
I ran some tests with KVM and host bridge interface. It didn’t need that step, it seems KVM sets “promisc” automatically wherever needed.
Just for the record, some links about bridges and VMs/containers