similar to: core dump from samba-tool when chnging user password

On Mon, Aug 24, 2020 at 11:57 AM James B. Byrne via samba < samba at lists.samba.org> wrote: > > > On Mon, August 24, 2020 11:17, James B. Byrne wrote: > > > > On the other hand, the errors I report are likely solvable should > someone with > > the ability to do so take note of them, so I am reporting this one. > What I > > want to know is whether this

FreeBSD-12.1p8 Samba-4.10.15 I attempted to change the user password of a logged in userid using samba-tool on the PDC and this is what happened: [root at smb4-2 ~ (master)]# samba-tool user password -U testuser Password for [BROCKLEY\testuser]: New Password: Retype Password: Bad talloc magic value - unknown value =============================================================== INTERNAL ERROR:

On Mon, August 24, 2020 11:17, James B. Byrne wrote: > > On the other hand, the errors I report are likely solvable should someone with > the ability to do so take note of them, so I am reporting this one. What I > want to know is whether this should be reported as a bug or whether this > problem has been solved in a more recent version of Samba. I am not prepared > to move

On Mon, Aug 24, 2020 at 12:52:58PM -0400, James B. Byrne via samba wrote: > > > On Mon, August 24, 2020 12:48, Andrew Walker wrote: > > > > Out of curiosity, can you provide a link to one of the FreeBSD bug reports? > > I believe the talloc port in FreeBSD uses arc4random() during talloc_init() > > to calculate magic. > > > >

On Mon, August 24, 2020 22:19, Andrew Bartlett wrote: > > A bit of an aside, but it would be incredibly awesome if the FreeBSD > port could adopt the same policy as, eg, Debian and not ship any > patches that are not upstream. > > We do consider such patches, with justification, when submitted by or > on behalf of their authors. See for example this recent MR submitted >

On Mon, 2020-08-24 at 12:48 -0400, Andrew Walker via samba wrote: > On Mon, Aug 24, 2020 at 11:57 AM James B. Byrne via samba < > samba at lists.samba.org> wrote: > > > > > > > On Mon, August 24, 2020 11:17, James B. Byrne wrote: > > > > > > On the other hand, the errors I report are likely solvable should > > > > someone with

FreeBSD-12.1p6 IOCage thick jails on ZFS, samba-4.10.15: On Fri, July 10, 2020 02:29, Andrea Venturoli wrote: > On 2020-07-09 21:36, James B. Byrne via samba wrote: >> set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_INVALID_PARAMETER. >> ERROR(runtime): uncaught exception - (3221225485, 'An invalid parameter was >> passed to a service or function.') > > What

On Sat, July 11, 2020 04:32, Andrea Venturoli wrote: > On 2020-07-10 14:47, James B. Byrne wrote: >> FreeBSD-12.1p6 IOCage thick jails on ZFS, samba-4.10.15: > > Can you post the smb.conf of both DCs? > > Just out of curiosity, are you also using vfs_zfsacl? Yes. smb.confs DC1 and DC2: /zroot/iocage/jails/smb4-1a/root/usr/local/etc/smb4.conf [root at vhost04 ~ (master)]#

FreeBSD-12.1p7 Samab-4.10.15 running in FreeBSD Jail I just wish to ensure that my conclusion respecting Samba, FreeBSD Jails, and NTP is correct. 1. Unless configured otherwise Windows domain clients will query and obtain their time from the samba_server DC. 2. Samba_server obtains its time from the OS, in this case a FreeBSD Jail. 3. FreeBSD Jails get their time from their host. 4. If

On Thu, July 23, 2020 16:50, Rowland penny wrote: > Port 137 should only be used by Samba nmb, so has nmbd somehow > been started ? No. The error is not caused by anything else listening on 137. [root at smb4-2 ~ (master)]# netstat -an | grep -i listen tcp4 0 0 192.168.18.162.22 *.* LISTEN tcp4 0 0 192.168.216.162.22 *.*

