Unhandled exception (StandardError): No buffer space available #66

Open
grempe opened this Issue Sep 20, 2011 · 8 comments

Comments

Projects
None yet
6 participants

grempe commented Sep 20, 2011

I am seeing the following errors in /var/log/syslog continuously on some of my servers running in the EC2 cloud on Ubuntu 10.04.

It seems to be raised from the following C code somewhere:

https://github.com/mojombo/god/blob/master/ext/god/netlink_handler.c#L26

Sep 19 20:44:40 localhost god[4886]: Unhandled exception (StandardError): No buffer space available#012/usr/lib/ruby/gems/1.8/gems/god-0.11.0/bin/../lib/god/event_handler.rb:62:in `handle_events'#012/usr/lib/ruby/gems/1.8/gems/god-0.11.0/bin/../lib/god/event_handler.rb:62:in `start'#012/usr/lib/ruby/gems/1.8/gems/god-0.11.0/bin/../lib/god/event_handler.rb:60:in `loop'#012/usr/lib/ruby/gems/1.8/gems/god-0.11.0/bin/../lib/god/event_handler.rb:60:in `start'#012/usr/lib/ruby/gems/1.8/gems/god-0.11.0/bin/../lib/god/event_handler.rb:59:in `initialize'#012/usr/lib/ruby/gems/1.8/gems/god-0.11.0/bin/../lib/god/event_handler.rb:59:in `new'#012/usr/lib/ruby/gems/1.8/gems/god-0.11.0/bin/../lib/god/event_handler.rb:59:in `start'#012/usr/lib/ruby/gems/1.8/gems/god-0.11.0/bin/../lib/god/cli/run.rb:70:in `default_run'#012/usr/lib/ruby/gems/1.8/gems/god-0.11.0/bin/../lib/god/cli/run.rb:100:in `run_daemonized'#012/usr/lib/ruby/gems/1.8/gems/god-0.11.0/bin/../lib/god/cli/run.rb:91:in `fork'#012/usr/lib/ruby/gems/1.8/gems/god-0.11.0/bin/../lib/god/cli/run.rb:91:in `run_daemonized'#012/usr/lib/ruby/gems/1.8/gems/god-0.11.0/bin/../lib/god/cli/run.rb:21:in `dispatch'#012/usr/lib/ruby/gems/1.8/gems/god-0.11.0/bin/../lib/god/cli/run.rb:8:in `initialize'#012/usr/lib/ruby/gems/1.8/gems/god-0.11.0/bin/god:122:in `new'#012/usr/lib/ruby/gems/1.8/gems/god-0.11.0/bin/god:122#012/usr/bin/god:19:in `load'#012/usr/bin/god:19
$ god check
using event system: netlink
starting event handler
forking off new process
forked process with pid = 31687
killing process
[ok] process exit event received
$ uname -a
Linux HOSTNAME 2.6.35-22-virtual #35-Ubuntu SMP Sat Oct 16 23:57:40 UTC 2010 i686 GNU/Linux
$ ruby --version
ruby 1.8.7 (2010-06-23 patchlevel 299) [i686-linux]
$ god --version
Version 0.11.0

Just got the same error.
Ubuntu 11.04 VM running via KVM.

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 11.04
Release:    11.04
Codename:   natty

# uname -a
Linux HOSTNAME 2.6.38-8-server #42-Ubuntu SMP Mon Apr 11 03:49:04 UTC 2011 x86_64 x86_64 x86_64   GNU/Linux

# ruby --version
ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 2011.03

# god --version
Version 0.11.0

benr75 commented Sep 30, 2011

Ditto, JUST started happening.

# god --version
Version 0.11.0

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 10.10
Release:    10.10
Codename:   maverick

# ruby --version
ruby 1.8.7 (2011-02-18 patchlevel 334) [x86_64-linux], MBARI 0x6770, Ruby Enterprise Edition 2011.03

# uname -a
Linux ip-10-218-31-205 2.6.35-25-virtual #44-Ubuntu SMP Fri Jan 21 20:39:04 UTC 2011 x86_64 GNU/Linux

benr75 commented Sep 30, 2011

TURNS OUT, god is not at fault. Looking at my god logs it turns out it was a gem issue, and it was simply the worker not being able to fire up. After installing the missing dependencies we were good to go.

geremy commented Nov 4, 2011

This seems to have just started with me with no apparent changes to the system . . . do you remember which dependencies you had to install to fix it?

benr75 commented Nov 4, 2011

Just did a bundle install and it solved the problem.

geremy commented Nov 4, 2011

Interesting . . . thank you.

alter I intall bundle, it still have the same errors :(

lemsx1 commented Oct 14, 2014

I got the same error in RHEL 6.2. Then I found this:
http://stackoverflow.com/questions/12253342/prevent-no-buffer-space-available-error-in-ruby

Is it possible that god just doesn't properly close resources (like sockets) if something else prevents it from properly opening said resource? is it missing ensure somewhere?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment