Icecast-Server issueshttps://gitlab.xiph.org/xiph/icecast-server/-/issues2024-01-20T23:27:48Zhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/2485Fix CI, on the road to 2.52024-01-20T23:27:48ZGilouFix CI, on the road to 2.5Main issue to track the already on-going work with the CI, so that we can push our releases to OBS.
Work is happening on @stephan48 forks and mine, and especially from mine to his: https://gitlab.xiph.org/stephan48/icecast-server/-/merge...Main issue to track the already on-going work with the CI, so that we can push our releases to OBS.
Work is happening on @stephan48 forks and mine, and especially from mine to his: https://gitlab.xiph.org/stephan48/icecast-server/-/merge_requests/3 and draft on-going to the main repository https://gitlab.xiph.org/xiph/icecast-server/-/merge_requests/16https://gitlab.xiph.org/xiph/icecast-server/-/issues/2484iPhone creates duplicate connections2024-01-06T03:59:36ZAngelo HongensiPhone creates duplicate connectionsIt seems that whenever a client connects to a stream from an iphone, either directly to the icecast port http://x.x.x.x:8000/stream or through web players, the iphone creates to identical connections to the icecast server, and keeps both...It seems that whenever a client connects to a stream from an iphone, either directly to the icecast port http://x.x.x.x:8000/stream or through web players, the iphone creates to identical connections to the icecast server, and keeps both active.
While this is not that bad, it does count toward the maximum connection limit. I have no idea if this is an icecast issue (perhaps specific headers or packets are being sent forcing the client to set up an additional connection) or an iPhone/safari/webkit issue, nor do I have the expertise to troubleshoot this.
Can you guys replicate this behaviour? For now, I'm assuming it's a bug in ios 17, any idea how to report this to apple??
edit: I'm not the only one: https://github.com/doublesymmetry/react-native-track-player/issues/2096https://gitlab.xiph.org/xiph/icecast-server/-/issues/2483Under heavy concurrency, there is a large number of timeouts occurring in the...2024-01-12T08:59:51ZTom TomUnder heavy concurrency, there is a large number of timeouts occurring in the audio streams.We forward requests to the icecast2 service through nginx, and we are experiencing a high number of 502 errors when the concurrency is high. Could you please advise on how to address this issue? For the
relevant icecast2 configuration, s...We forward requests to the icecast2 service through nginx, and we are experiencing a high number of 502 errors when the concurrency is high. Could you please advise on how to address this issue? For the
relevant icecast2 configuration, server connection status, and process resource usage, please refer to the attached document.
![icecast2_配置](/uploads/f9a32fdf28695b8b9c9816c0450ed4c6/icecast2_配置.png)
![top](/uploads/6cd4eeb06064b44327e7cc4fdc721cb2/top.png)![连接状态](/uploads/0030fb8cb33c3a56c7a67227c4663a33/连接状态.png)https://gitlab.xiph.org/xiph/icecast-server/-/issues/2482List Clients - feature request2024-01-06T02:45:43ZdaenixList Clients - feature requestFeature requests:
It would be nice to have in List Clients table the possibility to sort by columns (IP, user agent) which now is only sorted by connection time.
Last but not least to redirect automatically (after a number of seconds) ...Feature requests:
It would be nice to have in List Clients table the possibility to sort by columns (IP, user agent) which now is only sorted by connection time.
Last but not least to redirect automatically (after a number of seconds) to List Clients when kicking some IPhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/2481reserved identifier violation2023-08-15T09:33:30ZMarkus Elfringreserved identifier violation:eyes: I would like to point out that identifiers like “[`__BUFFER_H__`](https://gitlab.xiph.org/xiph/icecast-server/-/blob/57093def7baacf2aaaff3a17915cd7fc0b8cfec3/src/buffer.h#L14 "Update candidate")” and “[`__CFGFILE_H__`](https://git...:eyes: I would like to point out that identifiers like “[`__BUFFER_H__`](https://gitlab.xiph.org/xiph/icecast-server/-/blob/57093def7baacf2aaaff3a17915cd7fc0b8cfec3/src/buffer.h#L14 "Update candidate")” and “[`__CFGFILE_H__`](https://gitlab.xiph.org/xiph/icecast-server/-/blob/57093def7baacf2aaaff3a17915cd7fc0b8cfec3/src/cfgfile.h#L15 "Another update candidate")” [do not fit](https://wiki.sei.cmu.edu/confluence/display/cplusplus/DCL51-CPP.+Do+not+declare+or+define+a+reserved+identifier#DCL51CPP.Donotdeclareordefineareservedidentifier-NoncompliantCodeExample%28HeaderGuard%29 "Do not declare an identifier which is reserved for the compiler implementation.") to the expected naming convention of the C++ language standard.
:thought_balloon: Would you like to adjust your selection for unique names?https://gitlab.xiph.org/xiph/icecast-server/-/issues/2480Test Ticket, please ignore2023-08-07T14:32:40ZPhilipp SchafftTest Ticket, please ignoreThis is a little funny test ticket. You know the lazy dog, don't you?This is a little funny test ticket. You know the lazy dog, don't you?Philipp SchafftPhilipp Schaffthttps://gitlab.xiph.org/xiph/icecast-server/-/issues/2479Revise supported architectures, operatingsystems and buildtargets2024-01-06T03:14:17ZStephan JauernickRevise supported architectures, operatingsystems and buildtargetsCheck and define what architectures, operatingsystems and buildtargets we want:
- amd64, i386, aarch64, s390x, ...?
- Debian 12(stable), Debian(11), Ubuntu ?!?!?!?!, RedHatDerivate>9000 ??!?!?!, ...?
- GCC 2.9, clang xxx, intel-who-knows...Check and define what architectures, operatingsystems and buildtargets we want:
- amd64, i386, aarch64, s390x, ...?
- Debian 12(stable), Debian(11), Ubuntu ?!?!?!?!, RedHatDerivate>9000 ??!?!?!, ...?
- GCC 2.9, clang xxx, intel-who-knows-what, ...?
- ....
Should optimally be done before Icecast 2.5 rc1https://gitlab.xiph.org/xiph/icecast-server/-/issues/2478Request: Make status-json.xslt a real JSON REST API endpoint (Github #65)2024-01-06T03:52:01Z/usr/local/ΕΨΗΕΛΩΝRequest: Make status-json.xslt a real JSON REST API endpoint (Github #65)# TL:DR;
Please make sure that icecast status-json.xslt returns a singleton array of `source` when there is a single source available, to allow consumers using an object-oriented model of icecast output for scraping.
----
As a programm...# TL:DR;
Please make sure that icecast status-json.xslt returns a singleton array of `source` when there is a single source available, to allow consumers using an object-oriented model of icecast output for scraping.
----
As a programmer, I enjoy integrating open systems that speak popular protocols.
I was working on a mobile front end for icecast2 and I found that icecast exposes a JSON API to parse the available streams. I worked with Angular to process it.
I found that the JSON is generated by an XSL transform, which produces an output that in the REST paradigm is not easy to work with.
In XML, especially if you have a schema defined, you can easily tell whether the `<source>` tag appears once or multiple times, and multiple tags appear at the same level. In JSON, the `source` must be either an object or an array for the client to parse it **easily**
The problem is, look at these outputs when you have a single stream running, or multiple:
```json
{
"icestats": {
"admin": "example@localhost",
"host": "localhost",
"location": "somewhere",
"server_id": "Icecast 2.4.4",
"server_start": "Tue, 06 Jun 2023 09:33:57 +0000",
"server_start_iso8601": "2023-06-06T09:33:57+0000",
"source": [
{
...
"listenurl": "http://localhost:8000/silent2.ogg",
"server_description": "Unspecified description",
"server_name": "The Silent Party",
...
},
{
...
"listenurl": "http://localhost:8000/stream",
"server_description": "Unspecified description",
....
}
]
}
}
```
```json
{
"icestats": {
"admin": "example@localhost",
"host": "localhost",
"location": "somewhere",
"server_id": "Icecast 2.4.4",
"server_start": "Tue, 06 Jun 2023 09:33:57 +0000",
"server_start_iso8601": "2023-06-06T09:33:57+0000",
"source": {
"audio_bitrate": 128000,
....
"listenurl": "http://localhost:8000/silent2.ogg",
"server_description": "Unspecified description",
"server_name": "The Silent Party",
....
}
}
}
```
As you can see, if there is a single stream, then the object is a map. Otherwise, it's an array.
Software working on JSON has to suffer additional burden (i.e. more code, more tests, less reliability) to handle the icecast output compared to the straight solution of using an array for the source_s_.
Here is my solution for an Angular app
```typescript
export interface IcecastStatsDto {
admin?: string;
client_connections?: number;
....
stats_connections?: number;
source?: IcecastSourceDto | IcecastSourceDto[];
}
```
And some typescript code to change the `IcecastSourceDto | IcecastSourceDto[]` into a (singleton?) array
```typescript
private getArrayFromSingleValue(x?: IcecastSourceDto | IcecastSourceDto[]): IcecastSourceDto[] {
if (!x) {
return <IcecastSourceDto[]>[];
} else if ('filter' in x) {
return <IcecastSourceDto[]>x;
} else if ('server_url' in x) {
return <IcecastSourceDto[]>[<IcecastSourceDto>x];
} else {
return <IcecastSourceDto[]>[];
}
}
```
This is for a Javascript FE. If I was using a C# or Java application, decoding icecast output into a POCO/POJO woulc be much harder. Defining a singleton array (i.e. an array containing one element) is the preferred solution in OO world,
I hope my feedback will be useful to improve the softwarehttps://gitlab.xiph.org/xiph/icecast-server/-/issues/2476Support for linking well known IDs from metadata2023-06-07T08:36:00ZPhilipp SchafftSupport for linking well known IDs from metadataIt would be nice if Icecast could auto link data when there is a well known ID for it. This is the case with e.g. MusicBrainz.
There should be a boolean setting that can be used to turn this off (e.g. for legal reasons).
This may also ...It would be nice if Icecast could auto link data when there is a well known ID for it. This is the case with e.g. MusicBrainz.
There should be a boolean setting that can be used to turn this off (e.g. for legal reasons).
This may also be implemented on top of #2475 by adding defaults to it.https://gitlab.xiph.org/xiph/icecast-server/-/issues/2475Content resolver support2023-06-07T09:04:02ZPhilipp SchafftContent resolver supportAs there is not yet been a content resolver set up for Icecast and/or the foundation I would like to suggest the following:
Icecast should be extended with a set of settings used to generate URLs for content resolver requests. Initially...As there is not yet been a content resolver set up for Icecast and/or the foundation I would like to suggest the following:
Icecast should be extended with a set of settings used to generate URLs for content resolver requests. Initially there should be support for generating links to documentation. Other types (such as fetches) might later be added.
The I suggest to allow a template style URLs as values with `%`-prefixed parameters to be substituted.
As a reference "`ise-uri-template`" (`82ebe8fa-8b04-415a-ba90-16267465ef71`) defines:
> A URI template for accessing a resolver. This should not be used directly but my using one of the relations derived from it. Such templates are meant to be attached to contexts to allow easy access to resolvers without the need to set direct URIs on every tag.
>
> Templates are used as is with the following variables replaced by correctly URI encoded values. If a given value is not available this template is not available.
>
> * "%I": Any ISE of the tag
> * "%U": The UUID of the tag
> * "%O": The OID of the tag
> * "%R": The URI of the tag
>
> The use of those values is mostly safe as "%" is a special character in URIs that can only be followed by digits, or the letters "a" to "f". However some applications generate invalidly encoded Unicode URIs containing values in the form of "%uNNNN". Those are invalid by themself and therefore not valid in such templates.
I would like to extend that by providing three more substitutions:
* A generic one for the identifier (in any type/encoding)
* The name of the type/encoding used
* The name of the type/encoding used but the value `ise` for any ISE type (UUID, OID, URI).
If such parameters are added a note should be added to the code to make clear that they do not follow the `ise-uri-template` rules. However they may be added or at least reserved for `ise-uri-template` to avoid future syntax collisions.https://gitlab.xiph.org/xiph/icecast-server/-/issues/2472Locking issue with logging2024-01-14T14:15:37ZPhilipp SchafftLocking issue with loggingCurrently the signal handlers as well as the event subsystem's exec backend logs messages. Those seem to be subject to restrictions on the logging code's locking. This can result in the process hanging. It is unclear whether or not this ...Currently the signal handlers as well as the event subsystem's exec backend logs messages. Those seem to be subject to restrictions on the logging code's locking. This can result in the process hanging. It is unclear whether or not this may also corrupt the process in any way.
See also (likely unrelated): #2231https://gitlab.xiph.org/xiph/icecast-server/-/issues/2471listener_remove 2.5 beta not appear if listener creates two connection at the...2023-05-12T10:21:13ZHans-Georg Althofflistener_remove 2.5 beta not appear if listener creates two connection at the same timeI am using kh 2.4.0 kh20 and I am sure that this 64-bit build is based on 2.5 beta.
If a listener creates two connections at the same time, icecast creates two different client ids, which is absolut correct.
If the first of the two conne...I am using kh 2.4.0 kh20 and I am sure that this 64-bit build is based on 2.5 beta.
If a listener creates two connections at the same time, icecast creates two different client ids, which is absolut correct.
If the first of the two connection is closed, icecast is sending a `listener_remove` POST request. That is alright.
But if the second connection is also closed, no additional `listener_remove` POST request is send!
That should no be the case!
My MySQL database for this client id is therefore not closed and appear still at an active connection.
With the ols 2.4.4 32-bit version it works fine.https://gitlab.xiph.org/xiph/icecast-server/-/issues/2470Missing documentation for version 'latest'2023-04-06T12:15:53ZJonas L.Missing documentation for version 'latest'Documentation for some versions is missing on the website https://icecast.org/docs/:
- https://icecast.org/docs/icecast-latest
- https://icecast.org/docs/icecast-2.4.4Documentation for some versions is missing on the website https://icecast.org/docs/:
- https://icecast.org/docs/icecast-latest
- https://icecast.org/docs/icecast-2.4.4Marvin ScholzMarvin Scholzhttps://gitlab.xiph.org/xiph/icecast-server/-/issues/2469HLS (HTTP Live Streaming) should be supported2023-11-28T18:36:05ZBjoern JackeHLS (HTTP Live Streaming) should be supportedplain http audio streams as Icecast supportes them currently have two major drawbacks for clients:
1) network connectivity changes lead to audio stream losses, clients will have to reconnect, audio will be interrupted
2) network modems...plain http audio streams as Icecast supportes them currently have two major drawbacks for clients:
1) network connectivity changes lead to audio stream losses, clients will have to reconnect, audio will be interrupted
2) network modems have to be busy continously because the plain audio stream is being sent all the time. The permanent activity of the modem is not energy efficient at all. Mobile devices suffer from noticable battery drain.
The solution to the above mentioned problems is HLS (https://en.wikipedia.org/wiki/HTTP_Live_Streaming). The Rocket Streaming Audio Server from https://rocketbroadcaster.com/streaming-audio-server/ does support HLS for example.
With HLS audio streams modems of client devices can stay idle most of the time, as a result of that you see greatly enhanced battery live - and network switching and even short network outages will not be a problem for clients any more.
It would be awesome if Icecast would add support for HLS, too, to overcome the shortcomings of plain audio streams, which especially mobile users suffer from considerably.https://gitlab.xiph.org/xiph/icecast-server/-/issues/2468lost TCP connections of relays are not handled gracefully2023-04-06T22:19:52ZBjoern Jackelost TCP connections of relays are not handled gracefullyI'm running icecast with a mointpoint that has both a IPv4 and a IPv6 address. IPv4 and IPv6 traffic go over different providers, so this is also being done for redundancy reasons.
I tested how well icecast handles the fallback from the...I'm running icecast with a mointpoint that has both a IPv4 and a IPv6 address. IPv4 and IPv6 traffic go over different providers, so this is also being done for redundancy reasons.
I tested how well icecast handles the fallback from the IPv4 path to the IPv6 path or vice versa by killing the TCP connection or changing the route to "unreachable". It turns out that icecast connects to the other IPv4 or IPv6 path but connected clients will lose their connection immediately, which is bad. Of course we don't want to lose all our users and hope for them to reconnect to our stream in case of such a fallback in our upstream mount.
I tested exactly the same szenario with https://rocketbroadcaster.com/streaming-audio-server - and the Rocket Streaming Audio Server *does* handle this gracefully. The only thing that I was able to notice from the client side here was an ffmped audio decoding error message when the RSAS switched from the one path to the other path. But the switch was almost not noticable by clients.
It would be great if icecast would handle such a case as gracefully as the Rocket Streaming Audio Server.https://gitlab.xiph.org/xiph/icecast-server/-/issues/2467icecast2 crashes frequently2024-01-21T02:16:54ZTom Tomicecast2 crashes frequentlyWe found that icecast2.4.4 often crashes(It has crashed more than a dozen times in the last three days). By checking the system logs, and found that the reasons for the crash are as follows:
```
Apr 4 21:48:56 ubuntu-s-1vcpu-2gb-intel...We found that icecast2.4.4 often crashes(It has crashed more than a dozen times in the last three days). By checking the system logs, and found that the reasons for the crash are as follows:
```
Apr 4 21:48:56 ubuntu-s-1vcpu-2gb-intel-lon1-01 kernel: [46118.223163] icecast2[2005787]: segfault at 4f28 ip 00007f64546dd064 sp 00007fff1d087480 error 4 in libwolfssl.so.24.0.0[7f6454649000+d0000]
Apr 4 21:48:56 ubuntu-s-1vcpu-2gb-intel-lon1-01 kernel: [46118.223177] Code: 84 00 00 00 00 00 f3 0f 1e fa 41 54 55 48 89 fd 48 81 ec a8 00 00 00 64 48 8b 04 25 28 00 00 00 48 89 84 24 98 00 00 00 31 c0 <0f> b6 87 28 4f 00 00 83 e0 c0 3c 40 74 2e 31 f6 48 89 ef e8 74 75**
Apr 4 21:49:02 ubuntu-s-1vcpu-2gb-intel-lon1-01 systemd[1]: Stopping LSB: Icecast2 streaming media server...
Apr 4 21:49:02 ubuntu-s-1vcpu-2gb-intel-lon1-01 icecast2[2008732]: * Stopping streaming media server icecast2
Apr 4 21:49:02 ubuntu-s-1vcpu-2gb-intel-lon1-01 icecast2[2008732]: ...done.
Apr 4 21:49:02 ubuntu-s-1vcpu-2gb-intel-lon1-01 systemd[1]: icecast2.service: Succeeded.
Apr 4 21:49:02 ubuntu-s-1vcpu-2gb-intel-lon1-01 systemd[1]: Stopped LSB: Icecast2 streaming media server.
```
The operating system we use is: Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-146-generic x86_64)https://gitlab.xiph.org/xiph/icecast-server/-/issues/2465Add support for RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token...2023-03-18T10:25:42ZPhilipp SchafftAdd support for RFC 6750: The OAuth 2.0 Authorization Framework: Bearer Token UsageSupport for RFC 6750 should be added. In a first iteration this only needs to be supported by the `url` and the `enforce-auth` backend.
See also: xiph/icecast-libshout#2311Support for RFC 6750 should be added. In a first iteration this only needs to be supported by the `url` and the `enforce-auth` backend.
See also: xiph/icecast-libshout#2311Philipp SchafftPhilipp Schaffthttps://gitlab.xiph.org/xiph/icecast-server/-/issues/2462Track's end is repeated2023-11-18T23:34:29ZDan SanfordTrack's end is repeatedI have
- opus files
- ices2 2.0.3-1
- icecast2 2.4.4-4
- on debian
The problem is that it repeats end of tracks a 2nd time. (happens many times, even on fresh boot, but not always)
The repeat length looks close to buffer size, so that'...I have
- opus files
- ices2 2.0.3-1
- icecast2 2.4.4-4
- on debian
The problem is that it repeats end of tracks a 2nd time. (happens many times, even on fresh boot, but not always)
The repeat length looks close to buffer size, so that's why I think it's in icecast2.
I have downloaded the played opus file, and its end is played correctly offline. So that rules out my files.
I have never noticed this repeat on official radio streams with my player. So that rules out my player.
I have noticed it on 2 separate client PCs, so that points to the server.
I've tuned my /etc/icecast2/icecast.xml so there are no dropouts:
```
<limits>
<clients>100</clients>
<sources>20</sources>
<queue-size>1048576</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<burst-on-connect>1</burst-on-connect>
<burst-size>262140</burst-size>
</limits>
```
ices2 doesn't have a forum to ask the same question.https://gitlab.xiph.org/xiph/icecast-server/-/issues/2461Converting URL auth to use string renderer.2023-02-27T11:48:36ZPhilipp SchafftConverting URL auth to use string renderer.Currently the URL auth backend builds it's POST data itself. This should be migrated to use string renderer. The code from URL events can be used as a template.Currently the URL auth backend builds it's POST data itself. This should be migrated to use string renderer. The code from URL events can be used as a template.Philipp SchafftPhilipp Schaffthttps://gitlab.xiph.org/xiph/icecast-server/-/issues/2459Missing documentation for the stats method2023-01-28T20:46:12ZJonas L.Missing documentation for the stats methodHi,
I am unsure if the custom stats method (`curl -X STATS http://icecast:8000`) is deprecated/maintained and if I should use it?
If this can be used in new project, I am looking for some documentation about it. Is there a place where t...Hi,
I am unsure if the custom stats method (`curl -X STATS http://icecast:8000`) is deprecated/maintained and if I should use it?
If this can be used in new project, I am looking for some documentation about it. Is there a place where this already exists?
Thanks