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 versions is not implicitly supported until these issues are resolved. On May 11, 2011 10:25 AM, "Douglas Hubler" <[email protected]> wrote: > On Wed, May 11, 2011 at 9:26 AM, Tony Graziano > <[email protected]> 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 >> PresenceServer had a log of "0" bytes make me think it was not running, yet >> sipxconfig UI reported it was. To me, it looks like a bug. "How" I got to >> this version is questionable, and I can easily correct with a rebuild. Am I >> overly concerned with service reported running when it probably is not >> though? > > It's a good point. If someone see's it again, maybe i'll be inspired > to investigate. Internals of supervisor code is not straightforward > to me to have a good idea of the issue. > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
