From phschafft at de.loewenfelsen.net  Wed Jul  6 08:48:59 2022
From: phschafft at de.loewenfelsen.net (Philipp Schafft)
Date: Wed, 06 Jul 2022 08:48:59 +0000
Subject: [Icecast] Next presentations and summer break
Message-ID: <9c5d92129d5a8654049068dcbc0b557e1c42a88b.camel@de.loewenfelsen.net>

Good morning to everyone,

this Friday we'll have the last of our regular presentations over at
L?wenfelsen before our summer break. This time a special off-topic one
"Big cats among us". All about big cats. :)

Starting at 15:00 UTC. If anyone is interested please just write me
off-list. Also bring your family. :)


After that the next regular one that is fixed already will be
"Icecast overview" on 2022-09-09. Which is our first repeated one.


Personally I was wondering if there is interest in me filling the gap
with one about why sampling of (audio) signals is actually lossless. So
if there is interest in that as well, just ping me. If there is
interest in that or any other topic we surely can make it happen.


Looking forward to your feedback!

With best regards,

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

L?wenfelsen UG (haftungsbeschr?nkt)     Registration number:
Bickinger Stra?e 21                     HRB 12308 CB
04916 Herzberg (Elster)                 VATIN/USt-ID:
Germany                                 DE305133015
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20220706/7c7bd548/attachment.sig>

From that.jack.elliott at gmail.com  Fri Jul  8 22:51:26 2022
From: that.jack.elliott at gmail.com (Jack Elliott)
Date: Fri, 8 Jul 2022 15:51:26 -0700
Subject: [Icecast] <on-connect><on-disconnect> send email example?
Message-ID: <6e5ad403-840e-a2b7-5b14-540a00808abe@kpov.org>

Hi, running Icecast 2.40 here. Can someone point me to an example of a 
script that will send an email when a source-client connects, and when 
it disconnects? I'd like to include the name of the mountpoint in the 
email subject or body.

Thank you!

-- 
Jack Elliott
Director of Classical Music Programming
KPOV 88.9 FM
High Desert Community Radio
Bend, OR



From jordan at subj.am  Sun Jul 10 04:05:58 2022
From: jordan at subj.am (Jordan Erickson)
Date: Sat, 9 Jul 2022 21:05:58 -0700
Subject: [Icecast] <on-connect><on-disconnect> send email example?
In-Reply-To: <6e5ad403-840e-a2b7-5b14-540a00808abe@kpov.org>
References: <6e5ad403-840e-a2b7-5b14-540a00808abe@kpov.org>
Message-ID: <b1361f23-2477-8308-6180-95e7109ea6b0@subj.am>

Hey Jack,

I had this lying around from a long time ago, I think it should still 
work, just needs some tweaking (namely the email address).

---------------------
#!/bin/bash
#
# Actions to perform when a source connects to us
#
# Email contacts that want immediate notification
 ?? printf %b "\
Source connection established at $1
" > $EMAILMESSAGE
 ?? /usr/bin/mail -s "Source connection established" 
"myemail at mydomain.net" < $EMAILMESSAGE

exit 0
---------------------


Cheers,
Jordan


On 7/8/22 15:51, Jack Elliott wrote:
> Hi, running Icecast 2.40 here. Can someone point me to an example of a 
> script that will send an email when a source-client connects, and when 
> it disconnects? I'd like to include the name of the mountpoint in the 
> email subject or body.
>
> Thank you!
>


-- 
Jordan Erickson
SubJam, SPC - https://subj.am/
+1 360.603.5039



From mph at emotrics.com  Thu Jul 14 00:53:02 2022
From: mph at emotrics.com (Milton Huang)
Date: Wed, 13 Jul 2022 17:53:02 -0700
Subject: [Icecast] notifying relays
Message-ID: <CAKSXWJ7sihmxQ7PJ9iZATZtupv32JGAr1yer+QMPBEPZ8Z6vow@mail.gmail.com>

