Icecast Server/2.5 Maintenance

Icecast 2.5.x Maintenance

Overview

Icecast versions 2.5.x report a list of "Maintenance" items in the dashboard within the admin interface. Those messages are meant to provide help to keep a deployment in best shape.

List

Info

Info level messages are just there to aid e.g. in case of a problem. No active action is required.

Core files are disabled. / Core files are enabled.

This informs whether or not core files are enabled. Core files are a classic mean of debugging offered by some operating systems. Support may ask for this value.

IPv4-mapped IPv6 is available on this system.

The operation system supports legacy IP via current IP sockets. This means that only an IPv6 socket needs to be configured to also handle legacy IP.

This information may be hidden if Icecast seems to be configured correctly to avoid spamming the section.

chroot configured and active.

chroot was configured and is active. See your operation system's documentation on the details of chroot.

Change of UID/GID configured and active.

Changing of the user ID and/or group ID was configured and was successful.

Warning

Warnings should be considered thoroughly and the problems generally should be resolved in a timely manner. It is possible that the operation is affected by the problems reported with warnings.

Developer logging is active. This mode is not for production.

Icecast is build with developer logging active. This should never be seen in production. If seen without an Icecast developer asked for it it should be disabled. To disable this Icecast needs to be recompiled.

Hostname is not set to anything useful in <hostname>.

The hostname tag is not set correctly in the Icecast configuration. Some features such as directory support may be disabled. Playlist generation may not work correctly. There is generally more details in the error log. See https://icecast.org/faq/#faqentry-what-should-i-set-hostname-to for details.

No useful location is given in <location>.

The location tag is not set to anything useful in the configuration. See https://icecast.org/faq/#faqentry-what-should-i-set-location-to for details.

No useful location is given in <location>.

No useful location is given in the configuration. See https://icecast.org/faq/#faqentry-what-should-i-set-location-to for details.

No admin contact given in <admin>. YP directory support is disabled.

No valid admin contact details are given. Some features such as directory support may be disabled. See https://icecast.org/faq/#faqentry-what-should-i-set-admin-to for details.

Error

Errors record actual problems and should be taken care of as soon as possible.

Global client, and source limit is bigger than suitable for current open file limit.

Icecast is configured in a way allowing for more connections than the operating system permits. This may result in strange behaviour when the operating system's limit is reached.

Usually this is due to Icecast being set to some aggressively high client limit. However it can also be due to a low limit enforced by the operating system. In general the limit of the operating system must be higher than the one set by Icecast for Icecast to actually handle the number of clients.

IPv6 not enabled.

Icecast is configured with only legacy IP enabled. The current IP version (IPv6) needs to be enabled.

No PRNG seed configured. PRNG is insecure.

No configuration for the PRNG is given. The generator may return weak values. libigloo defaults are used. See libigloo's documentation for details.

Unknown tags are used in the config file. See the error.log for details.

Unknown tags are found in the configuration file. Those are invalid and future versions of Icecast may not load with them present. See the error log for details.

Unknown tags are often a result of typos.

Obsolete tags are used in the config file. See the error.log for details and update your configuration accordingly.

Obsolete tags are found in the configuration file. Those should be updated or removed accordingly. Future versions of Icecast may not load with them present. See the error log for details.

Invalid tags are used in the config file. See the error.log for details and update your configuration accordingly.

Invalid tags (for example tags with invalid values) are found in the configuration file. Those must be corrected. Future versions of Icecast may not load with them present. See the error log for details.

The configuration did not validate. See the error.log for details and update your configuration accordingly.

The configuration file is not valid. It may contain logical errors such as invalid combinations of values. Those must be corrected. Future versions of Icecast may not load with them present. See the error log for details.

chroot configured but failed.

chroot was configured but failed. This is a security problem and requires immediate handling. See the error log and your operation system's documentation for more details.

chroot configured but not supported by operating system.

chroot was configured but is not supported by the operating system. This is a security problem and requires immediate handling. See the error log and your operation system's documentation for more details.

Change of UID/GID configured but failed.

Changing of the user ID and/or group ID was configured but failed. This is a security problem and requires immediate handling. See the error log and your operation system's documentation for more details.

Change of UID/GID configured but not supported by operating system.

Changing of the user ID and/or group ID was configured but is not supported by the operating system. This is a security problem and requires immediate handling. See the error log and your operation system's documentation for more details.