Displaying 5 results from an estimated 5 matches for "4e89".
Did you mean:
489
2019 Aug 11
2
Can't replicate DCs
...DC2 -
Valemount\DC2
DSA Options: 0x00000001
DSA object GUID: 617c7792-2980-4625-917d-21418ac96f06
DSA invocationId: b5e8a8b6-ada3-472f-bee8-4e7d9ab813bc
==== INBOUND NEIGHBORS ====
CN=Configuration,dc=ad,dc=example,dc=com
McBride\DC1 via RPC
DSA object GUID: a908c575-ddb1-4e89-98e1-97d3e55bf213
Last attempt @ Sun Aug 11 15:40:51 2019 PDT failed, result
8453 (WERR_DS_DRA_ACCESS_DENIED)
6664 consecutive failure(s).
Last success @ Sun Aug 11 15:40:51 2019 PDT
CN=Configuration,dc=ad,dc=example,dc=com
McBride\DC3 via RP...
2019 Oct 04
2
samba-tool user syncpasswords crashes with python3
the script works...
root at probe28:~# cat test.dat
dn: CN=userxxxx,OU=Users,OU=xxxxx,OU=Organizations,DC=xxxxx,DC=xxxxx
proxyAddresses: SMTP:xxxxx.xxxxx at xxxxx.org
objectGUID: 637f4e70-8c1e-4e89-a6fc-82d525e584f2
pwdLastSet: 0
objectSid: S-1-5-21-1608159440-4144762864-1017073214-27184
sAMAccountName: userxxxx
mail: xxxxx.xxxxx at xxxxx.xxxxx
userAccountControl: 514
virtualClearTextUTF8:: S2VubndvcnQx
root at probe28:~#
root at probe28:~#
root at probe28:~#
root at probe28:~# cat test.d...
2019 Oct 04
2
samba-tool user syncpasswords crashes with python3
Hi,
i sync the passwords from samba to other backends using "samba-tool
user syncpasswords"
On my operative system (samba 4.10 and python2) all works fine.
I upgraded my test-DC to samba 4.11 and python3 and now the samba-tool
user syncpasswords --daemon crashes.
Fri Oct 4 12:29:47 2019: pid[983]: Attached to
logfile[/usr/local/samba/var/log.syncpw]
Fri Oct 4 12:29:47 2019:
2012 Dec 23
7
Unsticking a DomU
I''m not able to start, destroy, or delete a DomU:
> xen1:~ # xm start test4
> Error: Domain is already running
> Usage: xm start <DomainName>
>
> Start a Xend managed domain
> -p, --paused Do not unpause domain after starting it
> -c, --console_autoconnect Connect to the console after the domain
2012 Apr 20
44
Ceph on btrfs 3.4rc
After running ceph on XFS for some time, I decided to try btrfs again.
Performance with the current "for-linux-min" branch and big metadata
is much better. The only problem (?) I''m still seeing is a warning
that seems to occur from time to time:
[87703.784552] ------------[ cut here ]------------
[87703.789759] WARNING: at fs/btrfs/inode.c:2103