I have a setup with an Icecast master server playing a continuous stream to
a Relay on an AWS instance, which in turn provides an SSL stream to the
world using the latest Icecast version 2.4.99.3. On occasion, we will start
a second stream for testing purposes. What I'm finding is there is a long
delay before the stream shows up, which I assume is related to the default
master-update-interval.  What I'm wondering is whether there is a way to
notify the Icecast relay that I'm starting a new stream, as it seems
wasteful to decrease the master-update-interval for something that only is
used on occasion.  I really don't need the relay to be constantly polling
besides making sure our main stream hasn't failed, as we only usually have
the one stream.

-milton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20220713/3c8f4eda/attachment.htm>

From phschafft at de.loewenfelsen.net  Thu Jul 14 09:25:52 2022
From: phschafft at de.loewenfelsen.net (Philipp Schafft)
Date: Thu, 14 Jul 2022 09:25:52 +0000
Subject: [Icecast] notifying relays
In-Reply-To: <CAKSXWJ7sihmxQ7PJ9iZATZtupv32JGAr1yer+QMPBEPZ8Z6vow@mail.gmail.com>
References: <CAKSXWJ7sihmxQ7PJ9iZATZtupv32JGAr1yer+QMPBEPZ8Z6vow@mail.gmail.com>
Message-ID: <a30faeceded60c20065e1681099c3fadd4cf377b.camel@de.loewenfelsen.net>

Good morning,

On Wed, 2022-07-13 at 17:53 -0700, Milton Huang wrote:
> I have a setup with an Icecast master server playing a continuous
> stream to a Relay on an AWS instance, which in turn provides an SSL
> stream to the world using the latest Icecast version 2.4.99.3. On
> occasion, we will start a second stream for testing purposes. What
> I'm finding is there is a long delay before the stream shows up,
> which I assume is related to the default master-update-interval. 
> What I'm wondering is whether there is a way to notify the Icecast
> relay that I'm starting a new stream, as it seems wasteful to
> decrease the master-update-interval for something that only is used
> on occasion.  I really don't need the relay to be constantly polling
> besides making sure our main stream hasn't failed, as we only usually
> have the one stream.

If the second stream has a constant name you could just use an on-
demand relay. That will check the master only when there is a client
actually trying to access it.

Hope that helps. :)

With best regards,

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

L?wenfelsen UG (haftungsbeschr?nkt)     Registration number:
Bickinger Stra?e 21                     HRB 12308 CB
04916 Herzberg (Elster)                 VATIN/USt-ID:
Germany                                 DE305133015
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20220714/16666a0b/attachment.sig>

From that.jack.elliott at gmail.com  Thu Jul 14 15:16:03 2022
From: that.jack.elliott at gmail.com (Jack Elliott)
Date: Thu, 14 Jul 2022 08:16:03 -0700
Subject: [Icecast] <on-connect> / <on-disconnect> not working
Message-ID: <0ed1e99b-e780-e4a4-c206-5e03543ba496@kpov.org>

Hi,

Icecast server 2.4.0 running on Linux.

I have a couple of shell scripts that send emails on connect and on 
disconnect. From the command line they work, but when called from 
icecast they do not.

Here is the mount section of my icecast.xml:

<mount type="normal">
 ??????? <mount-name>/my_stream</mount-name>
<fallback-mount>/fallbacks/my_fallback.mp3</fallback-mount>
 ??????? <fallback-override>1</fallback-override>
 ??????? <fallback-when-full>1</fallback-when-full>
*<on-connect>/home/my_username/bin/email_onconnect.sh</on-connect>**
**<on-disconnect>/home/my_username/bin/email_ondisconnect.sh</on-disconnect>*
 ??????? <no-yp>1</no-yp>
 ??? </mount>

After putting the new <on-connect> and <on-disconnect> entries into 
icecast.xml I reloaded the config with /etc/init.d/icecast2 reload and 
there was no error written to /var/log/icecast2/error.log

<on-connect> calls /home/my_username/bin/email_onconnect.sh which works 
from the command line. Likewise, <on-disconnect> calls a similar script 
which also works from the command line. I've tested them.

The permissions for the two scripts:

-rwxr-xr-x 1 my_username my_username 352 Jul 14 07:49 email_onconnect.sh
-rwxr-xr-x 1 my_username my_username 375 Jul 14 07:49 email_ondisconnect.sh

