search

swallowcc / rfc5766-turn-server

Automatically exported from code.google.com/p/rfc5766-turn-server
0 stars 0 forks source link

Endless loop writting "socket to be closed: Bad file descriptor" on log file #123

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Force a webrtc client to connect via TCP

What is the expected output? What do you see instead?

The following line is repeated endessly untill HD if full
66: session 000000000000000003: socket to be closed: Bad file descriptor (local 
192.168.25.32:58886, remote )

What version of the product are you using? On what operating system?
Latest on ubuntu server 64

Please provide any additional information below.

Original issue reported on code.google.com by sergio.g...@gmail.com on 21 Apr 2014 at 8:33

Attachments:

GoogleCodeExporter commented 9 years ago 
that's just a loggin problem, to be fixed in 3.2.3.6

Original comment by mom040...@gmail.com on 21 Apr 2014 at 9:26

GoogleCodeExporter commented 9 years ago

Original comment by mom040...@gmail.com on 21 Apr 2014 at 9:27

GoogleCodeExporter commented 9 years ago

Original comment by mom040...@gmail.com on 21 Apr 2014 at 9:27

GoogleCodeExporter commented 9 years ago 
Be aware that it fills the HD and the CPU goes to 100% so it is a critical 
issue IMO, got back to an older version which was working ok.

Original comment by sergio.g...@gmail.com on 21 Apr 2014 at 9:29

GoogleCodeExporter commented 9 years ago 
Which older version was working OK ?
Thanks
Oleg

Original comment by mom040...@gmail.com on 21 Apr 2014 at 9:46

GoogleCodeExporter commented 9 years ago 
A quite old one, compiled from source svn revision: 1051

Original comment by sergio.g...@gmail.com on 21 Apr 2014 at 9:48

GoogleCodeExporter commented 9 years ago 
Sergio, I need some help to figure it out:

1) What exactly did you compile ? Did you take the SVN version from trunk ? 

2) If yes, then can you test it with the "official" sources released as 3.2.3.5 
? (branch branches/v3.2) ? 

3) Can you take the latest from branches/v3.2 and try it (RC 3.2.3.6) ?

4) Please provide more log, beyond the 66 second.

We do not support the code in .../trunk, that code is for development only.

Original comment by mom040...@gmail.com on 21 Apr 2014 at 11:25

GoogleCodeExporter commented 9 years ago 
1,2) The compiled version is the one that works, the error happened with 
turnserver-3.2.3.5-debian-wheezy-ubuntu-mint-x86-64bits.tar.gz  

3) Not sure if I can test tiwh 3.2.3.6 as the server neededs to be used for 
some tests, I will try to provide more info as soon as we can. 

4) Sure 

66: session 000000000000000003: socket to be closed: Bad file descriptor (local 
192.168.25.32:58886, remote )
66: session 000000000000000003: socket to be closed: Bad file descriptor (local 
192.168.25.32:58886, remote )
66: session 000000000000000003: socket to be closed: Bad file descriptor (local 
192.168.25.32:58886, remote )
66: session 000000000000000003: socket to be closed: Bad file descriptor (local 
192.168.25.32:58886, remote )
66: session 000000000000000003: socket to be closed: Bad file descriptor (local 
192.168.25.32:58886, remote )
66: session 000000000000000003: socket to be closed: Bad file descriptor (local 
192.168.25.32:58886, remote )
66: session 000000000000000003: socket to be closed: Bad file descriptor (local 
192.168.25.32:58886, remote )
66: session 000000000000000003: socket to be closed: Bad file descriptor (local 
192.168.25.32:58886, remote )
66: session 000000000000000003: socket to be closed: Bad file descriptor (local 
192.168.25.32:58886, remote )
66: session 000000000000000003: socket to be closed: Bad file descriptor (local 
192.168.25.32:58886, remote )

;)

The line is repeated until the disk is filled.

Original comment by sergio.g...@gmail.com on 22 Apr 2014 at 7:36

GoogleCodeExporter commented 9 years ago 
That's very strange. As far as I can see, there is no way that that message may 
be printed so many times.

Could you please do the following for me:

1) Compile version 3.2.3.5 by yourself, from the source tarball, and test it.
2) Compile the latest sources from branches/v3.2/ (3.2.3.6) and test them.

I suspect that something might be wrong with the Debian package. Of course we 
tested the scenario that you described and we could not find anything wrong.

Thanks
Oleg

Original comment by mom040...@gmail.com on 22 Apr 2014 at 7:46

GoogleCodeExporter commented 9 years ago 
Fixed in 3.2.3.6

Original comment by mom040...@gmail.com on 23 Apr 2014 at 8:33

GoogleCodeExporter commented 9 years ago 
I think that I found the very core reason why that is happening. I fixed the 
symptoms in 3.2.3.6 but I'll fix the core problem in 3.2.3.7.

Original comment by mom040...@gmail.com on 23 Apr 2014 at 9:56