On Thu, July 30, 2020 17:23, Robert Marcano wrote: > On 7/30/20 5:00 PM, James B. Byrne via samba wrote: >> FreeBSD-12.1p7 >> Samab-4.10.15 running in FreeBSD Jail >> >> >> I just wish to ensure that my conclusion respecting Samba, FreeBSD Jails, and >> NTP is correct. >> >> 1. Unless configured otherwise Windows domain clients will query and

On Mon, March 9, 2015 13:11, John Plemons wrote: > Been working on fail2ban, and trying to make it work with plain Jane > install of Centos 7 > > Machine is a HP running 2 Quad core Xeons, 16 gig or ram and 1 plus TB > of disk space. Very generic and vanilla. > > Current available epel repo version is fail2ban-0.9.1 > > Looking at the log file, fail2ban starts and stops

On Thu, July 23, 2020 14:36, Jeremy Allison wrote: > The samba binary has an nbt server turned on > by default. It has a different functionality > set than nmbd. The jail is not running anything other than sshd and webmin, as the netstat results clearly show. The issue appears to me to be that samba-tool cannot bind to that port even though it is available. -- *** e-Mail is

FreeBSD-12.1p7 jail running Samba-4.10.15 on ZFS. When I run 'samba-tool domain backup offline targetdir=/tmp' I see this: running backup on dirs: /var/db/samba4/private /var/db/samba4 /usr/local/etc Starting transaction on /var/db/samba4/private/secrets At which point samba-tool enters a permanent wait state. 86064 root 1 52 0 131M 78M wait 3 0:01 0.00%

On Thu, July 23, 2020 15:56, Andrew Bartlett wrote: > > Clearly there is, as otherwise we could not be in waitpid on it. > The process is not a python process, it will be tdbbackup. The > command line arguments to that process will be instructive. Here it is: root 36800 0.8 0.0 12556 2788 1 SJ 16:49 0:00.01 /usr/local/bin/tdbbackup -s .copy.tdb

On Tue, 2020-08-25 at 14:12 -0400, Andrew Walker via samba wrote: > On Tue, Aug 25, 2020 at 1:17 PM James B. Byrne via samba < > samba at lists.samba.org> wrote: > > > > > > > On Mon, August 24, 2020 22:19, Andrew Bartlett wrote: > > > > > > > > A bit of an aside, but it would be incredibly awesome if the > > > FreeBSD >

On Wed, July 22, 2020 21:47, Andrew Bartlett wrote: > Are you using DLZ_BIND9? There is a bug where it doesn't know the locking rules for those files. No. I am using the internal dns service. > Otherwise, work out which commend it is waiting on (the child) and > what lock that is waiting on (lslocks on linux is what I used to > debug this stuff). There does not appear to be

On Tue, Aug 25, 2020 at 1:17 PM James B. Byrne via samba < samba at lists.samba.org> wrote: > > > On Mon, August 24, 2020 22:19, Andrew Bartlett wrote: > > > > > A bit of an aside, but it would be incredibly awesome if the FreeBSD > > port could adopt the same policy as, eg, Debian and not ship any > > patches that are not upstream. > > > > We

I have abandoned trying to get an existing AD-DC on a FreeBSD host using UFS to replicate successfully to a FreeBSD host on ZFS. I am now in the process of provisioning a new domain on the ZFS host. The domain is created on a FreeBSD thick jail using IOcage as the jail manager; probably should be called the warden but I digress. I have successfully provisioned a new domain but I see an issue

Rowland Penny rpenny at samba.org Fri Aug 9 15:25:00 UTC 2024 On Fri, 9 Aug 2024 10:40:18 -0400 "James B. Byrne via samba" <samba at lists.samba.org> wrote: >> I am testing samba-4.19 on FreeBSd-14.1 and am getting this error in >> the log.wb-<DOMAIN> file: >> >> ../../source3/winbindd/winbindd_dual.c:1965(winbindd_sig_term_handler) >> >>