I'd like to get these functions working . . . ideas?

Thank you!

-- 
Jack Elliott
Director of Classical Music Programming
KPOV 88.9 FM
High Desert Community Radio
Bend, OR
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20220714/62b28a43/attachment.htm>

From petr.pisar at atlas.cz  Thu Jul 14 16:18:54 2022
From: petr.pisar at atlas.cz (Petr Pisar)
Date: Thu, 14 Jul 2022 18:18:54 +0200
Subject: [Icecast] <on-connect> / <on-disconnect> not working
In-Reply-To: <0ed1e99b-e780-e4a4-c206-5e03543ba496@kpov.org>
References: <0ed1e99b-e780-e4a4-c206-5e03543ba496@kpov.org>
Message-ID: <YtBB7lLtmrfqrhCM@album.bayer.uni.cx>

V?Thu, Jul 14, 2022 at 08:16:03AM -0700,?Jack Elliott napsal(a):
> Hi,
> 
> Icecast server 2.4.0 running on Linux.
>
Could you try upgrading Icecast? The latest version is 2.4.4 and there were
some fixes in between.

> I have a couple of shell scripts that send emails on connect and on 
> disconnect. From the command line they work, but when called from 
> icecast they do not.
[...]
> I'd like to get these functions working . . . ideas?
> 
A problem is that Icecast does not log a failed execution of the scripts.
Neither an exit code of the finished script.

It can only log some fork errors and file permissions before executing them.
And an attempt to execute a script is logged only if Icecast log level is set
to debug:

static void _run_script (event_exec_t *self, event_t *event) {
    pid_t pid, external_pid;

    /* do a fork twice so that the command has init as parent */
    external_pid = fork();
    switch (external_pid)
    {
        case 0:
            switch (pid = fork ())
            {
                case -1:
                    ICECAST_LOG_ERROR("Unable to fork %s (%s)", self->executable, strerror (errno));
                    break;
                case 0:  /* child */
                    if (access(self->executable, R_OK|X_OK) != 0) {
                        ICECAST_LOG_ERROR("Unable to run command %s (%s)", self->executable, strerror(errno));
                        exit(1);
                    }
                    ICECAST_LOG_DEBUG("Starting command %s", self->executable);
                    __setup_empty_script_environment(self, event);
                    execv(self->executable, __setup_argv(self, event));
                    exit(1);
                default: /* parent */
                    break;
            }
            exit (0);
        case -1:
            ICECAST_LOG_ERROR("Unable to fork %s", strerror (errno));
            break;
        default: /* parent */
            waitpid (external_pid, NULL, 0);
            break;
    }
}

You can use "strace" tool to check whether the scripts are actually executed.
Something like "strace -fq -e execve -p PID_OF_THE_RUNNING_SERVER".

The code is pretty terrible. access() does not answer whether a process can
exucute a program. Also execv() can fail for various reasons: Different
effective UID/GID, missing capabilities, violation of SELinux policy. And then
there can be problems with the executed program itself, like a wrong magic
number, unsupported architecture, a missing dynamic library, bad script
interpreter etc.

I recommend Icecast developers to remove the access() call and instead log
errno after a failed execve. Also logging a status code of the terminated
executable returned by waitpid() would be helpful.

-- Petr
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20220714/8416455d/attachment.sig>

From that.jack.elliott at gmail.com  Thu Jul 14 16:54:52 2022
From: that.jack.elliott at gmail.com (Jack Elliott)
Date: Thu, 14 Jul 2022 09:54:52 -0700
Subject: [Icecast] Which repository?
Message-ID: <3df4cbe7-09ce-b3b4-e45f-63072925edac@kpov.org>

Hi, I am running Icecast 2.4.0 on a Raspberry Pi. I want to upgrade 
Icecast to the latest stable version.

I am guessing that I want the "Debian 8.0 (jessie)" Distribution Release 
as shown on 
https://wiki.xiph.org/Icecast_Server/Installing_latest_version_(official_Xiph_repositories)

I'd like confirmation before I break anything. Here is my setup:

