On Mon, Aug 20, 2012 at 3:34 PM, <[email protected]> wrote: > Hi George, > > Back at work, trying to solve the initialconfig problem. > I started with a restart this morning with all the files in the > /var/sipxdata/tmp/ in place (restored them friday). > Then added a server through the GUI > This resulted in a run of initialconfig with an exit code 1. (09:55:44.821 > in log file) > I then deleted all the tar.gz's in /var/sipxdata/tmp (or should I delete > something else?) > Restarted services again. > Added a server again through the GUI. > Then the initial-config did not run anymore, in the log file I see a > "Connection refused" around that time, 10:14:14.754
I think you see this because there is another server configured, can you start from the beginning one more time and leave only master? that is gssipx02.internal.epo.org I assume. Then add slave in UI, run sipxecs-setup on slave and see if still same error. If you get the error try to manually run intial-config script and see if archive gets generated inside /var/sipxdata/tmp/ No need to manually delete any archive from /var/sipxdata/tmp/ > I put all the tar.gz's back in place, restarted services, but still > initialconfig won't run. > All I see is a replicationBean error around 10:29:44.211 > After some time this will probably work again because of some > synchronisation (because it also worked this morning). > But then I will run into the exit code 1 problem again. > Any clue how to solve this, because if I am not mistaken I am otherwise > looking at a complete rebuild of all the servers. Let's give it one more try before doing this George _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
