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

Terminal Errors on Mac #298

Closed
RowdyMuncher opened this issue Feb 4, 2023 · 4 comments
Closed

Terminal Errors on Mac #298

RowdyMuncher opened this issue Feb 4, 2023 · 4 comments

Comments

@RowdyMuncher
Copy link

Second issue is that i am getting thousands of these errors every day in terminal running the latest version on Mac.
2023-02-04T03:40:49.085+1000 ERROR tcp-tpt go-tcp-transport@v0.2.4/tcp.go:52 failed to enable TCP keepalive {"error": "set tcp4 192.168.0.35:1234->43.134.4.59:4099: setsockopt: invalid argument"}
2023-02-04T03:40:49.085+1000 ERROR tcp-tpt go-tcp-transport@v0.2.4/tcp.go:52 failed to enable TCP keepalive {"error": "set tcp4 192.168.0.35:1234->43.128.250.133:4010: setsockopt: invalid argument"}
2023-02-04T03:40:49.086+1000 ERROR tcp-tpt go-tcp-transport@v0.2.4/tcp.go:52 failed to enable TCP keepalive {"error": "set tcp4 192.168.0.35:1234->65.21.78.197:4107: setsockopt: invalid argument"}
2023-02-04T03:40:50.087+1000 ERROR tcp-tpt go-tcp-transport@v0.2.4/tcp.go:52 failed to enable TCP keepalive {"error": "set tcp4 192.168.0.35:1234->138.201.61.40:5179: setsockopt: invalid argument"}
2023-02-04T03:40:51.088+1000 ERROR tcp-tpt go-tcp-transport@v0.2.4/tcp.go:52 failed to enable TCP keepalive {"error": "set tcp4 192.168.0.35:1234->119.198.72.212:4001: setsockopt: invalid argument"}
2023-02-04T03:43:53.703+1000 ERROR tcp-tpt go-tcp-transport@v0.2.4/tcp.go:52 failed to enable TCP keepalive {"error": "set tcp4 192.168.0.35:1234->46.4.32.49:4290: setsockopt: invalid argument"}
2023-02-04T03:45:49.628+1000 ERROR dht go-libp2p-kad-dht@v0.10.1/handlers.go:228 error retrieving record from datastore {"key": "/F5RHI3TTF4ACKCACCIQQFH5OJU374ZJXYUPUSXFMDG5QC2K5KFSGWQVUGROLI2NTHKJFCYDG", "error": "open /Users/efraimsilver/.btfs/datastore/056189.ldb: too many open files"}
2023-02-04T03:45:49.805+1000 ERROR dht go-libp2p-kad-dht@v0.10.1/handlers.go:228 error retrieving record from datastore {"key": "/F5RHI3TTF4ACKCACCIQQFH5OJU374ZJXYUPUSXFMDG5QC2K5KFSGWQVUGROLI2NTHKJFCYDG", "error": "open /Users/efraimsilver/.btfs/datastore/056189.ldb: too many open files"}
2023-02-04T03:53:51.390+1000 ERROR tcp-tpt go-tcp-transport@v0.2.4/tcp.go:52 failed to enable TCP keepalive {"error": "set tcp4 192.168.0.35:1234->195.201.61.47:3977: setsockopt: invalid argument"}

There seems to be two types of errors and I need to work out how to fix this please.

Awaiting your reply
Regards
Efraim

Desktop (please complete the following information):

  • OS: macOS Catalina
  • Version 10.15.7
  • iMac Late 2013
@RowdyMuncher
Copy link
Author

One of the errors coming up is

2023/02/06 07:20:40 http: Accept error: accept tcp4 127.0.0.1:5001: accept: too many open files; retrying in 5ms which seems to be coming up often in terminal. There must be some kind of fix for both as terminal is spewing out these errors so constantly that it's a nuisance. If someone could please answer both my questions as soon as they can i would be very much appreciative.
Cheers
Efraim

@CrCati
Copy link
Collaborator

CrCati commented Feb 6, 2023

Hi, @RowdyMuncher thank you very much for the feedback!
The community has fed back to the development team.

@penn202000
Copy link

'too many open files', this post may help(like the poster said: at your own risk) : https://superuser.com/questions/433746/is-there-a-fix-for-the-too-many-open-files-in-system-error-on-os-x-10-7-1

@CrCati CrCati closed this as completed Feb 10, 2023
@CrCati CrCati reopened this Feb 10, 2023
@CrCati
Copy link
Collaborator

CrCati commented Feb 16, 2023

Hi, @RowdyMuncher I can't reproduce the issue on my Mac(12.6.2, MacBook Pro (16-inch, 2019)). This thread may help: "libp2p/go-tcp-transport#115". We'll try some other tests again. Once we reproduce the issue, we'll let you know.

@CrCati CrCati closed this as completed Feb 17, 2023
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

3 participants