-
-
Notifications
You must be signed in to change notification settings - Fork 166
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
Error: EBADF: bad file descriptor, close #581
Comments
have you tried scuttlebot-release with those versions? I fear rolling back to an older version without a package-lock or shrinkwrap will just give you more inconsistencies in the module tree. |
I'm not seeing this anymore, so maybe it just had to do with my machine powering off, or a bunk npm install? This is a ghost bug, we can close. |
This is happening again, after not happening for awhile, re-opening. |
Just started seeing this as well, you're not alone. 👯♂️ |
@evbogue Could you try strace?
I'm seeing two instances of EBADF, but neither are being output to the terminal (only strace):
I'm going to keep this running and see whether I can capture the error that actually outputs to the terminal, but since it's sporadic it'd be great if you could do the same. When it outputs to the terminal, you should see a line that literally just says "Error: EBADF: bad file descriptor, close" on its own line without any strace prefix. |
Got one:
|
@evbogue Any chance you're also running this with something like? while true; do timeout 1h sbot server; done I'm wondering whether the issue is coming from |
It's evolving... $ cd ~/src/patchbay
$ electron index.js
STARTING electron
STARTING SBOT
LOADING config
Listening on undefined:8008 (multiserver net plugin)
listening on socket unix:/home/christianbundy/.ssb/socket
ssb-friends: stream legacy api used
Listening on localhost:8989 (ssb-ws)
ssb-server connecting longterm +0ms
ssb-server connecting longterm +2ms
ssb-server connecting attempt +2ms
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
[5192:1207/190853.264819:FATAL:scoped_file.cc(48)] Check failed: 0 == ret. : Bad file descriptor
#0 0x55b30b3945d7 <unknown>
#1 0x55b30b36696e <unknown>
#2 0x55b30b3671da <unknown>
#3 0x55b30b37c886 <unknown>
#4 0x55b30b350080 <unknown>
#5 0x55b30b34b1f9 <unknown>
#6 0x55b30c623ab7 <unknown>
#7 0x55b30c5576ae <unknown>
#8 0x55b30c550327 <unknown>
#9 0x55b30b3ab7bd <unknown>
#10 0x55b30b3b2923 <unknown>
#11 0x55b30b3b2e40 <unknown>
#12 0x55b30b3b25bc <unknown>
#13 0x55b30b3b0615 <unknown>
#14 0x55b30b3766c3 <unknown>
#15 0x7f76f83f6a9d start_thread
#16 0x7f76f3401b23 __GI___clone
Received signal 6
#0 0x55b30b3945d7 <unknown>
#1 0x55b30b39414f <unknown>
#2 0x7f76f84013c0 <unknown>
#3 0x7f76f333dd7f __GI_raise
#4 0x7f76f3328672 __GI_abort
#5 0x55b30b367442 <unknown>
#6 0x55b30b366f02 <unknown>
#7 0x55b30b3671da <unknown>
#8 0x55b30b37c886 <unknown>
#9 0x55b30b350080 <unknown>
#10 0x55b30b34b1f9 <unknown>
#11 0x55b30c623ab7 <unknown>
#12 0x55b30c5576ae <unknown>
#13 0x55b30c550327 <unknown>
#14 0x55b30b3ab7bd <unknown>
#15 0x55b30b3b2923 <unknown>
#16 0x55b30b3b2e40 <unknown>
#17 0x55b30b3b25bc <unknown>
#18 0x55b30b3b0615 <unknown>
#19 0x55b30b3766c3 <unknown>
#20 0x7f76f83f6a9d start_thread
#21 0x7f76f3401b23 __GI___clone
r8: 0000000000000000 r9: 00007f76dd85dce0 r10: 0000000000000008 r11: 0000000000000246
r12: 00007f76f36716c0 r13: 00007f76dd85e440 r14: 00007f76dd85e440 r15: 00007f76dd85e438
di: 0000000000000002 si: 00007f76dd85dce0 bp: 00007f76dd85e390 bx: 0000000000000006
dx: 0000000000000000 ax: 0000000000000000 cx: 00007f76f333dd7f sp: 00007f76dd85dce0
ip: 00007f76f333dd7f efl: 0000000000000246 cgf: 002b000000000033 erf: 0000000000000000
trp: 0000000000000000 msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace] |
i only read https://linux.die.net/man/2/epoll_ctl but I don't think -1 is a valid fdesc to pass there. Without a trace from the js side it's really hard to gues what is trying to do that... maaaybe if you gather the other |
I'm not running my local server in a restart loop. But, my computer has powered off a few times because I forget to check |
My concern is that somewhere in the stack we're doing something like: if (err) console.log(err) I'm not super concerned about the bad file descriptor, but I feel like we should at least be printing a stack trace. |
also getting this now after updating scuttle-shells sbot from 13.0 to latest.. I also fear my previous comment about multiple epoll sets might be unhelpful. keks suggested that this is what the v8 event loop uses global to schedule it's IO.. in that case there is not much to dig into.. just even more wondering about what part of our system tries to add -1 to it... sounds definitely like an ignored error. |
i see this error too. thought it might be caused because i use NetBSD, but this doesn't seems to be the case. |
I'm getting this too when trying to run my pub. Currently using ssb-server 13.5.2 /home/punkmonk/.ssb logging.level:notice
my key ID: iMgGq295k0QoORDrYHbn7vmGvGTForIHAhOq/uiJzh8=.ed25519
WARNING-DEPRECATION: ssb-links not installed as a plugin. If you are using git-ssb, ssb-npm or patchfoo please consider installing it
Listening on 159.203.94.136:8008 (multiserver net plugin)
Listening on 159.203.94.136:8989 (multiserver ws plugin)
ssb-friends: stream legacy api used
Error: EBADF: bad file descriptor, read........... (ooo:42.9%, ebt:80%)
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, read........... (ooo:42.9%, ebt:33.3%)
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, read........... (ooo:42.9%, ebt:66.7%)
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, close
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, read
Error: EBADF: bad file descriptor, close |
It looks like this is actually coming from pull-file: pull-stream/pull-file#6 |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
I'm seeing a lot of these in my terminal. I am using [email protected]. I'm not [email protected], because gossip is broken.
Is anyone else seeing this? Maybe I need to resync my db because something is corrupt?
The text was updated successfully, but these errors were encountered: