MongoDB can't add new replica set member [rsSync] SEVERE: Got signal: 6
In the dump you have above, I see this error


  SocketException: remote: xx.xx.xx.xx:27017 error: 9001 socket
  exception [RECV_ERROR] server [168.63.252.61:27017]
  2014-11-02T22:53:29.099+0000 [rsSync] DBClientCursor::init call()
  failed 2014-11-02T22:53:29.307+0000 [rsSync] replSet initial sync
  exception: 13386 socket error for mapping query 0 attempts remaining
  2014-11-02T22:53:36.113+0000 [conn2013] end connection xx.xx.xx.xx:


Which indicates that there is a socket exception error. To me that means that the configuration of a replica is incorrect or the host definded in the replica set configuration can't be contacted (firewall, network issues, mongodb not running)

STARTUP2 indicates that threads were forked for replication. While in the STARTUP2 state, the member creates threads to handle internal replication operations, and then the member transitions to the:replstate:RECOVERING state. During initial sync, members stay in:replstate:STARTUP2 until the all data transfers and all indexes finishing building. Members in the STARTUP2 state are not eligible to vote.

Running rs.status() from the primary will show you how the primary sees the secondaries and what address (host/port) it's using to contact them. You can also run rs.status() from a secondary after running the rs.slaveOK() command. 

Try connnecting from the secondary to the primary and vis-versa using the mongo client.
Or you can use telnet mongo_host mongo_port_number from either server to see if both are listening to the ports you've defined.