On Wed, May 11, 2011 at 11:26 AM, Tony Graziano
wrote:
> I hear it I think about that upgrading from unstable versions is supported.
>
> well I am making my own point and maybe only to myself, upgrading from
> unstable versions is not implicitly supported until these issues are
> resolved.
Upgrad
it may not matter, this was also seen updating to 4.2.1 by someone else. in
both of these instances, they were coming from unstable versions.
I hear it I think about that upgrading from unstable versions is supported.
well I am making my own point and maybe only to myself, upgrading from
unstable
On Wed, May 11, 2011 at 9:26 AM, Tony Graziano
wrote:
> I had planned that. What I didn't understand is why none of the logging
> components failed to capture the issue and why there was a reported
> "ConfigurationMismatch".
> While everything reported properly in services, the fact that the
> Pre
I had planned that. What I didn't understand is why none of the logging
components failed to capture the issue and why there was a reported
"ConfigurationMismatch".
While everything reported properly in services, the fact that the
PresenceServer had a log of "0" bytes make me think it was not runn
I don't see what you are talking about here Tony...
I too had issues in going from 4.3.x to 4.4.0. I had to get it there, then
get a backup, then build a clean system and do a restore.
Mike
On Tue, May 10, 2011 at 1:00 PM, Tony Graziano wrote:
> I came to 4.4 via 4.3, and had to erase a packa
I came to 4.4 via 4.3, and had to erase a package or two and yum to get
here. All of my sipx packages are the same versions, and are the correct
version. Everything seems fine except the above mismatch(es). I have sent
the server profiles. I have restarted services/server. I have no logs for
Presen
