-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
0.9.0_rc25: all socket ports used up #2310
Comments
Maybe this is relevant: Can’t create new network sockets? Maybe it isn’t user limits… (from the blog of Oliver Hookins and Angela Collins) |
After a reboot and InfluxDB reinstall, the TIME_WAIT socket count didn't start going up until I started to write data. When writing, I the number went through the roof again, and I saw this in
|
@akaihola I think we know what is causing this and should have an fix for rc26. |
Seeing the same behavior with rc31. reverting to rc30 gets rid of the problem |
+1 Having the same issue with rc31 (influxdb-0.9.0_rc31-1.x86_64.rpm) |
+1, reverting to rc30 fixed it. |
We are seeing client connection open around 24,863. Hence influx can not accept more connections. Is there anyway to increase the conenction limits. I am having the issue with influx 0.9.0-rc30. |
I'm fairly certain this will be fixed in RC32 later today. In an attempt to keep the issue list clean for v0.9.0, I'm going to close this out for now, but let me know if it reappears. |
+1, I am having this same issue with rc32. Running tests against Influx, everything works fine up to a point and then I get:
Restarting |
@toddboom, what is the status of this? This seems to be very common problem if we have burst of input. |
@lokeshverizon are you experiencing this issue with 0.9.0 final? What OS? How did you install? |
We cannot reproduce this against 0.9.0 final. Closing issue until there are repro steps against 0.9.0 |
fix(ui/onboarding): Prevent unskippable steps from being skipped with progress bar
When I install and start RC25 on my Ubuntu 14.04 box, I run out of local ports in a couple of minutes. As a result, other software isn't able to open TCP sockets.
I found one similar report in the freenode IRC log.
$
The text was updated successfully, but these errors were encountered: