Displaying 11 results from an estimated 11 matches for "bcf8".
Did you mean:
bc98
2019 Mar 27
3
samba 4.9.5 - joining Samba DC to existing Samba AD failed
...A;;RP;4c164200-20c0-11d0-a768
> -00aa006e0529;;RS)(OA;;RP;bc0ac240-79a9-11d0-9020-00c04fc2d4cf;;RS)(A;;RC;;;A
> U)(OA;;RP;59ba2f42-79a2-11d0-9020-00c04fc2d3cf;;AU)(OA;;RP;77b5b886-944a-11d1
> -aebd-0000f80367c1;;AU)(OA;;RP;e45795b3-9455-11d1-aebd-0000f80367c1;;AU)(OA;;
> RP;e48d0154-bcf8-11d1-8702-00c04fb96050;;AU)(OA;;CR;ab721a53-1e2f-11d0-9819-0
> 0aa0040529b;;WD)(OA;;RP;5f202010-79a5-11d0-9020-00c04fc2d4cf;;RS)(OA;;RPWP;bf
> 967a7f-0de6-11d0-a285-00aa003049e2;;CA)(OA;;RP;46a9b11d-60ae-405a-b7e8-ff8a58
> d456d2;;S-1-5-32-560)(OA;;RPWP;6db69a1c-9422-11d1-aebd-0000f8036...
2010 Feb 26
0
How can we pickup a call that is not going to a real extension?
...or the callee-leg
exten => _[+0-9a-zA-Z*#_].,n,Pickup(${CALL_UUID}@inbound-wait-loop)
We thought Pickup() would work, but it only seems to work if the call is in the Dial state.
The logs have results like:
-- Executing [5552233 at caller-inbound-leg:8] Pickup("SIP/20678350-5cd1-11de-bcf8-123139006632-0000004e", "14f0dff4-9a34-11dd-93fd-0015588ab9f3 at inbound-wait-loop") in new stack
[2010-02-25 19:20:28.936] NOTICE[18759]: app_directed_pickup.c:294 pickup_exec: No target channel found for 14f0dff4-9a34-11dd-93fd-0015588ab9f3.
Is there a way for a callee to pickup...
2019 Mar 26
0
samba 4.9.5 - joining Samba DC to existing Samba AD failed
...-00a0c968f939;;RS)(OA;;RP;4c164200-20c0-11d0-a768
-00aa006e0529;;RS)(OA;;RP;bc0ac240-79a9-11d0-9020-00c04fc2d4cf;;RS)(A;;RC;;;A
U)(OA;;RP;59ba2f42-79a2-11d0-9020-00c04fc2d3cf;;AU)(OA;;RP;77b5b886-944a-11d1
-aebd-0000f80367c1;;AU)(OA;;RP;e45795b3-9455-11d1-aebd-0000f80367c1;;AU)(OA;;
RP;e48d0154-bcf8-11d1-8702-00c04fb96050;;AU)(OA;;CR;ab721a53-1e2f-11d0-9819-0
0aa0040529b;;WD)(OA;;RP;5f202010-79a5-11d0-9020-00c04fc2d4cf;;RS)(OA;;RPWP;bf
967a7f-0de6-11d0-a285-00aa003049e2;;CA)(OA;;RP;46a9b11d-60ae-405a-b7e8-ff8a58
d456d2;;S-1-5-32-560)(OA;;RPWP;6db69a1c-9422-11d1-aebd-0000f80367c1;;S-1-5-32...
2019 Mar 26
2
samba 4.9.5 - joining Samba DC to existing Samba AD failed
Hi Tim and Rowland, thanks for Your support!
I was thinking about e.g. Python 2.7.15 compatibility (as newer Samba
versions require Python3), but You are right, here in DB can be problem
- first Samba AD DC was created by migrating Samba3 NT4 domain to Samba4
AD cca week ago (using 'samba-tool domain classicupgrade ...', according
to Samba Wiki):
On Tue, 26 Mar 2019 10:14:02 +1300
Tim
2013 Sep 14
2
samba4 adding an index to sam.ldb
I have a large installation >20k users. We're using samba4 for AD Authentication, and also email address validation. I'm trying to edit the @INDEXLIST in sam.ldb to add an index on otherMailbox to speed up searches (0.05 sec for indexed, vs 2.5 sec for non-indexed searches) I'm finding that when I use ldbedit to do this, it appears to add the additional @IDXATTR. However, when I
2018 Nov 01
1
Internal DNS migrate to Bind9_DLZ
...1: SEC_ACE_OBJECT_TYPE_PRESENT
0: SEC_ACE_INHERITED_OBJECT_TYPE_PRESENT
type : union security_ace_object_type(case 1)
type : e48d0154-bcf8-11d1-8702-00c04fb96050
inherited_type : union security_ace_object_inherited_type(case 0)
trustee : S-1-5-11
aces: struct security_ace
type : SEC_ACE_TYPE_AC...
2018 Nov 01
2
Internal DNS migrate to Bind9_DLZ
I've been been trying to investigate this for sometime now, hence I came to
the experts :)
I have rejoined all my DC's with new names, see below.
;; ANSWER SECTION:
<domain>.corp. 3600 IN NS psad101zatcrh.<domain>.corp. -> New
rebuild, new hostname, RHEL6 to RHEL7 upgrade
<domain>.corp. 3600 IN NS prdc001zafsrh.<domain>.corp. -> New
2017 Mar 29
5
NT_STATUS_NO_LOGON_SERVERS after removing a DC and WERR_BADFILE when trying to remove broken DC
Situation: Trying to upgrade Samba from 4.1 to 4.5 without disruption
too much by adding new DCs and demoting old ones.
After bringing online the first 4.5 DC, I ran `demote
--remove-other-dead-server=` on that DC to remove one of the old 4.1 DCs
(held no FSMO roles). That seemed to run fine (the DC had been offline
for a few weeks at that point and I didn't want to restore it just for
2017 Oct 26
0
not healing one file
Hey Richard,
Could you share the following informations please?
1. gluster volume info <volname>
2. getfattr output of that file from all the bricks
getfattr -d -e hex -m . <brickpath/filepath>
3. glustershd & glfsheal logs
Regards,
Karthik
On Thu, Oct 26, 2017 at 10:21 AM, Amar Tumballi <atumball at redhat.com> wrote:
> On a side note, try recently released health
2017 Oct 26
3
not healing one file
On a side note, try recently released health report tool, and see if it
does diagnose any issues in setup. Currently you may have to run it in all
the three machines.
On 26-Oct-2017 6:50 AM, "Amar Tumballi" <atumball at redhat.com> wrote:
> Thanks for this report. This week many of the developers are at Gluster
> Summit in Prague, will be checking this and respond next
2017 Oct 26
2
not healing one file
...0F7B4AED206EAFED2BD2 (127d6e53-2216-4ca9-881c-3789b3bee58d) on home-client-2
[2017-10-25 10:14:16.922268] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/08E9EA530967C019EDB37BA974BC95180ABEA56C (fb5c7642-bcf8-4839-bed9-a4a566ff59ae) on home-client-2
[2017-10-25 10:14:16.952445] W [MSGID: 108015] [afr-self-heal-entry.c:56:afr_selfheal_entry_delete] 0-home-replicate-0: expunging file a3f5a769-8859-48e3-96ca-60a988eb9358/31DC050CD1D0772589D40C673A2931227AC1B5AE (3e4761b6-0133-49ff-93c5-7ee8bb5a684a) on hom...