Displaying 20 results from an estimated 10000 matches similar to: "samba-tool domain backup offline stalls"
2020 Jul 23
4
samba-tool domain backup offline stalls
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
2020 Jul 22
3
samba-tool domain backup offline stalls
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%
2020 Jul 23
3
samba-tool domain backup offline stalls
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
2020 Jul 23
3
samba-tool domain backup offline stalls
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
2020 Jul 13
5
DC replications of FreeBSD samba-4.10.15
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)]#
2020 Jul 23
0
samba-tool domain backup offline stalls
On Thu, July 23, 2020 16:16:30, Mani Wieser wrote:
>>> ../../source4/nbt_server/interfaces.c:228(nbtd_add_socket)
>>> Failed to bind to 127.0.162.1:137 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
> check where has port 137 occupied
There is nothing listening on 137
[root at smb4-2 ~ (master)]# netstat -an | grep -i listen
tcp4 0 0 192.168.18.162.22 *.*
2020 Jul 31
1
NTP and FreeBSD jails
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
2020 Aug 24
4
core dump from samba-tool when chnging user password
On Mon, August 24, 2020 13:51 +0000, Rowland penny wrote:
> It isn't a PDC, that is something quite different ;-)
>
I know, but it is a lot shorter to write than the DC possessing the PDC FSMO role.
> It is your first DC.
Not really, I have been working with MS AD Domains since NT 3.51, or whatever it
was called back then. This one just happens to be the one I am currently
2024 Aug 09
2
winbindd fails to start
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)
I suspect that this may caused by an ip4 address assignment clash as I am using
the configuration and data structures copied from our running Samba-4.13 DC.
When I run winbindd interactively I see this:
#
2020 Jul 30
2
NTP and FreeBSD jails
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
2020 Jul 10
2
DC replications of FreeBSD samba-4.10.15
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
2020 May 05
1
Samba-4.10.13 IPv6 turn it off
I am working on a FreeBSD jail (12.1p4) using samba410. I have joined this
service to our existing Samab DC DOMAIN using samba-tool domain join. This
worked as far as I can tell.
I have these entries in smb4.conf
# BOF
# Global parameters
[global]
netbios name = SAMBA-02
realm = BROCKLEY-2016.HARTE-LYNE.CA
server role = active directory domain controller
workgroup = BROCKLEY-2016
2020 Jul 22
1
samba-tool domain backup offline fails
On FreeBSD-12.1p7 running Samba-4.10.15 I have a working test AD domain. While
samba_server is confirmed stopped the 'samba-tool domain backup offline'
command gives the following error:
[root at smb4-1c-testfmso ~ (master)]# hostname
smb4-1.brockley.harte-lyne.ca
[root at smb4-1c-testfmso ~ (master)]# samba-tool domain backup offline
--targetdir=/tmp
ERROR(<class
2015 Mar 10
2
Fail2Ban Centos 7 is there a trick to making it work?
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
2024 Aug 12
1
winbindd fails to start
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)
>>
>>
2020 Jul 08
6
How to delete an unwanted NS record
On Wed, July 8, 2020 04:23, Rowland penny wrote:
> On 08/07/2020 08:50, Mani Wieser via samba wrote:
>>
>> On 07.07.2020 22:14, Mani Wieser via samba wrote:
>> Found it (while having my morning walk with the dog): same as with
>> SOA: this is a zone/domain thing and not record
>>
>> Usage: samba-tool dns delete <server> <zone> <name>
2020 May 29
4
Samba 4.11.8 on FreeBSD-12.1
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
2020 Jul 13
3
DC replications of FreeBSD samba-4.10.15
On Mon, July 13, 2020 10:23, Andrea Venturoli wrote:
> On 2020-07-13 15:06, James B. Byrne wrote:
>
>>> Just out of curiosity, are you also using vfs_zfsacl?
>>
>> Yes.
>
> But only on DC1, AFAICT!
> I see no mention of it on DC2's smb.conf.
> That could be the reason why you have two different behaviour.
>
> bye
> av.
>
That appears to
2020 Jul 03
1
samab-4.10 nsupdate
I am also seeing this in smbd.log:
[2020/07/03 09:20:18.211558, 1]
../../auth/kerberos/gssapi_helper.c:391(gssapi_check_packet)
GSS VerifyMic failed: A token had an invalid MIC: unknown mech-code
2529638943 for mech 1 2 840 113554 1 2 2
[2020/07/03 09:20:18.211625, 0]
../../source4/auth/gensec/gensec_gssapi.c:1347(gensec_gssapi_check_packet)
2020 Jul 23
2
samba-tool domain backup offline stalls
On 23/07/2020 18:12, James B. Byrne via samba wrote:
>
> On Thu, July 23, 2020 16:16:30, Mani Wieser wrote:
>
>>>> ../../source4/nbt_server/interfaces.c:228(nbtd_add_socket)
>>>> Failed to bind to 127.0.162.1:137 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
>> check where has port 137 occupied
> There is nothing listening on 137
>
> [root at smb4-2 ~