sabnzbd gobbling up ports???
Posted: November 26th, 2012, 3:03 am
So I've had this weird situation lately - after sitting idle for a while, my internet craps out. This started happening after I moved to Windows 8. Literally, my internet completely craps out - where I can't get to web pages or anything. I can ping, tracert, but web pages or anything else states blah blah blah can't be reached. Basically, anything that has a dedicated port or already connected is fine.
Checked windows logs and was getting this error message : "A request to allocate an ephemeral port number from the global TCP port space has failed due to all such ports being in use." This message completely tripped me up so of course I consulted the googles. Someone suggested running an netstat -nbt to see what was running. A condensed version of the result is this:
TCP 127.0.0.1:9090 127.0.0.1:49163 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49165 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49169 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49172 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49179 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49180 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49181 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49185 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49186 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49188 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49191 CLOSE_WAIT
[SABnzbd.exe]
This goes on and on (with port numbers continuing to go up) until the results file just kinda craps out and can't take anymore. The specfic command i'm running to get this is netstat -nbt > c:\netstatnbt.txt . (initially I just ran netstat -nbt and got the above, then restarted sabn and things were fine.)
I fixed it initially and bopped into the IRC chat to ask those guys about it, and they'd never heard of this before. The other thing they told me to do when it happened again was run netstat -an | more . Well I got some interesting results from that as well. partial is below -
TCP 127.0.0.1:9090 0.0.0.0:0 LISTENING
TCP 127.0.0.1:9090 127.0.0.1:49163 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49165 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49169 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49172 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49179 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49180 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49181 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49185 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49186 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49188 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49191 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49196 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49197 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49199 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49203 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49204 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49210 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49212 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49217 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49219 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49221 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49224 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49227 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49229 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49231 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49236 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49237 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49240 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49257 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49258 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49268 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49273 CLOSE_WAIT
And again it goes on and on. I have the full log files if y'all need to see them. Any thoughts guys why it would just start gobbling ports like that???
Thanks! Also, I'm on Windows 8 64-bit. Let me know if you need further PC specs.
Checked windows logs and was getting this error message : "A request to allocate an ephemeral port number from the global TCP port space has failed due to all such ports being in use." This message completely tripped me up so of course I consulted the googles. Someone suggested running an netstat -nbt to see what was running. A condensed version of the result is this:
TCP 127.0.0.1:9090 127.0.0.1:49163 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49165 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49169 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49172 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49179 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49180 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49181 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49185 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49186 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49188 CLOSE_WAIT
[SABnzbd.exe]
TCP 127.0.0.1:9090 127.0.0.1:49191 CLOSE_WAIT
[SABnzbd.exe]
This goes on and on (with port numbers continuing to go up) until the results file just kinda craps out and can't take anymore. The specfic command i'm running to get this is netstat -nbt > c:\netstatnbt.txt . (initially I just ran netstat -nbt and got the above, then restarted sabn and things were fine.)
I fixed it initially and bopped into the IRC chat to ask those guys about it, and they'd never heard of this before. The other thing they told me to do when it happened again was run netstat -an | more . Well I got some interesting results from that as well. partial is below -
TCP 127.0.0.1:9090 0.0.0.0:0 LISTENING
TCP 127.0.0.1:9090 127.0.0.1:49163 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49165 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49169 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49172 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49179 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49180 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49181 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49185 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49186 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49188 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49191 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49196 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49197 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49199 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49203 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49204 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49210 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49212 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49217 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49219 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49221 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49224 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49227 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49229 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49231 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49236 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49237 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49240 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49257 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49258 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49268 CLOSE_WAIT
TCP 127.0.0.1:9090 127.0.0.1:49273 CLOSE_WAIT
And again it goes on and on. I have the full log files if y'all need to see them. Any thoughts guys why it would just start gobbling ports like that???
Thanks! Also, I'm on Windows 8 64-bit. Let me know if you need further PC specs.