HTTP Request error and network connection issue

Christian

New member
Hi Dmitry,

  I want to report the following issue that occurs after RB is being up and running for over 2 weeks.
It starts with getting http request errors "Could not bind socket" and within a few hours later radio streams also starts to dysfonction. It's not staight forward but steams are getting discontinued and after some more time RB disconnects/reconnects continusly from streaming servers.
As you see in the screen shot the google.com DNS resolution and ping is working. Also Dropbox is in synchronisation. So network is fine. See attachement

I know that my environment is not conventional running on Virtual Machine with specific host internal networking but do you have other users reporting this ?

Christian
http://www.clubbingstation.com
 

Attachments

  • http request fail.gif
    http request fail.gif
    190.7 KB · Views: 440
Hi Christian

How many HTTP requests are you using? In the log there are 2 requests, and both of them are failing. Are there any others which still work?

This is very strange as this error usually appears when starting a server, but RB doesn't do it for HTTP request - it acts as a client.
Please open the report file (Settings->Open report folder) and see the full error text, it can be something like
Code:
Could not bind socket to port 80: Address already in use.
. Maybe it'll give some clues...

Good news, I already have some ideas which might resolve this.

Regarding other reports... I don't recall any similar reports. There was another issue reported recently, when HTTP request was rejected because of User-Agent property, but that's another case.
 
Also, when it happens again, please run command line and run the
Code:
netstat -n
command and post the results here.
 
Hi Dmitry,

I am running 2 http requests.
Here is the error I am getting :


12:18:04;error;"HTTP Request (#0) error: Could not bind socket. Address and port are already in use.";
12:18:04;error;"HTTP Request (#1) error: Could not bind socket. Address and port are already in use.";

I am running 2 RB here is the netstat -n from the one that was restartes 2days 6 hours ago.
  Proto  Adresse locale        Adresse distante      Etat
  TCP    10.42.43.102:1025      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1035      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1048      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1056      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1064      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1075      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1082      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1094      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1105      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1115      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1126      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1138      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1149      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1160      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1170      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1180      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1191      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1201      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1213      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1221      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1232      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1242      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1255      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1264      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1275      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1283      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1293      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1303      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1314      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1324      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1335      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1344      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1353      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1365      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1376      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1384      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1396      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1404      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1417      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1426      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1441      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1448      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1458      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1469      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1478      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1491      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1500      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1507      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1520      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1531      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1534      184.73.168.78:443      CLOSE_WAIT
  TCP    10.42.43.102:1542      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1544      199.47.218.160:443    CLOSE_WAIT
  TCP    10.42.43.102:1552      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:1555      199.47.217.174:443    CLOSE_WAIT
  TCP    10.42.43.102:4512      10.42.43.100:80        ESTABLISHED
  TCP    10.42.43.102:4513      10.42.43.100:80        ESTABLISHED
  TCP    10.42.43.102:4518      199.47.219.148:80      ESTABLISHED
  TCP    10.42.43.102:4532      10.42.43.42:17500      ESTABLISHED
  TCP    10.42.43.102:4534      31.12.64.108:19933    ESTABLISHED
  TCP    10.42.43.102:4543      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4552      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4562      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4571      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4579      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4589      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4596      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4608      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4618      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4627      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4635      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4646      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4654      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4674      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4675      199.47.217.178:443    CLOSE_WAIT
  TCP    10.42.43.102:4689      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4697      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4705      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4714      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4722      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4732      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4740      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4750      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4759      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4769      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4777      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4791      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4803      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4806      10.42.43.101:17500    ESTABLISHED
  TCP    10.42.43.102:4807      10.42.43.100:8051      ESTABLISHED
  TCP    10.42.43.102:4813      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4825      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4834      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4845      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4852      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4861      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4872      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4879      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4889      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4896      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4903      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4914      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4922      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4930      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4940      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4949      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4960      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4968      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4978      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:4989      46.105.34.64:80        CLOSE_WAIT
  TCP    10.42.43.102:17500    10.42.43.42:1884      ESTABLISHED
  TCP    10.42.43.102:17500    10.42.43.101:1052      ESTABLISHED
  TCP    127.0.0.1:1039        127.0.0.1:19872        ESTABLISHED
  TCP    127.0.0.1:19872        127.0.0.1:1039        ESTABLISHED

If I guess correctly there is a problem with the http request on 46.105.34.64 that is not closing the connexion?

Christian
 
Yes, you're right.
Even when software application closes the socket, Windows keeps it in the CLOSE_WAIT state... When all TCP slots are occupied, it cannot open new connections. That's why it cannot perform HTTP requests and establish server connections anymore.

As we now know the cause, I'm sure it will be fixed in the next update.
 
Back
Top