AzuraCast / AzuraCast

A self-hosted web radio management suite, including turnkey installer tools for the full radio software stack and a modern, easy-to-use web app to manage your stations.
https://www.azuracast.com/
GNU Affero General Public License v3.0
3.02k stars 562 forks source link

Some stations are not counting listeners on profile page #4341

Closed lramilo closed 2 years ago

lramilo commented 3 years ago

Using Docker installation method? Yes

AzuraCast version: 0.12.2 stable

Host Operating System: Ubuntu 18.x

Describe the bug: Some stations are not showing the listener count on profile page.

Steps to reproduce: I have multiple customer's stations from my hosting service running on AzuraCast as beta testers.

I managed to add external relays to handle listeners as I plan to offer this service for customers with high audience levels. These relays are Icecast 2.4.0-kh15 in order to have better compatibility with AzuraCast, specifically with audience monitoring.

Once I added all the relays, using API, I was able to see the correct audience levels. But after a while, I could not get the number on many of the station's profile pages; but could get the number on the listeners page.

I've restarted the stations, and also deleted the external relays, but nothing changed.

I don't know if there's something I cloud search in order to find the problem.

Help will be appreciated !

Additional info:

This is an example of one of the stations with the problem: It shows 0 listeners even when there are 3 connections (2 on AzuraCast's Icecast instances and 1 on an external Icecast relay)

image

image

This is how the external relays looks like:

image

This is the same station without the external relays, same behavior:

image

This is an example of one of the stations that work well: This is showing 24 listeners, that's correct as it could be seen on the details.

image

image

lramilo commented 3 years ago

The same problem is reflected on dashboard page.

image

Vaalyn commented 3 years ago

You might want to try updating to 0.13.0 since there have been some updates for listener data handling and relays. It could have been fixed already.

lramilo commented 3 years ago

Thank you @Vaalyn I've updated to 0.13.0 but the problem persists.

lramilo commented 3 years ago

On the other hand, some stations on the same server are counting listeners many times, as follows:

image

Vaalyn commented 3 years ago

Could you manually run the Now Playing Sync via the admin page and look for the 3 lines (and any errors directly related to them) for the remote relays that are not showing listeners?

The lines should begin like this:

AzuraCast.DEBUG: Sending GET request to http://stations:8000/admin/stats ...
AzuraCast.DEBUG: HTTP client GET call to http://stations:8000/admin/stats produced response 200 ...
AzuraCast.DEBUG: Raw body from response.  ...

Somewhere the data gets lost but we'll need to figure out where. These logs should help seeing if the response from the relays statistics page is correctly returning the data to AzuraCast.

lramilo commented 3 years ago

@Vaalyn I share a Google Docs with this info:

Station 8000 (works OK) screenshot Station 8020 (shows 0 listeners) screenshot Station 8030 (duplicates listeners) screenshot

And the complete log obtained after running the task

You could access the file using this link:

Google Docs: Azuracast/Some stations are not counting listeners on profile page #4341

I'm doing further testing and checking these logs too. Notice that I remove my external relays (as explained above on this same issue) I get the same result.

Please let me know if you need more details.

Thank you very much for your time !

Regards,

Vaalyn commented 3 years ago

I think the logs in your shared doc are incomplete.

Can you upload upload the complete logs as a .txt here?

lramilo commented 3 years ago

Sure @Vaalyn !

Please find complete logs.txt attached here. Also, I suspect having non-public streams could be affecting as this start happening once I changed this. I will try and back here with my results.

Again, thank you for your time.

Regards,

stale[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 2 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

github-actions[bot] commented 2 years ago

Thank you for your bug report, this issue has been closed due to inactivity. Should this issue persist, please re-open the bug report.