Mikael Kermorgant wrote:
Were there any messages in the errors logs on the supplier or consumers about not being able to replicate the schema?On Fri, Oct 2, 2009 at 5:24 PM, Rich Megginson <rmeggins@xxxxxxxxxx> wrote:Mikael Kermorgant wrote:Hello, First ones were the day after a schema modification on the master which had not been weel propagated on the slaves.How did you modify the schema on the master?Via the console, by adding an attribute. Had to copy the schema files to the slaves later.
This could be the explanation but I'm not really sure as it worked well several hours. The last one was today when using the console.Try console -D 9 -f console.log if you can reproduce theOk, I'll try that next time.Problem is we have no logs. Server suddenly freezes and is no more available via ssh , vnc or xen console.So the entire VM freezes, not just the directory server? So you see the server crashing and the VM freezing?Yes, sort of. I still had control of the cursor but could not ctrl+c the console on the xtermWould somebody have an idea about which steps to debug this situation ?Anything in the error log? /var/log/messages ? any other log files in /var/log?Only in /var/log/xen/xend.log which indicates that this is quite offtopic. I'll see what I can find on the xen side, Thanks, Mikael -- 389 users mailing list 389-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
<<attachment: smime.p7s>>
-- 389 users mailing list 389-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
