From: blackbirdy@... Date: 2016-06-03T09:30:24+00:00 Subject: [ruby-core:75831] [Ruby trunk Bug#12432] The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec() Issue #12432 has been updated by Hadas Leonov. Nobuyoshi Nakada wrote: > Seems an issue with unicorn and rcdk gem caused by a system restriction. > I think you should `exec` or `spawn` somewhere, maybe before requiring that gem, as the message says, but don't know about both. > Possibly maintainers of that gem may know. Unfortunately, the maintainers of the gem haven't updated it since 2006, when it was written for Ruby 1.8.4. I was hoping to bypass this by some external solution like some mac file setting or switching the java version, but I cannot go back to Ruby < 1.9.3. Thanks for the hint though, I'll update if I get the gem maintainers to answer. ---------------------------------------- Bug #12432: The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec() https://bugs.ruby-lang.org/issues/12432#change-59010 * Author: Hadas Leonov * Status: Third Party's Issue * Priority: Normal * Assignee: * ruby -v: * Backport: 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN ---------------------------------------- Hi all, I'm Running a server with ruby 2.1.5 with Rails 3.2.21 on Mac OS X El Capitan. The server works until I try to look at the existing data files or upload new data files into the server - then I get a "connection reset" in the browser, and the error below. Has anybody encountered anything like this, or alternatively knows what I can do to fix it? Thanks in advance, Hadas ---Files-------------------------------- ruby_2016-05-26-210152.crash (54.4 KB) bug-12432.log (21.9 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: