similar to: Samba 4 selftest errors

Thanks for the reply, Besides the problem with source4/lib/messaging/messaging_handlers.c, Good to hear that selftest is actively used, then do I understand it right that 'make test' should succeed? My bigger problem is that it failed with lots of errors. This must be a problem with my build, then, but since this is a fresh tarball I am a bit puzzled. I would appreciate some hint on

Greetings - On a RHEL6 system, Samba 4.2.1 compiles without any apparent problems but 'make quicktest' reports an error: FAILED (1 failures, 0 errors and 0 unexpected successes in 1 testsuites) A summary with detailed information can be found in: ./st/summary test: running (/usr/bin/perl /var/tmp/samba-4.2.1/selftest/selftest.pl --target=samba --prefix=./st

In the hope for some help, I would like some hint on how to diagnose the following single subunit: samba3.blackbox.smbclient_machine_auth.plain In particular the single test samba3.blackbox.smbclient_machine_auth.plain (s4member:local)(s4member:local) Results attached, run is from git at 'origin/v4-10-stable' Thanks in advance (This is because in my full selftest almost all failures

Hello All, I'm trying to contribute with my tests and continuous attempts to install and stress-test samba, but it gets really sad and frustrating finding out that no one answers. I know a lot of "we do this for free", "we do this in our free time", "wait longer for an answer" and that will come, save some typing and please, do not reply with that. I've

Village idiot here again. Thank you for your replies. Really. As for the acl_xattr.so: I was trying a new 'out of the box' install. I have done the whole download source/compile/provision bit on a Mint 17.1 and I am getting much farther.Now I get 'cannot find kdc for realm "ozco.home" while getting initial credentials" when I try kinit. About Kerberos. You advised me

HI. village idiot here. I have tried to set up Samba4 servers on several distros that have it preinstalled. this week. Mint, OpenSuse, and Ubuntu server all fail during domain provisioning with the message 'error loading ...acl_xattr.so: cannot open...No such file or directory. I have changed etc/fstab to include user_xattr and acl. What in the wild, wild world of sports is going on? -jimc

Hi! My Samba 4 system seems to be running reasonably well, but... I am getting the following error: TSIG error with servier: tsig verify failure Faied nsupdate: 2 yadda, yadda. This is from the command *samba_dnsupdate --verbose --all-names *All I can find on the web is time synchronization problems. Any ideas? I can send a full transcript if it would help.. Thanks! -jimc

Hi all, I just downloaded a fresh samba-4.10.0 tarball to verify the result of 'make test' What I did is: ./configure --enable-selftest make make test All run as the ordinary user. I encountered a build problem with 'make' in source4/lib/messaging/messaging_handlers.c due to the following conditional being placed /before/ #include "includes.h" #if defined(DEVELOPER)

Hello all I followed samba4 how to ( CentOS6 minimum install ) #working fro me ./configure.developer make #failed for me [root at dcmsc samba-4.0.0alpha16]# make quicktest WAF_MAKE=1 ./buildtools/bin/waf test --quick 'test' finished successfully (0.000s) Waf: Entering directory `/root/download/samba-4.0.0alpha16/bin' [ 111/3389] Generating VERSION Waf: Leaving directory

Hi, Yes, you're right, the problems are due to the selftest environment failing to start up. In this case, you could just reproduce the same problem with: SELFTEST_TESTENV=s4member:local make testenv There may be some package dependencies you're missing in order to get selftest to run correctly. In a earlier message it looked like you were missing the python DNS package (python-dnspython

In my environment the selftest for samba3.rpc.spoolss.printer was failing at source3/script/tests/printing/modprinter.pl(138) with the Perl error in subject: Insecure $ENV{ENV} while running setgid at /home/user/src/samba-git/samba/source3/script/tests/printing/modprinter.pl line 138 code is: ============================== delete @ENV{'BASH_ENV'}; $ENV{'PATH'} =

Yah, jimc again. I still cannot figure out what is wrong with my dc. The problem began with being unable to log on from Windows boxes after a power hit. The initial symptoms were: 1) When I log in on a Windows machine, with an account that should have administrator permissions, I don't have said admin rights. 2) When I attempt to launch the Windows remote server tools, I can select the

Selftest is an important part of network driver, this patch adds selftest for virtio-net, including loopback test, negotiate test and reset test. Loopback test checks whether virtio-net can send and receive packets normally. Negotiate test executes feature negotiation between virtio-net driver in Guest OS and virtio-net device in Host OS. Reset test resets virtio-net. Following last patch, this

*what* are you talking about? http://www.catb.org/esr/faqs/smart-questions.html#beprecise * on no distribution a kerberos service is running out of the box * you don't tell us even what distribution are you using * you don't tell us the errors * you even don't tell us the how-to you are talking about Am 04.02.2015 um 18:04 schrieb jimc: > I have been told that kerberos cannot

Yes, I did an fsck from a boot dvd. It came up clean. I did a recursive setfacal to set all acls to default. On 18 Nov 2015, at 03:33, jimc<jesmeyano at gmail.com> wrote: Yah, jimc again. I still cannot figure out what is wrong with my dc. The problem began with being unable to log on from Windows boxes after a power hit. The initial symptoms were: 1) When I log in on a Windows

Selftest is an important part of network driver, this patch adds selftest for virtio-net, including loopback test, negotiate test and reset test. Loopback test checks whether virtio-net can send and receive packets normally. Negotiate test executes feature negotiation between virtio-net driver in Guest OS and virtio-net device in Host OS. Reset test resets virtio-net. Following last patch, this

Hi! I wish to move my Samba 4 server to a new box. Since the old one is pata and the new one is sata, I cannot simply swap disks. What is the best way to transfer my server without loosing configuration files? Thanks -jimc

Seeing a build problem after updating my git tree: $ git remote -v origin git://git.samba.org/samba.git (fetch) origin git://git.samba.org/samba.git (push) $ git pull $ ./configure ... $ make clean WAF_MAKE=1 python ./buildtools/bin/waf build ./buildtools/wafsamba/samba_utils.py:397: DeprecationWarning: the md5 module is deprecated; use hashlib instead

HI. I have been told that kerberos cannot be running while samba4 is. How do I do this? I seem to have missed this on the how-to and system requirements. I have commented out every entry in /etc/services that seems even remotely kerberosish. I still get errors on kinit and host (from the how-to). I have googled until my computers are laughing at me and have posted on every forum I can find.

Hi! I got my first Samba 4 system up and running. {No applause, just throw money. Paper please, coins hurt} It is just a home network of about a dozen or so boxes. I have noticed that when I do a testparm, the result is not the same as the file I created. I'm fairly certain it isn't anything to worry about; I'm just trying to learn. Thanks! -jimc