search for: 4bf5

Displaying 7 results from an estimated 7 matches for "4bf5".

Did you mean: 4b65
2018 Jan 31
2
[Patches] for dbcheck (Re: [Patches] AD Database corruption after upgrade from <= 4.6 to 4.7 (bug #13228))
...one mandatory attribute ('fromServer') on entry 'CN=79fbbaa2-a6b5-4dfd-a7f4-26aaa568f74e,CN=LostAndFoundConfig,CN=Configuration,DC=iumnet,DC=edu,DC=na' wasn't specified!") WARNING: no target object found for GUID component for DN value fromServer in object CN=6eba8ddc-5f5b-4bf5-8025-772ec80a29e2,CN=LostAndFoundConfig,CN=Configuration,DC=iumnet,DC=edu,DC=na - <GUID=3da7e1da-33b5-428b-9313-2ae48ddfee10>;CN=NTDS Settings,CN=IUMONGDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=iumnet,DC=edu,DC=na WARNING: target DN is deleted for fromServer in obj...
2018 Jan 31
0
[Patches] for dbcheck (Re: [Patches] AD Database corruption after upgrade from <= 4.6 to 4.7 (bug #13228))
...;fromServer') on > entry > 'CN=79fbbaa2-a6b5-4dfd-a7f4-26aaa568f74e,CN=LostAndFoundConfig,CN=Configuration,DC=iumnet,DC=edu,DC=na' > wasn't specified!") > WARNING: no target object found for GUID component for DN value fromServer > in object > CN=6eba8ddc-5f5b-4bf5-8025-772ec80a29e2,CN=LostAndFoundConfig,CN=Configuration,DC=iumnet,DC=edu,DC=na > - <GUID=3da7e1da-33b5-428b-9313-2ae48ddfee10>;CN=NTDS > Settings,CN=IUMONGDC,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=iumnet,DC=edu,DC=na > WARNING: target DN is deleted for fr...
2018 Jan 22
6
[Patches] AD Database corruption after upgrade from <= 4.6 to 4.7 (bug #13228)
Hi, here're patches to avoid a database corruption with linked attributes, e.g. member/memberOf. See https://bugzilla.samba.org/show_bug.cgi?id=13228 As a temporary solution admins can add "server services = -kcc" to the global section of smb.conf. Also DO NOT repair the following errors with samba-tool dbcheck! "Remove duplicate links in attribute" and "ERROR:
2014 Oct 26
0
Port number in From URI on Asterisk 12 PJSIP
...DP:172.16.60.160:5061 ---> SIP/2.0 200 OK Via: SIP/2.0/UDP 10.1.1.1:5060 ;rport;received=172.16.60.160;branch=z9hG4bK-29450-3-0 Call-ID: 3-29450 at 172.16.60.160 From: <sip:39937841 at 192.168.225.2;user=phone>;tag=3 To: <sip:039988120F at 172.16.60.160 ;user=phone>;tag=4f7ef94f-fb15-4bf5-94bd-4e43fe-299655 CSeq: 1 INVITE Contact: <sip:172.16.60.160:5060> Allow: OPTIONS, SUBSCRIBE, NOTIFY, PUBLISH, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REFER, MESSAGE, REGISTER Supported: 100rel, timer, replaces, norefersub Content-Type: application/sdp Content-Length: 189 v=0 o=- 10864 4...
2005 Mar 10
5
asterisk and Broadvoice Outgoing Again :(
...-- Got SIP response 400 "Bad request" back from 147.135.8.128 -- Executing Dial("SIP/502-8efd", "SIP/8086749157@XXXXXXXX") in new stack -- Called 8086749157@XXXXXXXX -- Got SIP response 400 "Bad request" back from 147.135.8.128 -- SIP/XXXXXXXX-4bf5 is circuit-busy == Everyone is busy/congested at this time (1:0/1/0) -- Executing Congestion("SIP/502-8efd", "5") in new stack == Spawn extension (vicky, 008086749157, 2) exited non-zero on 'SIP/502-8efd' -- Got SIP response 400 "Bad request" back...
2017 Aug 06
1
[3.11.2] Bricks disconnect from gluster with 0-transport: EPOLLERR
...723] I [MSGID: 106493] [glusterd-rpc-ops.c:700:__glusterd_friend_update_cbk] 0-management: Received ACC from uuid: 7da17b36-d09e-4e8f-870c-f4780ed61225 [2017-08-06 03:12:38.975223] I [MSGID: 106493] [glusterd-rpc-ops.c:485:__glusterd_friend_add_cbk] 0-glusterd: Received ACC from uuid: c4e38a4f-f61f-4bf5-aee1-e33e4daf4ef5, host: 128.138.140.48, port: 0 [2017-08-06 03:12:38.982264] I [MSGID: 106493] [glusterd-rpc-ops.c:700:__glusterd_friend_update_cbk] 0-management: Received ACC from uuid: 87a12be2-5bb0-47cd-88c4-b2c28c03066a [2017-08-06 03:12:38.982651] I [MSGID: 106163] [glusterd-handshake.c:1309:...
2007 Mar 26
16
mongrel_service fails to get "service.exe" from ppid?
Konnichiwa Mongrel users, mongrel_service cannot run as a windows service under my environment, with the windows message : "error 1053 : The service did not respond to the start or control request in a timely fashion." >From a part of "ServiceFB.log" at c:/ruby/bin, mongrel_service failed to get the process name of "service.exe".