ok, there's one more issue and i couldn't find a fix before i need to
head out.  i'll be back sunday.   workaround is to run sipxecs-setup
again, it's a race condition issue w/mongo startup.

On Thu, Jun 7, 2012 at 10:37 PM, Douglas Hubler <[email protected]> wrote:
> yes, a few of use have run into these as well.  I think they are all
> fixed, but I'm doing a full rebuild now and will test in the AM.  The
> error reporting is very weak, I'll try to take the opportunity to
> clean that up this month if i get some good ideas.
>
> On Thu, Jun 7, 2012 at 7:56 PM, Dan Chang <[email protected]> wrote:
>> We encountered an interesting error trying to add a second machine to an
>> existing SipXecs 4.5.2 config server.  When we added the second machine
>> in the primary UI we got a green "Configured", however when we ran
>> "sipxecs-setup" on the second machine we received several errors
>> indicating a missing "/var/sipxdata/cfdata/servers".  I have seen some
>> comments that this error might be benign, though.
>>
>> When we tried to set roles on the second machine (such as Distributed
>> Database) we received errors upon sending profiles indicating the second
>> machine was unable to authenticate with the primary (we tried restarting
>> and deleting keys and such along the way).  In the end we removed the
>> server from the cluster.  I was just checking if anyone has seen this
>> problem, or maybe have any tips?  Errors are listed below.
>>
>> Thanks!
>>
>> D Chang
>>
>>
>> -=[ Second Machine - sipxecs-setup Error ]=-
>> [root@sip1 log]# sipxecs-setup --verbose --reset
>> Checking if /var/sipxdata/cfdata/domain.cfdat exists
>> Checking if /var/sipxdata/cfdata/domain-config.part exists
>> Checking if /var/sipxdata/cfdata/defaults/primary.cfdat exists
>> Checking if /var/sipxdata/cfdata/defaults/secondary.cfdat exists
>> Removing /var/sipxdata/cfdata/defaults/secondary.cfdat
>> Checking if /var/sipxdata/cfdata/defaults/master exists
>> Removing /var/sipxdata/cfdata/defaults/master
>> Checking if /var/sipxdata/cfdata/defaults/location_id exists
>> Removing /var/sipxdata/cfdata/defaults/location_id
>> Checking if /var/sipxdata/cfdata/1/mongo-client.ini exists
>> /usr/sbin/cf-key
>> A key file already exists at /var/cfengine/ppkeys/localhost.pub
>> su - sipx sh -c '/usr/sbin/cf-key'
>> A key file already exists at /etc/sipxpbx/.cfagent/ppkeys/localhost.pub
>> Is this the first server in your cluster? [ enter 'y' or 'n' ] : n
>> Configuring as an additional server...
>> Enter ip address or fully qualified host name of the primary server :
>> 205.176.100.133
>> Enter the numeric id assigned to this server by the administration
>> server : 2
>> Configuring system, this may take a few minutes...
>> /usr/bin/sipxagent -v  -d setup
>> cf-agent -v -D setup  -IKf /usr/share/sipxecs/cfinputs/promises.cf |
>> /usr/bin/sipxagent-log-reader -v
>> Token - warning:Could not examine file "/var/sipxdata/cfdata/servers" in
>> readfile
>> Digester - warning:Could not examine file "/var/sipxdata/cfdata/servers"
>> in readfile
>> Token - error:System error for stat: "No such file or directory"
>> Digester - error:System error for stat: "No such file or directory"
>> Token - warning:Could not examine file "/var/sipxdata/cfdata/servers" in
>> readfile
>> Digester - warning:Could not examine file "/var/sipxdata/cfdata/servers"
>> in readfile
>> Token - error:System error for stat: "No such file or directory"
>> Digester - error:System error for stat: "No such file or directory"
>> Token - warning:Could not examine file "/var/sipxdata/cfdata/servers" in
>> readfile
>> Digester - warning:Could not examine file "/var/sipxdata/cfdata/servers"
>> in readfile
>> Token - error:System error for stat: "No such file or directory"
>> Digester - error:System error for stat: "No such file or directory"
>> Token - warning:Could not examine file "/var/sipxdata/cfdata/servers" in
>> readfile
>> Digester - warning:Could not examine file "/var/sipxdata/cfdata/servers"
>> in readfile
>> Token - error:System error for stat: "No such file or directory"
>> Digester - error:System error for stat: "No such file or directory"
>> Token - warning:Could not examine file "/var/sipxdata/cfdata/servers" in
>> readfile
>> Digester - warning:Could not examine file "/var/sipxdata/cfdata/servers"
>> in readfile
>> Token - error:System error for stat: "No such file or directory"
>> Digester - error:System error for stat: "No such file or directory"
>> Token - warning:Could not examine file "/var/sipxdata/cfdata/servers" in
>> readfile
>> Digester - warning:Could not examine file "/var/sipxdata/cfdata/servers"
>> in readfile
>> Token - error:System error for stat: "No such file or directory"
>> Digester - error:System error for stat: "No such file or directory"
>> Token - warning:Could not examine file "/var/sipxdata/cfdata/servers" in
>> readfile
>> Digester - warning:Could not examine file "/var/sipxdata/cfdata/servers"
>> in readfile
>> Token - error:System error for stat: "No such file or directory"
>> Digester - error:System error for stat: "No such file or directory"
>> Token - warning:Could not examine file "/var/sipxdata/cfdata/servers" in
>> readfile
>> Digester - warning:Could not examine file "/var/sipxdata/cfdata/servers"
>> in readfile
>> Token - error:System error for stat: "No such file or directory"
>> Digester - error:System error for stat: "No such file or directory"
>> Token - warning:Could not examine file "/var/sipxdata/cfdata/servers" in
>> readfile
>> Digester - warning:Could not examine file "/var/sipxdata/cfdata/servers"
>> in readfile
>> Token - error:System error for stat: "No such file or directory"
>> Digester - error:System error for stat: "No such file or directory"
>> Digester - finished:
>> Analyzer - error Error. Could not examine file
>> "/var/sipxdata/cfdata/servers" in readfile. System error for stat: "No
>> such file or directory". Could not examine file
>> "/var/sipxdata/cfdata/servers" in readfile. System error for stat: "No
>> such file or directory". Could not examine file
>> "/var/sipxdata/cfdata/servers" in readfile. System error for stat: "No
>> such file or directory". Could not examine file
>> "/var/sipxdata/cfdata/servers" in readfile. System error for stat: "No
>> such file or directory". Could not examine file
>> "/var/sipxdata/cfdata/servers" in readfile. System error for stat: "No
>> such file or directory". Could not examine file
>> "/var/sipxdata/cfdata/servers" in readfile. System error for stat: "No
>> such file or directory". Could not examine file
>> "/var/sipxdata/cfdata/servers" in readfile. System error for stat: "No
>> such file or directory". Could not examine file
>> "/var/sipxdata/cfdata/servers" in readfile. System error for stat: "No
>> such file or directory". Could not examine file
>> "/var/sipxdata/cfdata/servers" in readfile. System error for stat: "No
>> such file or directory"
>> Error. Could not examine file "/var/sipxdata/cfdata/servers" in
>> readfile. System error for stat: "No such file or directory". Could not
>> examine file "/var/sipxdata/cfdata/servers" in readfile. System error
>> for stat: "No such file or directory". Could not examine file
>> "/var/sipxdata/cfdata/servers" in readfile. System error for stat: "No
>> such file or directory". Could not examine file
>> "/var/sipxdata/cfdata/servers" in readfile. System error for stat: "No
>> such file or directory". Could not examine file
>> "/var/sipxdata/cfdata/servers" in readfile. System error for stat: "No
>> such file or directory". Could not examine file
>> "/var/sipxdata/cfdata/servers" in readfile. System error for stat: "No
>> such file or directory". Could not examine file
>> "/var/sipxdata/cfdata/servers" in readfile. System error for stat: "No
>> such file or directory". Could not examine file
>> "/var/sipxdata/cfdata/servers" in readfile. System error for stat: "No
>> such file or directory". Could not examine file
>> "/var/sipxdata/cfdata/servers" in readfile. System error for stat: "No
>> such file or directory"
>>
>> Failure to run command /usr/bin/sipxagent -v  -d setup. See
>> /var/log/sipxpbx/sipxagent.log for details. After you
>> have addressed the issue, you may rerun this script.
>>
>>
>> -=[ Send Profiles Error ]=-
>>
>> tail /var/log/sipxpbx/sipxagent.log
>>
>> cf3>
>> ........................................................................
>> ...
>> cf3>  * Hailing 205.176.100.134 : 5308, with options "-v    -K" (serial)
>> cf3>
>> ........................................................................
>> ...
>> cf3> No existing connection to 205.176.100.134 is established...
>> cf3> Set cfengine port number to 5308 = 5308
>> cf3> Set connection timeout to 10
>> cf3>  -> Connect to 205.176.100.134 = 205.176.100.134 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-205.176.100.134.pub
>> cf3>  -> Could not map key file to new format - we have no digest yet
>> (using /etc/sipxpbx/.cfagent/ppkeys/sipx-205.176.100.134.pub)
>> cf3> Couldn't recv
>> cf3>  !!! System error for recv: "Connection reset by peer"
>> cf3> Protocol transaction broken off (1)
>> cf3>  !!! System reports error for recv: "Connection reset by peer"
>> cf3> I: Report relates to a promise with handle ""
>> cf3> I: Promise is made internally by cfengine
>> cf3>  !! Authentication dialogue with 205.176.100.134 failed
>> cf3> Unable to establish connection with 205.176.100.134
>> cf3>  -> No suitable server responded to hail
>>
>>
>> _______________________________________________
>> sipx-dev mailing list
>> [email protected]
>> List Archive: http://list.sipfoundry.org/archive/sipx-dev/
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev/

Reply via email to