$ cat /etc/os-release
PRETTY_NAME="Raspbian GNU/Linux 8 (jessie)"
NAME="Raspbian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

Thank you!

-- 
Jack Elliott
Director of Classical Music Programming
KPOV 88.9 FM
High Desert Community Radio
Bend, OR



From that.jack.elliott at gmail.com  Thu Jul 14 20:17:04 2022
From: that.jack.elliott at gmail.com (Jack Elliott)
Date: Thu, 14 Jul 2022 13:17:04 -0700
Subject: [Icecast] <on-connect> / <on-disconnect> not working
In-Reply-To: <YtBB7lLtmrfqrhCM@album.bayer.uni.cx>
References: <0ed1e99b-e780-e4a4-c206-5e03543ba496@kpov.org>
 <YtBB7lLtmrfqrhCM@album.bayer.uni.cx>
Message-ID: <a50839b3-aadf-3205-2b33-833bb8743015@kpov.org>

Thank you, Petr!

Yes, error.log is not very helpful. With loglevel set to 4 (debug) I 
find that the server does claim to run the commands, but there is 
nothing to indicate what the problem might be:

[2022-07-14? 13:05:13] DBUG source/source_run_script Starting command /home/my_username/bin/email_onconnect.sh
[2022-07-14? 13:05:13] DBUG source/source_update_settings disconnect script "/home/my_username/bin/email_ondisconnect.sh"

This with Icecast 2.4.0 -- I am waiting for some help with a question I 
have posted in this mailing list to confirm I have the right repo 
selected before I attempt upgrading Icecast. It is a running, 
in-operation service for our radio station and I don't want to break 
anything.

-- 
Jack Elliott
Director of Classical Music Programming
KPOV 88.9 FM
High Desert Community Radio
Bend, OR

On 7/14/22 09:18, Petr Pisar wrote:
> V?Thu, Jul 14, 2022 at 08:16:03AM -0700,?Jack Elliott napsal(a):
>> Hi,
>>
>> Icecast server 2.4.0 running on Linux.
>>
> Could you try upgrading Icecast? The latest version is 2.4.4 and there were
> some fixes in between.
>
>> I have a couple of shell scripts that send emails on connect and on
>> disconnect. From the command line they work, but when called from
>> icecast they do not.
> [...]
>> I'd like to get these functions working . . . ideas?
>>
> A problem is that Icecast does not log a failed execution of the scripts.
> Neither an exit code of the finished script.
>
> It can only log some fork errors and file permissions before executing them.
> And an attempt to execute a script is logged only if Icecast log level is set
> to debug:
>
> static void _run_script (event_exec_t *self, event_t *event) {
>      pid_t pid, external_pid;
>
>      /* do a fork twice so that the command has init as parent */
>      external_pid = fork();
>      switch (external_pid)
>      {
>          case 0:
>              switch (pid = fork ())
>              {
>                  case -1:
>                      ICECAST_LOG_ERROR("Unable to fork %s (%s)", self->executable, strerror (errno));
>                      break;
>                  case 0:  /* child */
>                      if (access(self->executable, R_OK|X_OK) != 0) {
>                          ICECAST_LOG_ERROR("Unable to run command %s (%s)", self->executable, strerror(errno));
>                          exit(1);
>                      }
>                      ICECAST_LOG_DEBUG("Starting command %s", self->executable);
>                      __setup_empty_script_environment(self, event);
>                      execv(self->executable, __setup_argv(self, event));
>                      exit(1);
>                  default: /* parent */
>                      break;
>              }
>              exit (0);
>          case -1:
>              ICECAST_LOG_ERROR("Unable to fork %s", strerror (errno));
>              break;
>          default: /* parent */
>              waitpid (external_pid, NULL, 0);
>              break;
>      }
> }
>
> You can use "strace" tool to check whether the scripts are actually executed.
> Something like "strace -fq -e execve -p PID_OF_THE_RUNNING_SERVER".
>
> The code is pretty terrible. access() does not answer whether a process can
> exucute a program. Also execv() can fail for various reasons: Different
> effective UID/GID, missing capabilities, violation of SELinux policy. And then
> there can be problems with the executed program itself, like a wrong magic
> number, unsupported architecture, a missing dynamic library, bad script
> interpreter etc.
>
> I recommend Icecast developers to remove the access() call and instead log
> errno after a failed execve. Also logging a status code of the terminated
> executable returned by waitpid() would be helpful.
>
> -- Petr
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20220714/d6f6883c/attachment.htm>

From petr.pisar at atlas.cz  Fri Jul 15 05:10:44 2022
From: petr.pisar at atlas.cz (Petr Pisar)
Date: Fri, 15 Jul 2022 07:10:44 +0200
Subject: [Icecast] <on-connect> / <on-disconnect> not working
In-Reply-To: <a50839b3-aadf-3205-2b33-833bb8743015@kpov.org>
References: <0ed1e99b-e780-e4a4-c206-5e03543ba496@kpov.org>
 <YtBB7lLtmrfqrhCM@album.bayer.uni.cx>
 <a50839b3-aadf-3205-2b33-833bb8743015@kpov.org>
Message-ID: <YtD21OsE8zG+rGqo@album.bayer.uni.cx>

V?Thu, Jul 14, 2022 at 01:17:04PM -0700,?Jack Elliott napsal(a):
> Thank you, Petr!
> 
> Yes, error.log is not very helpful. With loglevel set to 4 (debug) I 
> find that the server does claim to run the commands, but there is 
> nothing to indicate what the problem might be:
> 
> [2022-07-14? 13:05:13] DBUG source/source_run_script Starting command /home/my_username/bin/email_onconnect.sh
> [2022-07-14? 13:05:13] DBUG source/source_update_settings disconnect script "/home/my_username/bin/email_ondisconnect.sh"
> 
I really recommend using the strace tool to verify the script is successfully
executed.

I suspect that a problem is in your script. E.g. it does not work without
a terminal or with /dev/null connected to standard input and output. Icecast
changes file descriptors for the executed commands.

Does you script work when executed from a shell like this?

    /home/my_username/bin/email_onconnect.sh </dev/null >/dev/null 2>/dev/null

> This with Icecast 2.4.0 -- I am waiting for some help with a question I 
> have posted in this mailing list to confirm I have the right repo 
> selected before I attempt upgrading Icecast. It is a running, 
> in-operation service for our radio station and I don't want to break 
> anything.
>
While Icecast developers have a good relationship with Debian, I would recommend
you to contact vendor of the repository in question. Icecast developers cannot
be responsible for packaging Icecast by someone else.

-- Petr

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20220715/30258784/attachment.sig>

From jordan at subj.am  Fri Jul 15 05:14:05 2022
From: jordan at subj.am (Jordan Erickson)
Date: Thu, 14 Jul 2022 22:14:05 -0700
Subject: [Icecast] <on-connect> / <on-disconnect> not working
In-Reply-To: <0ed1e99b-e780-e4a4-c206-5e03543ba496@kpov.org>
References: <0ed1e99b-e780-e4a4-c206-5e03543ba496@kpov.org>
Message-ID: <fdcaf31c-ffd1-b234-9211-c988eeb7b996@subj.am>

Hi Jack,

Does the user user actually running the Icecast process have access to 
the scripts within the /home/my_username/bin directory? Not sure if 
Icecast is running as $my_username from what you've said here. I'm also 
not sure if Icecast checks access to each script specified in the config 
for access during startup/reload.


Cheers,
Jordan

-- 
Jordan Erickson
SubJam, SPC -https://subj.am/
+1 360.603.5039


On 7/14/22 08:16, Jack Elliott wrote:
>
> Hi,
>
> Icecast server 2.4.0 running on Linux.
>
> I have a couple of shell scripts that send emails on connect and on 
> disconnect. From the command line they work, but when called from 
> icecast they do not.
>
> Here is the mount section of my icecast.xml:
>
> <mount type="normal">
> ??????? <mount-name>/my_stream</mount-name>
> <fallback-mount>/fallbacks/my_fallback.mp3</fallback-mount>
> ??????? <fallback-override>1</fallback-override>
> ??????? <fallback-when-full>1</fallback-when-full>
> *<on-connect>/home/my_username/bin/email_onconnect.sh</on-connect>**
> **<on-disconnect>/home/my_username/bin/email_ondisconnect.sh</on-disconnect>*
> ??????? <no-yp>1</no-yp>
> ??? </mount>
>
> After putting the new <on-connect> and <on-disconnect> entries into 
> icecast.xml I reloaded the config with /etc/init.d/icecast2 reload and 
> there was no error written to /var/log/icecast2/error.log
>
> <on-connect> calls /home/my_username/bin/email_onconnect.sh which 
> works from the command line. Likewise, <on-disconnect> calls a similar 
> script which also works from the command line. I've tested them.
>
> The permissions for the two scripts:
>
> -rwxr-xr-x 1 my_username my_username 352 Jul 14 07:49 email_onconnect.sh
> -rwxr-xr-x 1 my_username my_username 375 Jul 14 07:49 
> email_ondisconnect.sh
>
> I'd like to get these functions working . . . ideas?
>
> Thank you!
>
> -- 
> Jack Elliott
> Director of Classical Music Programming
> KPOV 88.9 FM
> High Desert Community Radio
> Bend, OR
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20220714/46116ec0/attachment.htm>

From that.jack.elliott at gmail.com  Fri Jul 15 13:34:42 2022
From: that.jack.elliott at gmail.com (Jack Elliott)
Date: Fri, 15 Jul 2022 06:34:42 -0700
Subject: [Icecast] <on-connect> / <on-disconnect> not working
In-Reply-To: <fdcaf31c-ffd1-b234-9211-c988eeb7b996@subj.am>
References: <0ed1e99b-e780-e4a4-c206-5e03543ba496@kpov.org>
 <fdcaf31c-ffd1-b234-9211-c988eeb7b996@subj.am>
Message-ID: <01a40372-a1a7-dbaf-0133-766cdca5bb8d@kpov.org>

Hi Jordan, good idea!

The icecast2 process is owned by user icecast2, not the Owner of the 
target scripts. I changed the permissions for the email scripts to rwx 
for everyone, but no joy.

Thank you!

-- 
Jack Elliott
Director of Classical Music Programming
KPOV 88.9 FM
High Desert Community Radio
Bend, OR

On 7/14/22 22:14, Jordan Erickson wrote:
> Hi Jack,
>
> Does the user user actually running the Icecast process have access to 
> the scripts within the /home/my_username/bin directory? Not sure if 
> Icecast is running as $my_username from what you've said here. I'm 
> also not sure if Icecast checks access to each script specified in the 
> config for access during startup/reload.
>
>
> Cheers,
> Jordan
>
> -- 
> Jordan Erickson
> SubJam, SPC -https://subj.am/
> +1 360.603.5039
>
> On 7/14/22 08:16, Jack Elliott wrote:
>>
>> Hi,
>>
>> Icecast server 2.4.0 running on Linux.
>>
>> I have a couple of shell scripts that send emails on connect and on 
>> disconnect. From the command line they work, but when called from 
>> icecast they do not.
>>
>> Here is the mount section of my icecast.xml:
>>
>> <mount type="normal">
>> ??????? <mount-name>/my_stream</mount-name>
>> <fallback-mount>/fallbacks/my_fallback.mp3</fallback-mount>
>> ??????? <fallback-override>1</fallback-override>
>> <fallback-when-full>1</fallback-when-full>
>> *<on-connect>/home/my_username/bin/email_onconnect.sh</on-connect>**
>> **<on-disconnect>/home/my_username/bin/email_ondisconnect.sh</on-disconnect>*
>> ??????? <no-yp>1</no-yp>
>> ??? </mount>
>>
>> After putting the new <on-connect> and <on-disconnect> entries into 
>> icecast.xml I reloaded the config with /etc/init.d/icecast2 reload 
>> and there was no error written to /var/log/icecast2/error.log
>>
>> <on-connect> calls /home/my_username/bin/email_onconnect.sh which 
>> works from the command line. Likewise, <on-disconnect> calls a 
>> similar script which also works from the command line. I've tested them.
>>
>> The permissions for the two scripts:
>>
>> -rwxr-xr-x 1 my_username my_username 352 Jul 14 07:49 email_onconnect.sh
>> -rwxr-xr-x 1 my_username my_username 375 Jul 14 07:49 
>> email_ondisconnect.sh
>>
>> I'd like to get these functions working . . . ideas?
>>
>> Thank you!
>>
>> -- 
>> Jack Elliott
>> Director of Classical Music Programming
>> KPOV 88.9 FM
>> High Desert Community Radio
>> Bend, OR
>>
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
>
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20220715/dde5ddcb/attachment.htm>

From that.jack.elliott at gmail.com  Fri Jul 15 13:47:56 2022
From: that.jack.elliott at gmail.com (Jack Elliott)
Date: Fri, 15 Jul 2022 06:47:56 -0700
Subject: [Icecast] <on-connect> / <on-disconnect> not working
In-Reply-To: <YtD21OsE8zG+rGqo@album.bayer.uni.cx>
References: <0ed1e99b-e780-e4a4-c206-5e03543ba496@kpov.org>
 <YtBB7lLtmrfqrhCM@album.bayer.uni.cx>
 <a50839b3-aadf-3205-2b33-833bb8743015@kpov.org>
 <YtD21OsE8zG+rGqo@album.bayer.uni.cx>
Message-ID: <9c84e2cd-1c8a-4afa-e046-1689dfe30a7c@kpov.org>

Hello Petr,


On 7/14/22 22:10, Petr Pisar wrote:
> V?Thu, Jul 14, 2022 at 01:17:04PM -0700,?Jack Elliott napsal(a):
>> Thank you, Petr!
>>
>> Yes, error.log is not very helpful. With loglevel set to 4 (debug) I
>> find that the server does claim to run the commands, but there is
>> nothing to indicate what the problem might be:
>>
>> [2022-07-14? 13:05:13] DBUG source/source_run_script Starting command /home/my_username/bin/email_onconnect.sh
>> [2022-07-14? 13:05:13] DBUG source/source_update_settings disconnect script "/home/my_username/bin/email_ondisconnect.sh"
>>
> I really recommend using the strace tool to verify the script is successfully
> executed.
>
> I suspect that a problem is in your script. E.g. it does not work without
> a terminal or with /dev/null connected to standard input and output. Icecast
> changes file descriptors for the executed commands.
>
> Does you script work when executed from a shell like this?
>
>      /home/my_username/bin/email_onconnect.sh </dev/null >/dev/null 2>/dev/null

Yes it does.

I don't know how to interpret the output of strace.

Here is what your suggested command gave when I connected to the 
mountpoint on the Icecast server, then disconnected from it (username 
and target email addresses anonymized):

$ sudo strace -fq -e execve -p 673
[sudo] password for my_username:
[pid 20973] +++ exited with 0 +++
[pid 20992] +++ exited with 0 +++
[pid 20994] +++ exited with 0 +++
[pid 20993] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=20994, si_uid=112, si_status=0, si_utime=0, si_stime=1} ---
[pid 20995] execve("/home/my_username/bin/email_onconnect.sh", ["/home/my_username/bin/email_onconnec"..., "/stream"], [/* 5 vars */]) = 0
[pid 20996] execve("/usr/bin/msmtp", ["msmtp", "my_address at org"], [/* 7 vars */]) = 0
[pid 20996] +++ exited with 78 +++
[pid 20995] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=20996, si_uid=112, si_status=78, si_utime=0, si_stime=1} ---
[pid 20995] +++ exited with 78 +++
[pid 20997] +++ exited with 0 +++
[pid 20993] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=20997, si_uid=112, si_status=0, si_utime=0, si_stime=1} ---
[pid 20993] +++ exited with 0 +++
[pid 20998] execve("/home/my_username/bin/email_ondisconnect.sh", ["/home/my_username/bin/email_ondiscon"..., "/stream"], [/* 5 vars */]) = 0
[pid 20999] execve("/usr/bin/msmtp", ["msmtp", "my_address at org"], [/* 7 vars */]) = 0
[pid 20999] +++ exited with 78 +++
[pid 20998] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=20999, si_uid=112, si_status=78, si_utime=0, si_stime=1} ---
[pid 20998] +++ exited with 78 +++
[pid 21000] +++ exited with 0 +++

This thread is getting a little messy.

Thank you for looking at this!

>
>> This with Icecast 2.4.0 -- I am waiting for some help with a question I
>> have posted in this mailing list to confirm I have the right repo
>> selected before I attempt upgrading Icecast. It is a running,
>> in-operation service for our radio station and I don't want to break
>> anything.
>>
> While Icecast developers have a good relationship with Debian, I would recommend
> you to contact vendor of the repository in question. Icecast developers cannot
> be responsible for packaging Icecast by someone else.
>
> -- Petr
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20220715/57341b19/attachment.htm>

From petr.pisar at atlas.cz  Fri Jul 15 17:44:21 2022
From: petr.pisar at atlas.cz (Petr Pisar)
Date: Fri, 15 Jul 2022 19:44:21 +0200
Subject: [Icecast] <on-connect> / <on-disconnect> not working
In-Reply-To: <9c84e2cd-1c8a-4afa-e046-1689dfe30a7c@kpov.org>
References: <0ed1e99b-e780-e4a4-c206-5e03543ba496@kpov.org>
 <YtBB7lLtmrfqrhCM@album.bayer.uni.cx>
 <a50839b3-aadf-3205-2b33-833bb8743015@kpov.org>
 <YtD21OsE8zG+rGqo@album.bayer.uni.cx>
 <9c84e2cd-1c8a-4afa-e046-1689dfe30a7c@kpov.org>
Message-ID: <YtGndTX03VGx7mzb@album.bayer.uni.cx>

V?Fri, Jul 15, 2022 at 06:47:56AM -0700,?Jack Elliott napsal(a):
> [pid 20995] execve("/home/my_username/bin/email_onconnect.sh", ["/home/my_username/bin/email_onconnec"..., "/stream"], [/* 5 vars */]) = 0

Here email_onconnect.sh is successfully executed (return value 0). Though, it
does not mean that the script won't fail later. Just that the script has
started.

> [pid 20996] execve("/usr/bin/msmtp", ["msmtp", "my_address at org"], [/* 7 vars */]) = 0

Here email_onconnect.sh executed msmtp program.

> [pid 20996] +++ exited with 78 +++

Here msmtp program termined with an exit code 78.

> [pid 20995] --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=20996, si_uid=112, si_status=78, si_utime=0, si_stime=1} ---

Here email_onconnect.sh program received a signal that msmtp exited with
details about msmtp exit: It was a regular exit (not a crash), it was running
as user ID 112 and the exit code was 78.

> [pid 20995] +++ exited with 78 +++

Here the exit code is propaged up to a parent process. Probably msmtp was
the last command in email_onconnect.sh.

What does it mean? It means that Icecast successfully executed your
email_onconnect.sh script. But msmtp failed with exit code 78.

I don't know msmtp tool. Its documentation does not explains exit codes
much <https://marlam.de/msmtp/msmtp.html#Exit-code>. It only referes to
sysexits.h header file. That file does not exist in msmtp sources, it seems to
be copied from gnulib sources
<https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=lib/sysexits.in.h;h=9a65060ee695eb93a8adbf3e329f1e5df3fcdbbc;hb=HEAD>.
There you can read:

    # define EX_CONFIG 78

Gnulib documentation does not explain what EX_CONFIG means. Searching Internet
discloses a similar header file <https://gist.github.com/bojanrajkovic/831993>
from BSD which is more verbose:

    #define EX_CONFIG	78	/* configuration error */

So very probably msmtp tool tries to report an error in a configuration.

I recommend you to study msmtp documentation to know how to enable logging in
msmtp and where to read the log. Debian has a brief introduction
<https://wiki.debian.org/msmtp>. You probably want to set "logfile" option to
a writable file and then watch what will emerge in that file.

You could also log standard output and error output of msmtp command in your
email_onconnect.sh script. Like this:

    msmtp "my_address at org" >/tmp/log 2>&1

Maybe you will find something interesting.

-- Petr
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20220715/71c438bf/attachment.sig>