On Fri, Oct 19, 2012 at 6:18 PM, Aaron Pursell <[email protected]> wrote: > On server 1 it reports: > > cf3> * Hailing 192.168.1.32 : 5308, with options "-v -K" (serial) > cf3> > ........................................................................... > cf3> No existing connection to 192.168.1.32 is established... > cf3> Set cfengine port number to 5308 = 5308 > cf3> Set connection timeout to 10 > cf3> -> Connect to 192.168.1.32 = 192.168.1.32 on port 5308 > cf3> -> Did not find new key format /etc/sipxpbx/.cfagent/ppkeys/sipx-.pub > cf3> -> Trying old style /etc/sipxpbx/.cfagent/ppkeys/sipx-192.168.1.32.pub > cf3> Couldn't send > cf3> !!! System error for send: "Broken pipe" > cf3> Couldn't send > cf3> !!! System error for send: "Broken pipe" > cf3> Couldn't send > cf3> !!! System error for send: "Broken pipe" > cf3> Challenge response from server 192.168.1.32/192.168.1.32 was incorrect! > cf3> I: Report relates to a promise with handle "" > cf3> I: Promise is made internally by cfengine > cf3> !! Authentication dialogue with 192.168.1.32 failed > cf3> Unable to establish connection with 192.168.1.32 > cf3> -> No suitable server responded to hail > cf3> CFEngine - autonomous configuration engine - commence self-diagnostic > prelude > > On server 2 nothing ever hits the log.
Is 192.168.1.32 your secondary IP? Can you try service sipxsupervisor restart on second machine and see if it works after (is the 2nd machine configured from the first shot, or have you run sipxecs-setup more than once) Thanks George _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
