Displaying 4 results from an estimated 4 matches for "49e7".
Did you mean:
49,7
2011 Sep 22
1
XCP 1.1 error: Error code: INVALID_SOURCE
...is not mounted.
Is it a bug or just my handling error?
Regards / thank you.
Mark
Some more details:
# ---
[root@xcp-dev01 ~]# xe vm-list
uuid ( RO) : f535e5bd-6540-3745-d494-14f776da85e5
name-label ( RW): squeeze
power-state ( RO): halted
uuid ( RO) : 0642d282-a077-49e7-9382-8ac3276d08b9
name-label ( RW): Control domain on host: xcp-dev01
power-state ( RO): running
[root@xcp-dev01 ~]# xe cd-list
uuid ( RO) : 8f1d5ebd-9fb6-42b0-b7ba-d473028300c3
name-label ( RW): IDE 1.0
uuid ( RO) : 508ed910-83b5-4874-bbf7-c0248e3fc986
nam...
2016 Sep 23
6
replPropertyMetaData & KCC issues after updating to Samba 4.5.0
...ated. This is all with SOLDC1 in site B still down. This tells me
SOLDC2 becomes an island without anyway to replicate.
One strange thing is 'samba-tool drs showrepl' begs to differ.
root at soldc2:~# samba-tool drs showrepl
site-b\SOLDC2
DSA Options: 0x00000001
DSA object GUID: 25055641-49e7-4b3f-a7e3-9d206375306c
DSA invocationId: d11890e8-6b90-4e94-aca4-6d7a940f47b5
==== INBOUND NEIGHBORS ====
CN=Configuration,DC=domain,DC=local
site-b\SOLDC1 via RPC
DSA object GUID: 55e069f5-4f47-415b-8fa4-a398948235aa
Last attempt @ Fri Sep 23 14:40:18 2...
2016 Sep 24
0
replPropertyMetaData & KCC issues after updating to Samba 4.5.0
...still down. This tells
> me SOLDC2 becomes an island without anyway to replicate.
>
> One strange thing is 'samba-tool drs showrepl' begs to differ.
>
> root at soldc2:~# samba-tool drs showrepl
> site-b\SOLDC2
> DSA Options: 0x00000001
> DSA object GUID: 25055641-49e7-4b3f-a7e3-9d206375306c
> DSA invocationId: d11890e8-6b90-4e94-aca4-6d7a940f47b5
>
> ==== INBOUND NEIGHBORS ====
>
> CN=Configuration,DC=domain,DC=local
> site-b\SOLDC1 via RPC
> DSA object GUID: 55e069f5-4f47-415b-8fa4-a398948235aa
>...
2016 Sep 22
2
replPropertyMetaData & KCC issues after updating to Samba 4.5.0
On 9/21/2016 11:32 PM, Garming Sam wrote:
> I would have assumed that deleting all the NTDS connections for all the
> DCs would have remedied this issue. I'll write a patch to try to avoid
> this error in any case.
>
> Ignoring this error and answering your earlier question, it's often hard
> to tell if the KCC is doing what is expected or not. To figure that out,
>