Liquidsoap constantly failing

Get Help
21

From @aresstokrat on Tue Jun 06 2017 07:51:57 GMT+0000 (UTC)

this is what it shows when starting a show:

2017/06/06 10:49:50 [mp3-128:3] Will try again in 5.00 sec.
2017/06/06 10:49:50 [s4:3] Prepared "/var/tmp/airtime/pypo/cache/scheduler/144.mp3" (RID 0).
2017/06/06 10:49:50 [schedule_noise_switch:3] Switch to map_metadata_5630 with transition.
2017/06/06 10:49:50 [lang:3] transition called...
2017/06/06 10:49:50 [switch_5628:3] Switch to insert_metadata_5614.
2017/06/06 10:49:50 [cue_cut_5555:3] Cueing in...
2017/06/06 10:49:50 [amplify_5559:3] Overriding amplification: 0.336512.
2017/06/06 10:49:50 [lang:3] timeout --signal=KILL 45 pyponotify --media-id=133 &
2017/06/06 10:49:50 [lang:3] Using stream_format 0
2017/06/06 10:49:50 [lang:3] Using stream_format 0
2017/06/06 10:49:50 [lang:3] Using stream_format 0
2017/06/06 10:49:55 [server:3] New client: localhost.
2017/06/06 10:49:55 [lang:3] dynamic_source.get_id
2017/06/06 10:49:55 [server:3] Client localhost disconnected.
2017/06/06 10:49:56 [mp3-128:3] Connecting mount mp3-128 for source@localhost...
2017/06/06 10:49:56 [mp3-128:2] Connection failed: could not write data to host: Connection refused in write()
2017/06/06 10:49:56 [lang:3] timeout --signal=KILL 45 pyponotify --error='could not write data to host: Connection refused in write()' --stream-id=1 --time=1496667758.49 &
2017/06/06 10:49:56 [mp3-128:3] Will try again in 5.00 sec.
2017/06/06 10:50:02 [mp3-128:3] Connecting mount mp3-128 for source@localhost...
2017/06/06 10:50:02 [mp3-128:2] Connection failed: could not write data to host: Connection refused in write()
2017/06/06 10:50:02 [lang:3] timeout --signal=KILL 45 pyponotify --error='could not write data to host: Connection refused in write()' --stream-id=1 --time=1496667758.49 &
2017/06/06 10:50:02 [mp3-128:3] Will try again in 5.00 sec.
2017/06/06 10:50:08 [mp3-128:3] Connecting mount mp3-128 for source@localhost...
2017/06/06 10:50:08 [mp3-128:2] Connection failed: could not write data to host: Connection refused in write()
2017/06/06 10:50:08 [lang:3] timeout --signal=KILL 45 pyponotify --error='could not write data to host: Connection refused in write()' --stream-id=1 --time=1496667758.49 &
2017/06/06 10:50:08 [mp3-128:3] Will try again in 5.00 sec.
22

From @aresstokrat on Tue Jun 06 2017 08:04:23 GMT+0000 (UTC)

Thank you !!! I found the error, it was in icecast config.
No ‘mount’ for /mp3-128

<mount>
<mount-name>/live</mount-name>
<charset>UTF-8</charset>
<fallback-mount>/play</fallback-mount>
<fallback-override>1</fallback-override>
<fallback-when-full>1</fallback-when-full>
</mount>

<mount-name>/mp3-128</mount-name>
<charset>UTF-8</charset>
</mount>

now its runing perfectly fine !! Yesssss!!! :slight_smile:

23

From @hairmare on Tue Jun 06 2017 16:34:30 GMT+0000 (UTC)

Weird, normally LibreTime creates the needed mountpoints on the fly.

24

From @aresstokrat on Wed Jun 07 2017 11:07:19 GMT+0000 (UTC)

Today i found out that services are marked as down in admin panel.
(pypo, liquidsoap)
Icecast’s status page shows no mounting points.

BUT - ON AIR is red and stream is playing even now, how that ?
And after few tracks i checked status page and its marked UP again.
(still no mounting point in icecast’s status page)

$ sudo systemctl status airtime-playout.service

● airtime-playout.service - Airtime Playout Service
   Loaded: loaded (/etc/systemd/system/airtime-playout.service; enabled)
   Active: active (running) since Вт 2017-06-06 10:54:48 +03; 1 day 3h ago
 Main PID: 22306 (airtime-playout)
   CGroup: /system.slice/airtime-playout.service
           └─22306 /usr/bin/python /usr/bin/airtime-playout

