Project

General

Profile

Actions

Bug #12432

closed

The process has forked and you cannot use this CoreFoundation functionality safely. You MUST exec()

Added by hadasl (Hadas Leonov) almost 8 years ago. Updated almost 8 years ago.

Status:
Third Party's Issue
Assignee:
-
Target version:
-
[ruby-core:75734]

Description

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) ruby_2016-05-26-210152.crash hadasl (Hadas Leonov), 05/26/2016 09:43 PM
bug-12432.log (21.9 KB) bug-12432.log nobu (Nobuyoshi Nakada), 05/27/2016 07:09 AM

Updated by nobu (Nobuyoshi Nakada) almost 8 years ago

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.

Updated by hadasl (Hadas Leonov) almost 8 years ago

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.

Updated by normalperson (Eric Wong) almost 8 years ago

wrote:

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.

Maybe try disabling "preload_app" in unicorn and
not loading gems in the unicorn config file.

Actions

Also available in: Atom PDF

Like0
Like0Like0Like0