#34 butt socket timeout after 10 seconds

[Fleskalebas]

Hi Daniel,

First of all, thanks for this easy program! I use it for years without any complaints. However, since a couple of days now I have issues with streaming to icecast.

A snippet of the icecast log:

[2020-11-13  19:27:37] INFO source/source.c listener count on /mountpoint now 0
[2020-11-13  19:27:48] WARN source/source.c Disconnecting source due to socket timeout

If I check the butt GUI it still says: streaming....

To rule out an icecast problem I downloaded rocket broadcaster but also here, after 10 seconds the mountpoint disappears. I checked netstat and port 8000 is not in use.

After this, I downloaded Mixxx (another piece of software that can stream to icecast) and this one works flawlessly. So it looks like it's isolated to butt. Strangely enough it works fine on my dev machine (same setup, same versioning).

How can we approach this issue?

[Paul Higgins]

I'm having the same problem with version 0.1.20 running on Windows 10 Pro version 1909.

Here's a portion of the icecast debug log:

[2020-11-13 16:04:02] DBUG stats/stats.c update "/stream" listeners (0)
[2020-11-13 16:04:07] DBUG stats/stats.c update "/stream" total_bytes_read (0)
[2020-11-13 16:04:07] DBUG stats/stats.c update "/stream" total_bytes_sent (0)
[2020-11-13 16:04:12] DBUG stats/stats.c update "/stream" total_bytes_read (0)
[2020-11-13 16:04:12] DBUG stats/stats.c update "/stream" total_bytes_sent (0)
[2020-11-13 16:04:13] DBUG source/source.c last 1605308642, timeout 10, now 1605308653
[2020-11-13 16:04:13] WARN source/source.c Disconnecting source due to socket timeout
[2020-11-13 16:04:13] INFO source/source.c Source from 127.0.0.1 at "/stream" exiting

(I have the source-timeout in icecast set to 10.)

[Paul Higgins]

In my case, upgrading to version 0.1.25 seems to have resolved the problem.

[Daniel Nöthen]

Hello Guys, I am getting more and more messages of this kind. Fixing this has the highest priority right now. Unfortunately I did not find a way to reproduce this on my Windows machine what makes debugging very hard. Yesterday I did a 8 hour broadcast without any issues.... So if you find a way to reproduce this it would help me very much.

[Fleskalebas]

I have an older butt version (0.1.16) on my developer machine (running 20H2) and no problems there. The machine I am talking about is a Windows 2004 with butt 0.1.25.
Also hard for me to reproduce... I only did some testing with firewall on/off, ports in use testing, testing with icecast replacement...but nothing works.

Would be handy to have a kind of debug mode in butt with extra verbose logging or something...

edit: just installed 0.1.25 on my dev machine, still everything okay.

I saw in netstat -an that Teamviewer_Service.exe also does something with port 8000, so I changed icecast/butt to port 8001, but to no avail. I even stopped the TeamViewer service but that didn't work either.

[Paul Higgins]

Well, I thought the problem was solved by upgrading to 0.1.25, but that's not the case.

Here's some information that might be relevant. The PC on which butt and icecast is installed is located elsewhere on our campus. I'm using Remote Desktop to access the PC. When I log in and start both icecast and butt, things work fine. When I then disconnect from Remote Desktop, I get the socket timeout error and the audio stops. When I reconnect with Remote Desktop, I notice that the levels on the VU meter don't move. Exiting butt and starting it again fixes the problem (until I disconnect again).

[Fleskalebas]

Interesting. We use it on a machine with TeamViewer. This weekend I can check if it also happens when I use the PC normally.

[Daniel Nöthen]

That is interesting Paul,

I could imagine that the RDP fiddles around with the audio to forward it to the remote client or something. Could that be possible? And if yes, it would be good to disable any audio stuff related to the RDP access. I found this with a quick search on google. Maybe it helps:
https://smallbusiness.chron.com/disable-microsoft-rdp-audio-driver-49267.html

[Paul Higgins]

I had the same thought, Daniel. I just tried changing the RDP settings. With some of the settings, butt (upon starting) would give the message "ERROR: no sound device with input channels found". When I had the RDP audio settings set to "Play on remote computer", butt would start up correctly and pass the audio to Icecast. However, disconnecting would still cause the audio stream to timeout.

For now, I'm going to accept that using Remote Desktop can introduce this problem. I've got the PC set to automatically start butt and Icecast upon startup, so I'll just reboot the PC when I end my Remote Desktop session.

[Daniel Nöthen]

This is really annyoing. Did you consider using a VNC solution like https://www.tightvnc.com instead of RDP? This will not change any sound settings on the server.

[Fleskalebas]

To be sure, I just checked again directly on the console (without Teamviewer) but still the same issue. Socket closes after 10 seconds. Maybe you could provide a butt version with very verbose logging, so we hopefully can find the cause? :)

[Daniel Nöthen]

Hello, sorry at moment I am busy with other projects. I will release a new version until end of year with a more verbose logging capability :)

[Fleskalebas]

No problem, I have a working alternative but it's a big piece of software. I liked your lightweight program :) Enjoy the other projects!