Removing redundancy

Hello,
since I'm encountering to much issues with the redundancy system and don't have the time to debug further, I decided to delete the secondairy node (for ex. the last restart the redundancy looked OK, but both all the plc's were out of sync resulting 2 same loads doing the same but with other values).
I hoped this was as easy as implementing the redundancy, so did the reverse order. Eventually the main node started, everything again looked OK, but the op station didn't want to mount the main node.
In the log file of the main node I found the following:
 

I removed the mounting, build with force and added back the mount but the problem remains.
One thing to note: all the builds were done with force.
Is it possible that there 's still flying around from the redundancy and messing things up?!?

In the meantime I restored back the old load backup and without any change the PLC's are nog in sync. But as stated above, I can change any moment ...

Ok, I think I found a part of the cause.
Since the files ld_redcom_node... where created in the past, the distributor keeps loading them causing the load to become into a state of not being totatly aware that it was splitted.
A workaround I did for nog was deleting the ld_redcom* from the node and in the build folder. The connection is restored.
Only thing to figure out is why my hist server isn't working anymore, but this can be independant from the cause above since I'm now on some test virtual machines to trace the earlier problem.

Problem with the sevserver is also found: Proviewr was starting up faster than Mysql resulting the obvious error that the database could not be opened --> solved.

So the conclusion: delete all the redundant parameters and also the ld_redcom files from the build dir and everything works as if there was never redundancy configured.

This gives me some margin to examine where the whole redundant part goes wrong in my load.