Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EAGAIN Error #24

Closed
GuySawyer opened this issue Jul 28, 2014 · 3 comments
Closed

EAGAIN Error #24

GuySawyer opened this issue Jul 28, 2014 · 3 comments

Comments

@GuySawyer
Copy link

I am getting a resource unavailable error which I think is related to onoff. Have a look at the error message. I have checked all my other modules, and they are not causing the error.

fs.js:476
  var r = binding.read(fd, buffer, offset, length, position);
                  ^
Error: EAGAIN, resource temporarily unavailable
    at Object.fs.readSync (fs.js:476:19)
    at Object.fs.readFileSync (fs.js:310:28)
    at Object.exports.readAIN (/usr/local/lib/node_modules/bonescript/hw_capemgr.js:214:30)
    at Object.f.analogRead (/usr/local/lib/node_modules/bonescript/index.js:229:15)
    at null.<anonymous> (/home/debian/node_modules/thing-client/beagle1.js:648:18)
    at wrapper [as _onTimeout] (timers.js:252:14)
    at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

Your help will be appreciated.
Thanks
Regards Guy

@fivdi
Copy link
Owner

fivdi commented Jul 28, 2014

The error occurs on line 214 of hw_capemgr.js in BoneScript, and not in onoff. It occurs when accessing the sysfs file for one of the BeagleBones analog input pins. onoff never accesses the files for analog input so I can't imagine it being in any way related to the error. onoff doesn't appear in the stack trace either. Does your application actually use onoff?

@GuySawyer
Copy link
Author

Ah, ok. That makes sense. Yes, I am using onoff. But it looked to me like one of my readSync operations was creating the error.

Obviously not. I will look into the bonescript issue.
Thanks for your quick response, and help.

Regards

@fivdi
Copy link
Owner

fivdi commented Jul 28, 2014

Ok, I'll close this one so,

@fivdi fivdi closed this as completed Jul 28, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants