similar to: ices question

I get a segmentation fault when starting the IceS encoder on a Linux-based QNAP NAS. I'm trying to set up IceS to stream an ALSA input to Icecast. Icecast works well and confirms when I stream using other things to it. However IceS hits a segmentation fault immediately after starting the encoder. The IceS log is: [~] # sudo ices /etc/ices.xml [2020-05-11 19:24:34] INFO ices-core/main IceS

Hello, I'd like to be able to run multiple instances of Ices (2.0), each with their own playlist and streaming to different mountpoints. Although I'm relatively new to Ices and Icecast, so far I have had little trouble getting it running with two or more instances of Ices feeding off fixed playlists (files). I'd like to be able to set each instance of Ices to run with script based

Ok, so i have to know the PID of ices to send the update-signal. I've added this to my ices.xml: <pidfile>/home/www/bin/ices.pid</pidfile> (directly under the node <ices>) I thought i've seen this somewhere in the manual. However, when i start ices, no pid-file is created :-/ Is this the right way? <p>----- Original Message ----- From: "Karl Heyes"

I am having problems getting Ices to work with ALSA. If I use arecord (arecord -D plughw:0,0 output.wav) I can record the input from my microphone into a file. The playback works perfectly. However, if I use Ices with the same values I hear nothing on the receiving end of my broadcast (although I can connect to it). In order to do a further test, I setup a <savefile> tag in my

Karl, I installed icecast/ices from the latest stable ebuild on gentoo portage. It appears from the log file that ices is only version 2.0.0 even though the ebuild is version 2.1.0. I just reinstalled icecast with the newest (unstable) ebuild and it still doesn't seem to have version 2.0.1 of ices. Do you recommend that I manually compile or that I find a way to use a wrapper for ALSA to

Hi, I'm currently migrating from Shoutcast/MP3 to Icecast/OGG/Vorbis using ices. Unfortunately, when initialising the encoder, ices crashes with a bus error. Is there anything I can look into? Details as follows: icecast2-2.1.0,1 ices-2.0.0,1 libshout2-2.0_5,1 libogg-1.1.2_1,3 libvorbis-1.1.0_1,3 (All were installed from the ports tree) On FreeBSD ares.radiozilvervos.com 5.3-RELEASE-p4

I have icecast 2.0.0 and ices 2.0.0 working nicely together with no apparent errors. I connect to the URL with winamp and it works get. Problems arise when I try to connect with any other computer other than my own. This includes other computers on my LAN and off it aswell. In the winamp window they get the message: [HTTP/1.0 200OK] http://www.feelthevibe . . . Any suggestions as to why my

Hello all I am sending my icecast configuration. What i am trying to do is 'live stream' so as to be able to broadcast radio live on my website. I am using icecast as the server and ices as the streamer. Below is the configuration for icecast and following it is my configuration for ices. I cannot seem to find out where i went wrong. <icecast> <limits>

Hi, we started using centos7 to run kvm+libvirt. For novnc to virtual machines I like to start websockify as a daemon by libvirt (as a hook) Under Debian I used the line: # start-stop-daemon --start --chuid $RUNUSER --make-pidfile --pidfile $PIDFILE --startas $PROGRAM -- $OPTIONS which creates a nice pidfile. In Centos I figured out, to include /etc/init.d/functions and I tried: # daemon

Hi there, I just joined the list and have a question on one of the earlier posts: On Oct 28 2003, Ricardo wrote that his server diconnected his clients. I have the exact same problem - and a bit of testing/analysis. <p>I am running an Icecast server and IceS on the same linux box. IceS is encoding a live stream from my sound card. After a while of listening (approx 2 mins) from another

skotthof wrote: > > OK, I figured out, I have to install > redhat-lsb package for start-stop-daemon > "Implementation of Linux Standard Base specification" > > Sebastian > On Tue, Jun 02, 2015 at 11:06:59AM +0200, skotthof wrote: >> Hi, >> >> we started using centos7 to run kvm+libvirt. >> For novnc to virtual machines I like to start >>

I posted the other day with a question about a player that mysteriously quits playing the icecast stream. I believe the problem is related to the icecast stream for two reasons. 1) Because it quits on more than one different player (Winamp 5 and Foobar2000) and 2) Because I used to use shoutcast with Winamp 2 and never had this problem. Anyway, I tried to get as much information about the problem

Test that we can script the read of a specific pattern from nbdkit. Also, test that we can concatenate global functions through consecutive -c. This test fails if commit d6cbd130 is reverted. --- sh/Makefile.am | 5 ++++- sh/test-dump.sh | 45 +++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 49 insertions(+), 1 deletion(-) create mode 100755 sh/test-dump.sh diff --git

Well I’ve looked through the configuration file several times and I still do not see the mistake I’ve made. Icecast 2.0.1 seems to be working just fine and starts up without problems. But if I try and start ices I keep getting the error that it cannot connect to 127.0.0.1:8000 because the login failed. Yet I know the password I gave it is correct so I can only presume there is a configuration

Package: xen-utils-common Version: 4.4.0-1 Severity: important Tags: patch Under some circumstances the xl toolstack needs to create a loopback mount of a guest disk in dom0 (e.g. in order to run pygrub). Depending on the nature of the guest disk (e.g. qcow2 or raw file image based) this can require a qemu instance in dom0. The upstream xencommons starts such a qemu on boot. The following patch

On 21.11.2014 13:50, Ian Campbell wrote: > Package: xen-utils-common > Version: 4.4.0-1 > Severity: important > Tags: patch > > Under some circumstances the xl toolstack needs to create a loopback > mount of a guest disk in dom0 (e.g. in order to run pygrub). Depending > on the nature of the guest disk (e.g. qcow2 or raw file image based) > this can require a qemu

On 9/13/18 11:09 AM, Richard W.M. Jones wrote: > This assumes bashisms, but bash is required to run the tests. > > This is mostly refactoring. However the changes (simplifications) are > quite substantial: > > - Since the new start_nbdkit helper function cleans up nbdkit on > exit, most scripts no longer need to deal with the pid or kill the > pid in the

Hi! I run a mongrel cluster with 6 mongrels in it. I want to monitor them individually for process hangs (and then restart them) and this is the solution I came up with: Here''s my configuration file for monit (/usr/local/etc/monitrc): [snipped relevant bits] ------ #check lighttpd process check process lighttpd with pidfile /var/run/lighttpd.pid start program =