On Mon, Mar 30, 2009 at 11:33 PM, Scott Lawrence <[email protected]> wrote: > On Mon, 2009-03-30 at 15:26 -0400, M. Ranganathan wrote: >> On Mon, Mar 30, 2009 at 3:20 PM, Dale Worley <[email protected]> wrote: >> > On Mon, 2009-03-30 at 10:25 -0400, Raymond Dans wrote: >> >> The actual component has a version in its process xml file (under >> >> /usr/share/sipxecs/process.d). >> >> SipXconfig, I believe, gets a version number from its properties file >> >> (sipxconfig.properties) and should call the XML/RPC SetConfigVersion >> >> using its version number for each of the services it will ask to start. >> >> Supervisor will then check the version that was set against what was >> >> found in the process xml file. If they don't match, you don't get >> >> started. >> > >> > What do you do to get this error cleared out? >> >> >> Send Profile to the HA server from sipxconfig. As discussed on #sipx, >> I think we may want to rework it so that step is not necessary ( >> confused the daylights out of me ). > > Be more explicit... rework _what_ so that _what_ step is not necessary? > > If the version number is not set (which what matches your symptoms), > then it's because something is _broken_. We need to figure out what > that something is and fix it. > >
Sorry. To be more explicit : During install of a secondary server, when the tar.gz file that is generated by sipxconfig is transported from the primary to secondary server, it can also include whatever configuration information is necessary so that it will not be necessary to subsequently do a "send profile" to the secondary server. The current situation is that you see a gree REGISTERED indication but the secondary server is not configured until you push profiles to it by selecting that server and sending the profiles. > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
