vincenthuynh

We had encountered this message as well. It was frustrating as it caused Fabio to stop updating routes. In our case, it turned out to be a bad service tag...

We were hoping to use this feature too but it looks like it wasn't released in `1.5.13`. It's still in master branch. You'll have to build it yourself. See: https://github.com/fabiolb/fabio/pull/626

We went through and reaped any run-away processes this morning. I'll keep an eye on it again after the weekend and grab some logs if I find any.

I was able to find a run-away process on one of our other nodes: ``` $ps ... nobody 30815 0.1 1.0 6982276 554908 ? Ssl Jan11 45:51 /usr/lib/jvm/jdk1.8.0_161/bin/java -server -Xmx1024m...

Hi again, We have some more information that might help with debugging the orphaned processes: Below is a job that uses a static port. It unexpectedly terminates and then is...

Hi @tgross @notnoop Could someone shed some light on what may be causing this error with the Java driver? We tend to see the rouge processes happen on a client...

I was able to get this to work on `vagrant 1.6.3` by manually installing nokogiri with gem that comes natively with vagrant: `/opt/vagrant/embedded/bin/gem install --install-dir ~/.vagrant.d/gems nokogiri -v '1.6.3.1'` (You...