июн 07 13:59:39 raspberrypi airtime-playout[22306]: .datetime(2017, 6, 7, 11, 26, 25), u'replay_gain': -4.24, 'dst': u'/var/tmp/airtime/pypo/cache/scheduler/173.mp3', u'file...'soundcloud
июн 07 13:59:39 raspberrypi airtime-playout[22306]: nt': False, u'end': datetime.datetime(2017, 6, 7, 11, 43, 21), u'fade_out': 100, u'show_name': u'12h', 'file_ready': True...e/pypo/cach
июн 07 13:59:39 raspberrypi airtime-playout[22306]: , u'fade_in': 100}, u'2017-06-07-11-36-05': {u'cue_out': 209.2, u'independent_event': False, u'end': datetime.datetime(20...e.datetime(
июн 07 13:59:39 raspberrypi airtime-playout[22306]: ': None, u'report_location': None, u'url': None, u'checksum': None, u'bpm': None, u'track_number': 3, u'isrc_number': None, u'length...
июн 07 13:59:39 raspberrypi airtime-playout[22306]: 2017-06-07 13:59:39,278 [pypoliqqueue] [INFO ]  waiting 216.72143s until next scheduled item
июн 07 13:59:39 raspberrypi airtime-playout[22306]: 2017-06-07 13:59:39,407 [pypofetch] [INFO ]  File '/var/tmp/airtime/pypo/cache/scheduler/165.mp3' removed
июн 07 13:59:39 raspberrypi airtime-playout[22306]: 2017-06-07 13:59:39,483 [pypofetch] [INFO ]  File '/var/tmp/airtime/pypo/cache/scheduler/254.mp3' removed
июн 07 13:59:39 raspberrypi airtime-playout[22306]: 2017-06-07 13:59:39,484 [pypofetch] [INFO ]  Loop #277
июн 07 13:59:40 raspberrypi airtime-playout[22306]: 2017-06-07 13:59:40,296 [pypofile] [INFO ]  copying from http://localhost//rest/media/166 to local cache /var/tmp/airtime...ler/166.mp3
июн 07 13:59:40 raspberrypi airtime-playout[22306]: 2017-06-07 13:59:40,297 [pypofile] [ERROR]  http://localhost:80/rest/media/166/download
Hint: Some lines were ellipsized, use -l to show in full.

$ sudo systemctl status airtime-liquidsoap.service

● airtime-liquidsoap.service - Airtime Liquidsoap Service
   Loaded: loaded (/etc/systemd/system/airtime-liquidsoap.service; enabled)
   Active: active (running) since Вт 2017-06-06 10:57:46 +03; 1 day 3h ago
 Main PID: 23252 (liquidsoap)
   CGroup: /system.slice/airtime-liquidsoap.service
           └─23252 airtime-liquidsoap /usr/local/lib/python2.7/dist-packages/airtime_playout-1.0-py2.7.egg/liquidsoap/ls_script.liq --verbose -f

июн 07 14:03:17 raspberrypi airtime-liquidsoap[23252]: 2017/06/07 14:03:17 [cue_cut_5555:3] Cueing in...
июн 07 14:03:17 raspberrypi airtime-liquidsoap[23252]: 2017/06/07 14:03:17 [amplify_5559:3] Overriding amplification: 0.436516.
июн 07 14:03:17 raspberrypi airtime-liquidsoap[23252]: 2017/06/07 14:03:17 [lang:3] timeout --signal=KILL 45 pyponotify --media-id=237 &
июн 07 14:03:17 raspberrypi airtime-liquidsoap[23252]: 2017/06/07 14:03:17 [lang:3] Using stream_format 0
июн 07 14:03:17 raspberrypi airtime-liquidsoap[23252]: 2017/06/07 14:03:17 [lang:3] Using stream_format 0
июн 07 14:03:17 raspberrypi airtime-liquidsoap[23252]: 2017/06/07 14:03:17 [lang:3] Using stream_format 0
июн 07 14:03:21 raspberrypi airtime-liquidsoap[23252]: #########################################
июн 07 14:03:21 raspberrypi airtime-liquidsoap[23252]: #           *** pypo  ***               #
июн 07 14:03:21 raspberrypi airtime-liquidsoap[23252]: #     pypo notification gateway         #
июн 07 14:03:21 raspberrypi airtime-liquidsoap[23252]: #########################################

@hairmare

Weird, normally LibreTime creates the needed mountpoints on the fly.

I did’t knew that.
I was making all changes by hands. (including mount points)
Where it searches for icecast’s config and what rights does it need?
Couse i have config not in default directory.

25

From @hairmare on Wed Jun 07 2017 14:52:50 GMT+0000 (UTC)

> Where it searches for icecast’s config and what rights does it need?

Couse i have config not in default directory.

It’s probably doing it through the api using the admin username/password combo.

The default config as installed on the vagrant boxes seems to work. I haven’t done any real testing to figure out how it works and what happens when the password is changed.

26

From @aresstokrat on Thu Jun 15 2017 12:24:15 GMT+0000 (UTC)

Strange thing happeping. After restart of Pi , no Pypo and Analyzer service started.
I checked
systemctl list-unitsand found that there is no such services loaded. How that can be?
and

● airtime-celery.service loaded failed failed LibreTime Celery Service

still i see them in directory

$ ls -la /etc/systemd/system
итого 72
drwxr-xr-x 13 root root 4096 июн  5 14:06 .
drwxr-xr-x  6 root root 4096 май 15 13:03 ..
-rwxr-xr-x  1 pi   pi    181 июн  9 11:23 airtime_analyzer.service
-rwxr-xr-x  1 pi   pi    361 май 31 16:48 airtime-celery.service
-rwxr-xr-x  1 pi   pi    177 июн  9 11:22 airtime-liquidsoap.service
-rwxr-xr-x  1 pi   pi    171 июн  9 11:23 airtime-playout.service

[UPDATE 1]
but daemon-reload does’t help.
i cant run them with
sudo systemctl start-airtime-playout.service

sudo systemctl list-unit-files

airtime-celery.service                 enabled 
airtime-liquidsoap.service             enabled 
airtime-playout.service                disabled
airtime_analyzer.service               disabled

[UPDATE 2]
this is what i did next (but it does’t help, maybe i need to restart pi):

pi@raspberrypi:~ $ sudo systemctl enable airtime-playout.service 
Created symlink from /etc/systemd/system/multi-user.target.wants/airtime-playout.service to /etc/systemd/system/airtime-playout.service.
pi@raspberrypi:~ $ sudo systemctl enable airtime_analyzer.service 
Created symlink from /etc/systemd/system/multi-user.target.wants/airtime_analyzer.service to /etc/systemd/system/airtime_analyzer.service.
pi@raspberrypi:~ $ sudo systemctl status airtime-playout.service 
● airtime-playout.service - Airtime Playout Service
   Loaded: loaded (/etc/systemd/system/airtime-playout.service; enabled)
   Active: inactive (dead)
pi@raspberrypi:~ $ sudo systemctl start airtime-playout.service 
pi@raspberrypi:~ $ sudo systemctl start airtime_analyzer.service

how to find origin of disabling ? what log should i read?

[UPDATE 3]

Can not connect to the streaming server
could not connect to host: Connection refused in connect()

In stream section of admin panel. How that :(((( I did’t change anything. Icecast2 is working with same config :((

[UPDATE 4]

2017/06/15 16:12:54 [FireFM:3] Connecting mount mp3-128 for source@localhost...
2017/06/15 16:12:54 [FireFM:2] Connection failed: could not connect to host: Connection refused in connect()
2017/06/15 16:12:54 [lang:3] timeout --signal=KILL 45 pyponotify --error='could not connect to host: Connection refused in connect()' --stream-id=1 --time=1497532098.24 &
2017/06/15 16:12:54 [FireFM:3] Will try again in 5.00 sec.
2017/06/15 16:12:55 [FireFM(dot)1:3] Connecting mount aac96 for source@localhost...
2017/06/15 16:12:55 [FireFM(dot)1:2] Connection failed: could not connect to host: Connection refused in connect()
2017/06/15 16:12:55 [lang:3] timeout --signal=KILL 45 pyponotify --error='could not connect to host: Connection refused in connect()' --stream-id=2 --time=1497532098.24 &
2017/06/15 16:12:55 [FireFM(dot)1:3] Will try again in 5.00 sec.

and finaly its come to an state
Connected to the streaming serverby itself in 15 minutes. I dont know why, did’t change anything. :frowning: