Go-ethereum: Failed to raise file descriptor allowance: invalid argument

Created on 26 Feb 2019  路  11Comments  路  Source: ethereum/go-ethereum

System information

Geth version: 1.8.23-stable
OS & Version: OSX

Expected behaviour

Running light node.

Actual behaviour

INFO [02-26|22:38:39.409] Maximum peer count                       ETH=0 LES=100 total=25
Fatal: Failed to raise file descriptor allowance: invalid argument

Steps to reproduce the behaviour

I was running a light node on ropsten without problems but I started getting sync errors, so I updated the client and the error above started poping up, I tried to remove lightdata but the error still persists.

Most helpful comment

This is an issue in Go 1.12. We've added a workaround on master. IF you build with Go 1.11.5 the invalid argument will go away.

All 11 comments

So the individual error is being thrown in common/fdlimit/fdlimit_unix in the raise function. It looks like from there something is going wrong with the syscall, https://golang.org/pkg/syscall/. Maybe $GOOS or $GOARCH got set incorrectly as that is tied to syscall?

We hit the same issue. Note that it manifests itself immediately after geth starts, so there's no opportunity to use ulimit to see what kinds of limits are set. 1.8.22 appears to be unaffected.

19177 Looks like it could be related?

This is an issue in Go 1.12. We've added a workaround on master. IF you build with Go 1.11.5 the invalid argument will go away.

@karalabe It is a pain in the ass manually fixing since I'm otherwise installing trough brew. Any timeline on official update?

@karalabe I have the same Q as @MoMannn ?

We'll push out a stable release to fix this on Monday.

@karalabe Thank you for the heads up, and all the hard work you are doing. Really appreciated!!!!!

Is this always going to persist on version 1.8.23? Reason I am asking is I hard forked from this version so currently going to use this one.

I've tried go 1.11.5 and the latest 1.13.3 and both do not work.

Yes, you need a fixed code to handle Go 1.12+'s changed behavior.

Hm ok, guess I might have to update the nodes. Thanks.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

VoR0220 picture VoR0220  路  3Comments

aakilfernandes picture aakilfernandes  路  3Comments

keitaj picture keitaj  路  3Comments

freshonline picture freshonline  路  3Comments

vogelito picture vogelito  路  3Comments