On 19 Aug 2015, at 12:15 am, Streeter, Michelle N
michelle.n.stree...@boeing.com wrote:
I created a whole new virtual and installed everything with the new version
and pacemaker wouldn’t start.
I have not yet learned how to use the logs yet to see what they have to say.
No, I did not
On 18/08/15 10:15 AM, Streeter, Michelle N wrote:
I created a whole new virtual and installed everything with the new
version and pacemaker wouldn’t start.
I have not yet learned how to use the logs yet to see what they have to say.
No, I did not upgrade corosync. I am running the latest
I created a whole new virtual and installed everything with the new version and
pacemaker wouldn't start.
I have not yet learned how to use the logs yet to see what they have to say.
No, I did not upgrade corosync. I am running the latest which will work with
rhel6.
When I tried later versions,
On 18 Aug 2015, at 7:13 am, Streeter, Michelle N
michelle.n.stree...@boeing.com wrote:
I was recommended to upgrade from 1.1.9 to 1.1.12.
I had to uninstall the 1.1.9 version to install the 1.1.12 version
Did you upgrade anything else? cman? corosync? heartbeat? What distro? Logs?
I was recommended to upgrade from 1.1.9 to 1.1.12.
I had to uninstall the 1.1.9 version to install the 1.1.12 version
I am not allowed to connect to a repo and so I have to download the rpms and
install them individually.
After I installed pacemaker-lib, cli, cluster-lib, and pacemaker itself,
On 17/08/15 05:13 PM, Streeter, Michelle N wrote:
I was recommended to upgrade from 1.1.9 to 1.1.12.
I had to uninstall the 1.1.9 version to install the 1.1.12 version
I am not allowed to connect to a repo and so I have to download the rpms
and install them individually.
After I
