Log of the #duraspace-ff channel on chat.freenode.net

Using timezone: Eastern Standard Time
* eddies leaves00:19
* jcoyne leaves00:50
* nbanks joins02:05
* nbanks leaves02:13
* nbanks joins02:29
* nbanks leaves02:44
* github-ff joins14:18
[fcrepo4] cbeer pushed 1 new commit to master: http://git.io/x7RHKg
fcrepo4/master 9a53bdc Chris Beer: bump upstream dependencies
* github-ff leaves
<bljenkins>Project fcrepo-fixity-corrupter build #66: SUCCESS in 33 sec: http://ci.projectblacklight.org/jenkins/job/fcrepo-fixity-corrupter/66/14:31
Project fcrepo-fixity build #247: STILL UNSTABLE in 3 min 27 sec: http://ci.projectblacklight.org/jenkins/job/fcrepo-fixity/247/14:34
* jcoyne joins
<bljenkins>Project fcrepo-kitchen-sink build #353: SUCCESS in 5 min 41 sec: http://ci.projectblacklight.org/jenkins/job/fcrepo-kitchen-sink/353/14:37
* jcoyne leaves15:12
* awoods__ joins18:46
<aawoods>cbeer/barmintor: As an experiment, I am setting up a three node cluster on some AWS servers. Each node comes up fine and recognizes itself as a "new cluster view", but no node recognizes the other two nodes. As far as I can tell, the only updates I need to make are in the /etc/default/tomcat7 file, adding something like: JAVA_OPTS="${JAVA_OPTS} -Djgroups.tcp.address= -Djgroups.tcpping.initial_hosts='[7800],1018:50
.0.0.104[7800],[7800]' -Dfcrepo.ispn.numOwners=2 -Djava.net.PreferIPv4Stack=true"
am I missing something?
nope, there was nothing missed... the issue turned out to be AWS wanting internal-IPs instead of external ones. All is well.19:43
* aawoods leaves19:51
* jcoyne joins22:12
* jcoyne leaves23:06

Generated by Sualtam