[Icecast] Auto rotation on day/hour or dump possible?

Philipp Schafft phschafft at de.loewenfelsen.net
Wed Jun 28 09:01:39 UTC 2023


Good Morning,

On Wed, 2023-06-28 at 09:19 +0200, Michel van Dop wrote:
> Hi Philipp,
> 
> Okay that's also a nice solution rename the log file and reload
> icecast. Only it may be that the file size has been reached, turning
> off archive then is this option is the best way! Thanks

yes. It's a good idea no to use two rotation methods at the same time.
;)

> The wrapper works well so far. And also retaining the original log
> files.

Perfekt.


> I check the the Linux machine for the ssl problem for 2.4.4 and 2.5
> beta. It is Debian GNU/Linux 10 (buster) OpenSSL 1.1.1n  15 Mar 2022

1.1.1n seems to work file for me at least.


> 
> I'm looking forward to the final release. Glad you are doing that and
> developing it.

"final". I hope we'll have many more releases over the next hrair
years.

Hope we also find some common project at some point. Or maybe we'll
meet at the next presentation? (Next is 2023-09-22 on HTML5 and CSS3.
Everyone on this list invited as always :)

With best regards,


> > Op 27-06-2023 10:55 CEST schreef Philipp Schafft <
> > phschafft at de.loewenfelsen.net>:
> > 
> >  
> > Good morning,
> > 
> > On Tue, 2023-06-27 at 09:34 +0200, Michel van Dop wrote:
> > > Hi Philipp,
> > > 
> > > Thank you, thats good news that the log on date rotation is in
> > > the
> > > new version 2.5.
> > 
> > keep in mind that the ticket you linked is about dumpfile rotation.
> > log
> > file rotation is the same as it always has been.
> > 
> > As this is a very common thing being asked if I may just include:
> >    When you want to rotate Icecast's logs for any reason at any
> > time
> >    you can just move rename them (also moving to a different same-
> >    volume directory). After that you need to send SIGHUP to
> > Icecast.
> >    This will ask Icecast to reload the config which also includes
> >    releasing the logfiles. When you do that, the logfile is closed
> > and
> >    reopened. Once Icecast has started the new file the old is all
> > yours
> >    and you can do with it what you want.
> > 
> >    Two notes here: a) this follows the standard way of UNIX
> > daemons, b)
> >    reloading might take a tiny bit of time as it happens async
> > within
> >    the server (which also fallows a). This doesn't matter for most
> >    applications. However if you need to do operations that are only
> >    valid once Icecast has completely released you should wait for
> > the
> >    new file to appear (normally within 3 seconds).
> > 
> > 
> > > And can you indicate what you are waiting for before making it
> > > the
> > > stable 2.5 release?
> > 
> > Currently the main items are optimisation in the build system for
> > the
> > official binaries as well as some politics (as you always have with
> > bigger projects).
> > 
> > (Actually those build system sharp corners we work on are what also
> > delays the next release we hoped to do this month.)
> > 
> > 
> > Generally I would suggest that nobody starts building something new
> > on
> > 2.4.x. However if you're still on 2.4.x it's fine to not yet
> > upgrade.
> > 
> > 
> > > And in which version of openssl does this problem no longer
> > > occur?
> > 
> > I'm not fully sure. We never found out. As TLS related software
> > needs
> > to be up to date anyway I would guess that any version that is
> > still
> > considered safe is also working.
> > 
> > 
> > > Sorry for straying from the original question :-)
> > 
> > Then go ahead and open another thread and everyone is fine with it.
> > ;)
> > 
> > 
> > With best regards,
> > 
> > 
> > > > Op 26-06-2023 17:11 CEST schreef Philipp Schafft <
> > > > phschafft at de.loewenfelsen.net>:
> > > > 
> > > >  
> > > > Good morning,
> > > > 
> > > > On Mon, 2023-06-26 at 16:29 +0200, Michel van Dop wrote:
> > > > > Hello,
> > > > > 
> > > > > I use/test now a log wrapper. 
> > > > > He checks which log has already been sent. In this way it
> > > > > only
> > > > > sends
> > > > > the new data it is fast and almost realtime.
> > > > > 
> > > > > This was the link that not work about log rotation in old
> > > > > mailing
> > > > > i
> > > > > found:
> > > > > https://trac.xiph.org/ticket/2173
> > > > 
> > > > This is most likely: 
> > > > https://gitlab.xiph.org/xiph/icecast-server/-/issues/2173
> > > > 
> > > > (It has been implemented and is part of the next release.)
> > > > 
> > > > 
> > > > > Thanks for the infomration about the KH version. I use it in
> > > > > the
> > > > > past
> > > > > for flash/aac.
> > > > > 
> > > > > I test 2.5 version and have a very nice interface. 
> > > > > It did crash once and also had some problems with https (stop
> > > > > after 3
> > > > > seconds after some weeks running fine) 
> > > > > using fallover mountpoints) Same as 2.4.4. 
> > > > > Caused a lot by using fallover mountpoints. Without fallover,
> > > > > the
> > > > > https stuttering problem does not arise.
> > > > 
> > > > I think those are not really related to this thread. Please
> > > > feel
> > > > free
> > > > to to open tickets for them.
> > > > 
> > > > Also the 3 seconds with TLS sound very much like the one bug
> > > > that
> > > > was
> > > > in OpenSSL at some point. Newer versions of OpenSSL have that
> > > > fixed, so
> > > > please check if it's still happening before filing a report. :)


-- 
Philipp Schafft (CEO/Geschäftsführer)
Telephone:           +49.3535 490 17 92
Website:             https://www.loewenfelsen.net/
Follow us:           https://www.linkedin.com/company/loewenfelsen/
Geschäftsführer/CEO: Philipp Schafft

Löwenfelsen UG (haftungsbeschränkt)     Registration number:
Bickinger Straße 21                     HRB 12308 CB
04916 Herzberg (Elster)                 VATIN/USt-ID:
Germany                                 DE305133015




More information about the Icecast mailing list