On Air Is Greyed Out
  • Vote Up0Vote Down Dane TerrellDane Terrell
    Posts: 10Member
    Very wierd. Airtime was streaming just fine, all of a sudden it streams silently. The On Air button occassionaly will light up red but then grey back out and stay grey. Also, it seems stuck trying to connect to icecast. The passwords are correct and airtime_128 mounts in icecast.

    I verified that airtime is running correctly. Any ideas? Icecast is also working correctly. I can log in and start other mount points and listen.
  • 13 Comments sorted by
  • Vote Up0Vote Down hoerichhoerich
    Posts: 627Member, Airtime Moderator
    I do face similar phenomenons, but I'm not sure for now what the problem is.
    I experience OFF-AIR for the first 50secs of a 5min (internal) Webstream.
    Icecast seems to work fine for me. I got two Live-Streams constantly connected to Icecast for Takeovers.
    I try to sort out the logs this week.

    Official Airtime Forum Manager
    --------------------------
    Most of the time an issue is located between keyboard and chair.
  • Vote Up0Vote Down Dane TerrellDane Terrell
    Posts: 10Member
    I even reinstalled Airtime, fresh install, and still the on air is greyed out, streaming in silence and for some reason, airtime can not connect to icecast. It can mount, but not connect. The passwords are correct as well.
  • Vote Up0Vote Down Dane TerrellDane Terrell
    Posts: 10Member

    2013/07/15 16:48:14 [stdout:3] #########################################
    2013/07/15 16:48:14 [stdout:3] #           *** pypo  ***               #
    2013/07/15 16:48:14 [stdout:3] #     pypo notification gateway         #
    2013/07/15 16:48:14 [stdout:3] #########################################
    2013/07/15 16:48:17 [server:3] New client: localhost.localdomain.
    2013/07/15 16:48:17 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:48:27 [server:3] New client: localhost.localdomain.
    2013/07/15 16:48:27 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:48:37 [server:3] New client: localhost.localdomain.
    2013/07/15 16:48:37 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:48:47 [server:3] New client: localhost.localdomain.
    2013/07/15 16:48:47 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:48:57 [server:3] New client: localhost.localdomain.
    2013/07/15 16:48:57 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:49:07 [server:3] New client: localhost.localdomain.
    2013/07/15 16:49:07 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:49:17 [server:3] New client: localhost.localdomain.
    2013/07/15 16:49:17 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:49:27 [server:3] New client: localhost.localdomain.
    2013/07/15 16:49:27 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:49:37 [server:3] New client: localhost.localdomain.
    2013/07/15 16:49:37 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:49:47 [server:3] New client: localhost.localdomain.
    2013/07/15 16:49:47 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:49:57 [server:3] New client: localhost.localdomain.
    2013/07/15 16:49:57 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:50:07 [server:3] New client: localhost.localdomain.
    2013/07/15 16:50:07 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:50:17 [server:3] New client: localhost.localdomain.
    2013/07/15 16:50:17 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:50:27 [server:3] New client: localhost.localdomain.
    2013/07/15 16:50:27 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:50:37 [server:3] New client: localhost.localdomain.
    2013/07/15 16:50:37 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:50:47 [server:3] New client: localhost.localdomain.
    2013/07/15 16:50:47 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:50:57 [server:3] New client: localhost.localdomain.
    2013/07/15 16:50:57 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:51:07 [server:3] New client: localhost.localdomain.
    2013/07/15 16:51:07 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:51:12 [server:3] New client: localhost.localdomain.
    2013/07/15 16:51:12 [lang:3] vars.stream_metadata_type
    2013/07/15 16:51:12 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:51:12 [server:3] New client: localhost.localdomain.
    2013/07/15 16:51:12 [lang:3] vars.default_dj_fade
    2013/07/15 16:51:12 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:51:13 [server:3] New client: localhost.localdomain.
    2013/07/15 16:51:13 [server:3] Client localhost.localdomain disconnected.
    2013/07/15 16:51:13 [main:3] Shutdown started!
    2013/07/15 16:51:13 [main:3] Waiting for threads to terminate...
    2013/07/15 16:51:13 [airtime_128:3] Closing connection...
    2013/07/15 16:51:13 [clock.wallclock_main:3] Streaming loop stopped.

  • Vote Up0Vote Down Albert FRAlbert FR
    Posts: 1,978Member, Airtime Moderator
    what said :

    airtime-check-system

    ?
    ----
    Je peux le faire ;) [Pour vous] / I can do it [For You] Gnu/Linux & Media Architect
    Co-founder NessRadio.com
  • Vote Up0Vote Down hoerichhoerich
    Posts: 627Member, Airtime Moderator
    Ok, I was watching the last Shows for this problem

    We've had an internal Webstream scheduled from 10:07 - 11:00 CEST working.
    At 11 CEST a 1-hr-Show started containing a Jingle, 59min-Show and an Outro. All Stereo.

    At 11:00:00 CEST Airtimes Red-Light greyed out, the Webstream scheduled from 10-11AM continued streaming for about 12-18 minutes.
    Then the Red-Light turns Red again and Airtime steps into the Scheduled Show already running 15-18 minutes.

    I experience a similar problem with our TOH-Show-Elements 11 times a day for 7 minutes the first minute of the Containing Webstream is not broadcasted.

    It seems like the first ca. 20% of the scheduled content is not broadcasted, the rest is aired fine.
    Attached are my logs from 11:30 CEST, although the log-file is dated with 09:30.
    I'm wondering what triggers the timestamp for the log-dump?
    My Airtime-Time was 11:30 when creating log-dump.

    I thought I share my troubles n logs, because we are currently preparing our annual Radio Festival, so my time is rare this week.

    airtime-check-system told me everything's ok, while on-air light was greyed out.
    airtime-log-all-2013-07-16-09-35-29.zip
    2M
    Official Airtime Forum Manager
    --------------------------
    Most of the time an issue is located between keyboard and chair.
  • Vote Up0Vote Down Albert FRAlbert FR
    Posts: 1,978Member, Airtime Moderator
    first look,
    I'm updating this post if I find something else...

    you seems to have authentication problem :

    013/07/16 11:35:24 [lang:3] live dj connected
    2013/07/16 11:35:24 [lang:3] Live DJ authenticated: False

    have you problem with liquidsoap ?
    is always up ?
    can you verify with monit ?
    Post edited by Albert FR at 2013-07-16 08:51:30
    ----
    Je peux le faire ;) [Pour vous] / I can do it [For You] Gnu/Linux & Media Architect
    Co-founder NessRadio.com
  • Vote Up0Vote Down hoerichhoerich
    Posts: 627Member, Airtime Moderator
    i try monit later.
    no problems with LS since v1.1.11

    Your mentioned Authentication comes from a streaming-client I forgot to disable.
    I did change our arrangement from using Show-Source-Input to using scheduled Webstreams.
    This should not have an effect on LS or this problem. But I deactivate it later and see...

    thx for the tipp, albert
    Official Airtime Forum Manager
    --------------------------
    Most of the time an issue is located between keyboard and chair.
  • Vote Up0Vote Down Dane TerrellDane Terrell
    Posts: 10Member
    When I run airtime system check, everything is fine and normal, nothing failed. I've manually restarted and started the monitor and rabbit mqserver. Still can't connect to icecast nor does the on air work.
  • Vote Up0Vote Down Dane TerrellDane Terrell
    Posts: 10Member
    Here is my airtime system check readout

    AIRTIME_STATUS_URL             = http://mistikradio.co:80/airtime/public/api/status/format/json/api_key/%%api_key%%
    AIRTIME_SERVER_RESPONDING      = OK
    KERNEL_VERSION                 = 3.2.0-49-generic-pae
    MACHINE_ARCHITECTURE           = i686
    TOTAL_MEMORY_MBYTES            = 2053296
    TOTAL_SWAP_MBYTES              = 2086908
    AIRTIME_VERSION                = 2.4.0
    OS                             = Ubuntu 12.04.2 LTS i686
    CPU                            = Intel(R) Pentium(R) 4 CPU 3.20GHz
    WEB_SERVER                     = Apache/2.2.22 (Ubuntu)
    PLAYOUT_ENGINE_PROCESS_ID      = 11531
    PLAYOUT_ENGINE_RUNNING_SECONDS = 48981
    PLAYOUT_ENGINE_MEM_PERC        = 0.4%
    PLAYOUT_ENGINE_CPU_PERC        = 0.0%
    LIQUIDSOAP_PROCESS_ID          = 12601
    LIQUIDSOAP_RUNNING_SECONDS     = 48673
    LIQUIDSOAP_MEM_PERC            = 0.8%
    LIQUIDSOAP_CPU_PERC            = 9.9%
    MEDIA_MONITOR_PROCESS_ID       = 22694
    MEDIA_MONITOR_RUNNING_SECONDS  = 44120
    MEDIA_MONITOR_MEM_PERC         = 0.5%
    MEDIA_MONITOR_CPU_PERC         = 0.0%
    -- Your installation of Airtime looks OK!

  • Vote Up0Vote Down Cliff WangCliff Wang
    Posts: 339Member, Sourcefabric Team
    @Dane,

    Could you please attach all logs here? Just do:
    sudo airtime-log --dump
    Cloud Radio -> http://airtime.pro
  • Vote Up0Vote Down Dane TerrellDane Terrell
    Posts: 10Member
    I figured something out. Airtime 2.4 on my system causes the on air to be grey out. I unistalled it and re-installed 2.3 it can connect to icecast and on the on air works, but it is still not streaming to icecast.
  • Vote Up0Vote Down Dane TerrellDane Terrell
    Posts: 10Member
    Icecast is not receiving data from airtime
  • Vote Up0Vote Down Dane TerrellDane Terrell
    Posts: 10Member
    Solved. Restarted the playout.
Add a Comment