When I try to start unicorn I get this error:
/home/.rvm/gems/ruby-2.1.0/gems/kgio-2.8.1/lib/kgio_ext.so: [BUG]
Segmentation fault ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
How can I fix this problem?
On Mon, May 5, 2014 at 3:51 AM, Ed Ed [email protected] wrote:
When I try to start unicorn I get this error:
/home/.rvm/gems/ruby-2.1.0/gems/kgio-2.8.1/lib/kgio_ext.so: [BUG]
Segmentation fault ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]How can I fix this problem?
WAG: figure out why your unicorn is apparently being started in the
context of the very old system ruby 
Providing actual information – unicorn config file, startup invocation,
platform, etc. – might help others help you on that …
–
Hassan S. ------------------------ [email protected]
twitter: @hassan
WAG: figure out why your unicorn is apparently being started in the
context of the very old system ruby
I think that it isn’t the main problem 
Ok, I attach unicorn.sh file in my reply.
Really? So the actual error message isn’t relevant to your problem?
ruby -v gives me 2.1.0, but I can’t understand why it try ruby 1.8.7
On Mon, May 5, 2014 at 7:33 AM, Ed Ed [email protected] wrote:
WAG: figure out why your unicorn is apparently being started in the
context of the very old system rubyI think that it isn’t the main problem
Really? So the actual error message isn’t relevant to your problem?
Segmentation fault ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
Good luck with that, then.
–
Hassan S. ------------------------ [email protected]
twitter: @hassan
What is the default PATH of the user that runs startup scripts?
when I call echo $PATH there exist path to my ruby 2.1.0 bin
On Mon, May 5, 2014 at 8:42 AM, Ed Ed [email protected] wrote:
ruby -v gives me 2.1.0, but I can’t understand why it try ruby 1.8.7
/etc/init.d/ scripts are not typically run as “you”.
What is the default PATH of the user that runs startup scripts?
Does it include your rvm path? If not, then it’s hardly a surprise
that it’s using the system ruby.
–
Hassan S. ------------------------ [email protected]
twitter: @hassan
Two things:
- Add an echo to output the version of ruby used
- Let the first/initialization command be to use the right version of
ruby, say something likervm use ruby-2.x.x
Hope it helps!
Cheers,
Karthik
Jus’ to be clear, add the said two things in your unicorn.sh script and
see
the output to help debugging. Makes sense?
Two things:
- Add an echo to output the version of ruby used
- Let the first/initialization command be to use the right version of
ruby, say something likervm use ruby-2.x.x
rvm current and default is set to ruby-2.1.0
Ok, I have done that from script and it shows that ruby is 2.1.0, but
the error with kgio gem still exists.
On 6 May 2014 13:58, Ed Ed [email protected] wrote:
Ok, I have done that from script and it shows that ruby is 2.1.0, but
the error with kgio gem still exists.
What does the error say now? Copy/paste here to avoid typos.
Colin
What does the error say now? Copy/paste here to avoid typos.
The error is written in my question.
On 6 May 2014 13:58, Ed Ed [email protected] wrote:
Ok, I have done that from script and it shows that ruby is 2.1.0, but
the error with kgio gem still exists.
Googling for
kgio segmentation fault
found this as the first hit, is it helpful?
Colin
Googling for
kgio segmentation fault
found this as the first hit, is it helpful?
Question | DigitalOcean
Yes, I have already viewed that.It didn’t help me.
On 6 May 2014 16:52, Ed Ed [email protected] wrote:
What does the error say now? Copy/paste here to avoid typos.
The error is written in my question.
So it is still running the wrong ruby?
Colin
So it is still running the wrong ruby?
It says that ruby is 2.1.0, but is still gives the error.
The error you posted says it is 1.8.7
I understand that and can’t find the solution.
On 7 May 2014 16:43, Ed Ed [email protected] wrote:
So it is still running the wrong ruby?
It says that ruby is 2.1.0, but is still gives the error.
The error you posted says it is 1.8.7
Colin
On 8 May 2014 09:00, Ed Ed [email protected] wrote:
The error you posted says it is 1.8.7
I understand that and can’t find the solution.
What change did you make following the link I posted?
Colin